To create a dependent field in Gainsight, here's a step-by-step guide on how to achieve this:
-
Access the Gainsight Administration area and navigate to the object that contains the fields you want to set the dependency on (in this case, the object containing the "Lifecycle" and "Churn Reason" fields).
-
Locate the "Lifecycle" field and click on it to edit its properties.
-
Set up the field dependency by selecting the "Churn Reason" field as the dependent field and the "Lifecycle" field as the controlling field.
-
Specify the conditions for the dependency. In this case, you want the "Churn Reason" field to be required only when the "Lifecycle" field is set to "Contract End".
-
Save the field dependency settings.
-
Now, navigate to the "Churn Reason" field and set it as a required field in its properties. This ensures that when the condition specified in the field dependency is met, the "Churn Reason" field becomes mandatory.
-
Save the changes to the "Churn Reason" field.
With these steps, you have created a dependent field in Gainsight. Now, when users select "Contract End" in the "Lifecycle" field, the "Churn Reason" field will be required, and they will be prompted to fill it out. For other values in the "Lifecycle" field, the "Churn Reason" field will be empty.
The issue here is that when the user selects Contract End in the Lifecycle field, it already submits a sync request to SFDC before even letting them update the Churn Reason field, and then once they update that too, it will send a separate request for that field change too.
Is it possible to make the changes synced together, meaning if the Contract End if selected, the user will need to select the Churn Reason field too and then Gainsigth will submit the sync request to SFDC.