Is there a reason we can't edit standard fields, particularly in the Company object? For example, renaming ARR is not possible, but it is in the Customer Info object of course. So my customer renamed it to Annual Account Value in Customer Info and wants to reflect that same naming convention in the Company object to avoid unnecessary confusion.
This hopefully can be added to Data Designer and to Success plans. Data designer creates system fields however possible from the data designer we should have the ability to add the description.
For success plans I would say from the success plan editor we should be able to make those changes.
This hopefully can keep the integrity of the data management feature and “field name” where these objects are still system objects and can not be edited for upgrade purposes.
I don’t understand why this is marked as Not planned? It’s unquestionably a step backward from what we were able to do with the Customer Info object. If you’re not going to let us change the name, then at least let us delete these out of box fields so that they don’t cause confusion. This is a big Admin Quality of Life thing.
I’d like to raise this again. I think bare minimum we should be able to hide the field, but Data Management doesn’t even let us do that (see below screenshot)! Our use case is that my org is renaming themselves “CSMs” for this coming year. I have a ton of workflows/reports/etc that are tied to our current lookup field, so moving everything to the out-of-box “CSM” field is not an option. But if I relabel it to “CSM” or “Customer Success Manager”, then it will cause confusion for many people because we’re apparently stuck with the out-of-box field.
Bumping this up. We recently rebranded our “CSMs” to “CGAM’s” and was asked to replace all “CSM” field titles. I asked if support could do this from the backend but was declined. Looks like now I’ll have to create a brand new field and manually replace all 500+ dependancies.. It would be great if there was any way to retitle these fields.
Yeah it’s either do that or painstakingly update every end user-facing report, global filter, etc. @pkidd. Not fun at all either way.
@Shilpa Gumnur - this really needs to be reconsidered. As I mentioned in my original post SIX YEARS ago, we were able to rename fields in the Customer Info object in Salesforce, so we’ve actually lost parity the entire time we’ve been on NXT. It’s not like we’re asking for API names to change. Why exactly is this such a hard thing to change?
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.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select.
+3
+4
+1
+12