Simpler Ability to View Low Volume Object on the C360

 @gunjanm Related report is a report configuration in C360. So ‘hide in reporting’ option should suffice. 

There was a fix on making the fields alphabetical on the low volume object UI but there’s a lot more functionality that would make this object type more usable in the front-end. The ticket below was implemented but it only made the fields appear in alphabetical order. 

I would prioritize the front-end experience for users. If we can make this better for end-users, that would help at least make this more functional. 

 

@ssamarth that really does not suffice. The hide in reporting function applies to everything, meaning I can no longer populate data via Rules Engine either, nor can I use it to display in other reports. 

Hi 

We have added Layouts capability to our objects that would solve the usecases mentioned

1. Field level access permissions (Hide/Edit)
2. To be able to better order and group fields together.
3. Ability to create or use sub-headers
4. Resize fields to suit RTA Fields

There are other feedbacks here that we will continue to analyze

1. GSID fields to allow Edit. This is a technical limitation right now. Will look at other possible options
2. Look up field improvements

Thank you

Preethi

@pgeorge is there more information you can provide on these capabilities and the timeframe? 

Echoing here. Is this new capability already released? Any caveats or support articles around it?

@Robert_DeLaO @gunjanm 

These capabilities have not yet been released. We have them in our roadmap and will share you the timelines when they are ready.

Thank you 

Preethi

any update on this? @GameChangerAdmin @anirbandutta 

Running into this just now myself.

First, the existing Support Documentation does not tell you that the GSID field is required in order to make a record editable, so I spent about 30min on Support chat trying to figure out how to make my record editable.

After finding out I needed the GSID for the record, I was really disappointed. Gainsight is normally a very user friendly product, and this functionality negates that experience. For a user to need to see a GSID field, that is not relevant to them and only clutters the experience, really makes this functionality unusable for me at a large organization where I’m enabling and supporting 100+ users on Gainsight.

Please remove this requirement to make Gainsight a more user-friendly experience for CSMs.

Did this behavior change? It seems that removing the gsid does not remove the add/edit ability anymore. Is it now available by default? And if so, is there a way to remove add/edit ability?