Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Dataset enhancement request

Answered
David Klein User

I would like to improve functionality on datasets in 2 ways:
1) I would like to be able to add a new attribute to columns that would determine whether column was included as a filter or not. If the column was not included as a filter then we would still have ability to reference column when exporting data to a destination. For example, let's suppose I have a column for street address. I don't really need users to be able to filter on the street address. But I would want that field available to be exported for a postal destination. This is especially important when dealing with larger datasets that have multiple columns.
2) It would be beneficial to limit visibility of datasets to certain roles/users. Currently, if a user has access to one dataset then they have access to all. While we can use workspaces to get around this it leads to having to duplicate work and maintain more datasets/workspaces than necessary.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Sean Lynch Fivetranner

    Thank you for the feedback, David! Could you explain a bit more about what you mean by 1)? 

    Are you asking for a way to "hide" a column proactively from being used as a filter when defining a segment? Or are you asking for a sort of indicator variable that you could send to a destination indicating of a particular column was used in the segment definition? (I'm assuming "filter" refers to Audience Hub segments but let me know if Im' wrong). 

    And thank you for the feedback on access controls in #2. We're definitely working on some improvements on this front.

  • David Klein User

    re: 1) The purpose of the proposed dataset column attribute would be so that I can make a field available for syncing to a destination but not have it visible as an option for building a segment. This would allow an admin to hide columns that aren't relevant for segment building but allow them to still have them available when syncing to a destination.

    Also, is there a way to reference a segment from the source DB? I know that you offer the SQL for the segment but the issue with referencing the SQL is if someone changes the segment definition then I wouldn't have the proper universe of contacts. I ask because a potential workaround to #1 would be to create a custom sql query that I can sync that is derived from a segment definition.

  • Sean Lynch Fivetranner

    Understood, thanks for clarifying!

    To your second question, if you'd like to access the raw SQL, you can do that programmatically via our API: https://fivetran.com/docs/activations/rest-api/api-reference/workspace-apis/sources/segments/fetch-segment. You're right that you'd occasionally need to re-query to update the SQL definitions. 

    Alternatively, if you don't need the SQL definition itself, you can also set up an activation sync from your segments to write the resulting members of your segment back into your warehouse so you can build on them there.