Bring back the ability to edit field types in Data Management

Related products: CS Data Management & Integrations

Prior to data management being “horizon-ized,” we were able to edit field types in data management as long as there were no dependencies on that field - i.e. if I was setting up an object and accidentally saved a field as a number instead of a string, I could easily go back and change it as long as I hadn’t sourced that object yet in reports, rules, etc. 

 

Now, though, that ability to edit has annoyingly disappeared. My use case is that I used a CSV to set up an object because it had about 30 fields. So Gainsight guesses what my field types are, and it’s up to me to fix them as needed. I accidentally saved too early though and was unable to edit about 5 fields that were wrongly classified. My only options were to delete each individual field and re-add them one-by-one or just delete the entire object and re-load the CSV.

 

Both options are a poor user experience, and, more importantly, are a step backward from what we used to be able to do. Please consider bringing this functionality back.

I am genuinely curious how the decision was made to note only remove this key functionality for #AQOL, but also not call it out on this support article: https://support.gainsight.com/Gainsight_NXT/02Data_Management/About/Data_Management_Change_Document 

The dependency work this creates is unbelievably large.

Generally, a lot of changes to functionality like this leave us as admins and ops leaders in a state of shock when we plan capacity accordingly to what we know to be historically possible, commit to the work, set timelines with our stakeholders, and then have to say, “never mind, it’s gonna take way longer...and it’s because of the product.” This breeds mistrust in the platform.


I am genuinely curious how the decision was made to note only remove this key functionality for #AQOL, but also not call it out on this support article: https://support.gainsight.com/Gainsight_NXT/02Data_Management/About/Data_Management_Change_Document 

The dependency work this creates is unbelievably large.

Generally, a lot of changes to functionality like this leave us as admins and ops leaders in a state of shock when we plan capacity accordingly to what we know to be historically possible, commit to the work, set timelines with our stakeholders, and then have to say, “never mind, it’s gonna take way longer...and it’s because of the product.” This breeds mistrust in the platform.

Especially when admins, such as myself, explicitly ask if functional parity between new/old versions will be maintained and we receive an unequivocal “yes of course it is”, and then we have to find out on our own through trial and error that is not in fact the case.


Ran into this yesterday, and wound up having to delete the field and add a new one to accomplish.  Definitely not ideal.


I’ve only ever worked in Horizon, and when I came across this need, was surprised the functionality didn’t exist! Especially would love the ability to upgrade from a picklist to multi picklist!


I’ve only ever worked in Horizon, and when I came across this need, was surprised the functionality didn’t exist! Especially would love the ability to upgrade from a picklist to multi picklist!

Also ran into this, and would like to point out that it acts like you can change it, but when you save and go back, it stays the same as it was.