Problem: Data set names aren't user friendly in hindsight
Example: Data set name = GreatData and I do a prep step and it defaults to "GreatData_prepared" which is fine, but later I decide this is the "final data set" that should be used by others and I'd like a more intuitive name. I understand changing data set names is not recommended.
Solution: Can we have an alias name for data sets? Then I could create an alias for this data set called "User_Demographics" or "Final_GreatData" or "Dashboard_GreatData" etc. Then allow for an alias name view in the flow?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.