We change blends, tables and transfers often. Sometimes we notice later that a change caused issues with data. It’s not always easy to remember which changes were made to backtrack the problem.
Therefore it would be great if blends, tables, and transfers would automatically create a change history where you can see all changes in configurations, e.g. added/removed metrics and dimensions, changed settings and so on.
+1Thank you so much for taking the time to share this idea!
You're absolutely right - keeping track of configuration changes can be challenging, especially when they impact data down the line. Having an automatic change history for blends, tables, and transfers would definitely be a valuable addition.
This is a great suggestion, and it’s something we’d really like to explore in the future. While we can’t commit to a timeline just yet, feedback like yours plays a big role in shaping our roadmap - and we’d love to reach out for more detailed input when the time comes.
Thanks again!
+6
This could be as simple as logging a user note on the “save changes” popup screen. Use an optional long text form field to let the user describe their change and then expose the comment history somewhere in the interface.
Already have an account? Login
Don't have an account? Sign Up
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.