I was struggling with a rule where the CSV column names didn’t match the names I was setting in the rule (export to S3 enabled) and the response I got from support was that it was intended behaviour adn to submit and idea, so here I am:
FieldAlias is created only once when we save the field for the first time, and if the display name is changed after that, it won't change the field alias again.
It's very common practice to build rules in phases, test, adjust, and once all is working as expected do the final changes, such as field naming (“Display Name”). If you were to troubleshoot something in the future, basically you have to guess which column in the exported CSV you are looking at if at any point in time the Display Name was updated.
Please, can you consider respecting the current "Display Name” as Column Header when exporting to CSV? Currently the only “workaround” is to either delete and re-add with new names before saving, or add a transform to rename and export from there.
Closed (Duplicate)
Set the Display Name as the header of a CSV (rules engine - export to S3)
+7You’d probably be interested in this one as well :)
1 person likes this
+8Thank you
Continuous improvement is better than delayed perfection
1 person likes this
+3The older post is here:
Scott Drost, Gainsight -- Principal Customer Success Architect
1 person likes this
+2Updated idea statusNew Idea→Closed (Duplicate)
Idea merged into:All the votes from this idea have been transferred.
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.