Skip to main content

I use Conga CLM in our org. I have two lines of businesses I am supporting. As of today, I have 4 fields that all follow the dependency chain. The fields are: 

Country -> Org Level -> Category -> Sub-category 

This dependency is set all accross our Agreementg Object. 

 

Our marketing team use these 4 fields and have these dependencies set to support their process. However, I have another department we onboarded recently and they do not like this dependency functionality, however, they would like to use these fields. Specifically, they want to seelct a country, category, and sub-category field, but do not want to use the Org level field. 

 

I tried to default the org level field but it wont default unless a country is selected and it will still require the user to select the org level field. The user now wants this field gone frm the layout but it will not let us select the Category field. 

 

Any suggestions on how to tackle this issue bewteen the businesses and their requirements? 

 

Dependency field discrepancy

 

 

 

#Data Management

1 answer
  1. Feb 28, 2025, 8:36 PM

    Hi @Qasim Mateen,

    I understand the challenge you're facing. Since skipping the Org Level in a dependency chain isn’t supported by Salesforce, your best option may be to create a separate set of fields for the department that doesn’t require the Org Level. This means duplicating the dependency chain (e.g., Country → Category → Sub-category) so that the new team can work independently without disrupting the current setup.

0/9000