Skip to main content
  • Home
  • Ideas
  • Honoring dependencies on the picklists values from Salesforce
New Idea

Honoring dependencies on the picklists values from Salesforce

Related products:None
meenal_shukla
In Salesforce, there is an ability to apply configurable dependencies on a field - if the opportunity type is 'Renewal', then in the forecast picklist field, just show relevant fields such as 'At Risk', 'Renewal will happen', 'Will churn' vs. if the opportunity type is 'New Business, just show 'Upside', 'Commit', 'Close' etc in the forecast picklist field. When we pull these fields into the linked objects, we lose these dependencies, and therefore the user can see all the available values in picklist. How can I enable user to see only relevant values in this picklist in the linked object?
Outplay. Outwit. Outlast.

    6 replies

    H
    Forum|alt.badge.img+1
    • hitesh_sharma
    • Gainsight Employee ⭐️
    • 213 replies
    • March 28, 2018
    Hi Meenal,

    For the Dependent picklist to work in layout, make sure to add them in same group and one under the other (Opportunity type in top and Forecast picklist below that)

    Let me know if this helps.

    Regards,
    Hitesh
    hardik_mota
    Forum|alt.badge.img+4
    • hardik_mota
    • Helper ⭐️
    • 85 replies
    • June 28, 2018
    This reply was created from a merged topic originally titled Field dependencies in C360 are not being filtered as per 'customer info' object f....

    In C360 section, client is expecting that based on the selection in ‘Churn Risk Category’ which is the ‘controlling field’, the values available for selection in ‘Churn Risk Reason’ would be filtered based upon how we set up the field dependency in customer info object. This works fine when we preview the Customer Info record in Salesforce, but when we go through the C360 interface, we see the all picklist values in the dependent field ‘Churn Risk Reason’ regardless of what is chosen in the controlling field Churn Risk Category.

    Here’s video recording link to understand the requirement : https://cl.ly/1W3H3T0I3l0g

    So user is requesting to post as an enhancement request where the dependency filters should be applied on C360 page as well to avoid any unexpected picklist to be selected.
    Hardik
    sai_ram
    1 person likes this
    • sai_ram
      sai_ram
    M

    Hello everyone, thank you for bringing this up. We have planned to provide this enhancement in the near future. We will update you once the enhancement is shipped.

    cmultanen
    Forum|alt.badge.img+1
    • cmultanen
    • Helper ⭐️
    • 267 replies
    • September 28, 2020

    +1, any updates on this? 

    carolyn_dibuono
    Forum|alt.badge.img
    • carolyn_dibuono
    • Contributor ⭐️⭐️⭐️
    • 13 replies
    • October 28, 2020

    @muralikrishnagopu is there an update on ETA? Also, will this apply to ALL field dependencies built on Gainsight objects (for example CTA) or just account/customer info?

    sai_ram
    1 person likes this
    • sai_ram
      sai_ram
    R
    Forum|alt.badge.img
    • rakesh_lingala
    • Helper ⭐️⭐️⭐️
    • 281 replies
    • July 27, 2021

    Hello Everyone!

    I’m happy to announce that your request has been partially implemented in both NXT and SFDC versions of Gainsight. 

    Gainsight now honors picklist field dependencies in C360 layouts. When CSMs select the value of a dependent field in the C360, the available options are based on the controller field’s selection. For more information on dependent picklist fields, refer to the Dropdown List and Multi Select Dropdown List (SFDC) article.

    Thanks!

    Reply


    Terms & ConditionsCookie settings

    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