Skip to main content

Community

The Trade Desk - Filter Report Schedules to ShowOnlyRequestedByMe

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi Marc,

    Thanks for submitting this feature request. I've added a feature improvement to our backlog for this.

    I see that you set the Schema change handling setting to Block All for your Trade Desk connection. I assume that already prevents new tables that you don't want from being added to your connection. Is there a reason why that solution isn't sufficient? 

    You also mentioned this would help with performance. Is the performance of the connection with your current setup insufficient for your use case? What kind of sync time are you hoping to achieve with this change?

    Thanks in advance for the input. It will help us figure out the priority of this request relative to the other items in our backlog.

    Cheers,
    Luke

     

    Hi Luke,

    Thanks for the response. In the current state, the Block All setting is sufficient for preventing new tables being exported.

    At the time I submitted this feature request, the TTD connector was extracting new tables in every daily sync, even though these tables were not selected in the schema. This was extending the sync by over 3 hours. This behaviour was recently resolved for our connection. The daily sync now extracts only the tables selected in the schema and completes within ~10-15 minutes.

    There are still some scenarios where filtering on ShowOnlyRequestedByMe would be helpful:

    • When configuring a new connection, the schema fetch and initial sync takes much longer than necessary because it scans all accessible tables. Filtering to only my reports would help reduce the initial sync duration. However, my preferred solution here would be what I describe in this other feature request, i.e. allow schema selection before the initial fetch/sync.
    • In an existing connection, making edits to the schema requires scrolling or filtering through potentially thousands of tables. Filtering out reports created by other users would make it easier to manage the schema in the UI.
    • The "Schema changes Last 30 days" count on the connection screen is meaningless because it is continuously incremented by new tables being added to the schema. Our current count is over 5000. The "Send email when a new schema, table, or column is detected" feature would likely trigger daily with irrelevant updates.