Skip to main content
nadav_shemtov
nadav_shemtov
Contributor ⭐️⭐️⭐️⭐️⭐️
January 24, 2017

Gainsight fields should follow field dependencies - choice in one field could limit/set value for another field

  • January 24, 2017
  • 3 replies
  • 67 views
These was raised by several users at HPE: 

The request is to have Gainsight enable dependencies between different fields, specifically on the CTA object. 

Some key examples include having the ability to limit the "Reason" codes that show based on the CTA type (e.g. if CTA type A is chosen, show only reason codes B and C), but this logic can be extended throughout Gainsight fields. 

Is this a planned enhancement?

      3 replies

      manu_mittal
      Gainsight Employee ⭐️
      manu_mittal
      Gainsight Employee ⭐️
      January 24, 2017
      Thanks for sharing, Nadav. Two comments:
      • We are adding the ability to define CTA Reasons, etc. per CTA Type. This should be available in our Winter release.
      • We already honor Salesforce field dependencies. Here's an example where 'Rate this Playbook' values are made dependent on 'Source':
                



                



                

        wayne_baker
        wayne_baker
        Helper ⭐️
        February 17, 2017
        Opening this back up. I am working in the HPE environment and trying to migrate some things off the CTA and into the success plans.

        However, the field dependency is not working there, on the success plan template. This is at the R360.

        In addition to that, we utilize the picklist object a lot with features like this. Making it nearly impossible to set a dependency on them. Is there any plan in the future to have the ability to determine a picklist off a picklist lookup? 
        wayne_baker
        wayne_baker
        Helper ⭐️
        February 17, 2017
        Opening this back up. I am working in the HPE environment and trying to migrate some things off the CTA and into the success plans.

        However, the field dependency is not working there, on the success plan template. This is at the R360.

        In addition to that, we utilize the picklist object a lot with features like this. Making it nearly impossible to set a dependency on them. Is there any plan in the future to have the ability to determine a picklist off a picklist lookup? 
        Terms & ConditionsAccessibility statement