Skip to main content
Open

Add the ability to edit a related record from the C360/R360

Related products:CS C360 & R360 & P360
sai_ram
andreammelde
  • sai_ram
    sai_ram
  • andreammelde
    andreammelde

jordan_cook
  • Contributor ⭐️⭐️⭐️⭐️
  • 45 replies

We are currently onboarding approximately 25 different product teams to our instance of Gainsight. We have decided, rather than to add dozens of custom fields to the relationship table for each product team, that we will create a custom low-volume object (as needed) for each team. This only adds one additional field to the Relationship object, and keeps things cleaner.

The problem now is that users don’t know where to go to edit their data. If it’s a “standard field”, they make changes on the attributes page. But if it’s one of their custom fields, they have to navigate to the related list, open the related record in edit mode, and update the data there.

This is not an ideal experience. Users have to remember which fields are located on each object, and then navigate and edit accordingly. 

Since these objects have a 1:1 relationship with the Relationship object, we are requesting that those fields are also able to be edited from the R360 attributes page. So in essence, any time a relationship (or Company) looks up to another low-volume object, Gainsight would allow fields on that object to be made editable on the R30/C360 layout. I believe it already works this way when you need to edit a Company-level field from the R360.

4 replies

Azad
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 95 replies
  • August 30, 2022
Updated idea statusNo StatusAcknowledged

matthew_lind
Forum|alt.badge.img+11
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 650 replies
  • August 30, 2022

I’m behind this idea, @jordan_cook , for exactly the reasons you explain:

  1. Larger tenants with lots of teams that have diverging datasets and
  2. A desire not to saddle Standard objects like Company or Relationship with excessive custom fields

I pondered using a Related Record and decided against it precisely because of the confusion around editing that Related Record. In my case, I did saddle Company with the custom fields, but then again I didn’t have 25 teams arriving either.


jordan_cook
Forum|alt.badge.img+2
  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • 45 replies
  • August 30, 2022

Yes @matthew_lind, this was exactly the discussions we had internally. Each product team comes in with their own spreadsheet with way too many fields to add to the Relationship table. The latest team, for example, had a spreadsheet that went all the way to column HO. No Joke. We compromised and brought in only about 50 new fields to a custom table. There is no way the Relationship object should handle 50 fields x 25 teams.


jordan_cook
Forum|alt.badge.img+2
  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • 45 replies
  • February 15, 2023

My team is begging me for this again today. Editing records on a low-volume table (that is not one-to-many) is super kludgey. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings