Entities – Conditional Fields Based on the Country Standard Field

Learn how to configure custom fields that automatically show or hide based on the country selected for an entity — enabling precise, jurisdiction-specific data models in DiliTrust LEM.

✅ What Is This Feature?

In DiliTrust LEM (Legal Entity Management), it is possible to configure conditional custom fields: fields that appear or disappear depending on the value selected in another field. Until now, this conditional logic only worked with custom list fields.

This feature extends conditional logic to standard fields of type list, starting with the Country field — the most impactful standard field in entity management.

In practice, this means you can now configure custom fields (for example, specific regulatory fields, local legal identifiers, or jurisdiction-specific data) that only appear when a given country is selected for an entity. Fields that are irrelevant for other countries remain hidden, keeping entity forms clean and precise.

⭐ Why Does This Matter?

Country is the cornerstone of an entity's data structure. Every jurisdiction has its own legal requirements, and the information needed for a French entity differs significantly from what is required for a German, British, or Singaporean one.

Before this feature, LEM administrators had to use workarounds or accept that all fields would be visible regardless of the country — leading to cluttered forms, confusion for users, and a higher risk of data entry errors.

With this enhancement, your entity configuration templates can now be fully context-aware:

• Only the fields relevant to the selected country are displayed
• Data entry is faster and less error-prone
• Entity forms reflect the real-world complexity of multi-jurisdictional corporate structures
• Corporate secretaries and administrators can manage more entities more efficiently

✋ Who Is This Feature For?

• LEM Administrators — responsible for configuring entity templates and defining which fields appear in entity forms across different jurisdictions
• Corporate Secretaries — who enter and maintain entity data and benefit from cleaner, more relevant forms tailored to each country

✨ Prerequisites / Getting Started

Before configuring conditional fields based on the Country standard field, ensure the following:

1. You have LEM Administrator access rights in DiliTrust.
2. You are working in the Suite – Setup module, under the Entities configuration section.
3. You have already created (or plan to create) the custom fields you want to conditionally show or hide. These fields must be of a compatible type.
4. The entity template you wish to configure is accessible in your tenant.

✅ Step-by-Step Guide

Follow the steps below to configure a custom field that appears or disappears based on the selected Country.

1. Access the Setup module
   Log in to DiliTrust and navigate to Suite → Setup → Entities.
2. Open the entity template to configure
   Select the entity template or entity type for which you want to define conditional field behaviour.
3. Locate the custom field to make conditional
   In the field configuration panel, find the custom field you want to conditionally display. This is the child field — the one that will appear or disappear.
4. Set the conditioning parent field to "Country"
   In the conditioning settings for that custom field, select Country as the parent (conditioning) field. This is the new capability: previously, only custom list fields could act as parent fields.
5. Select the triggering country value(s)
   Choose one or more country values that should trigger the display of the child field. For example, select France if the field should only appear for French entities.
6. Save the configuration
   Confirm and save your changes. The conditional rule is now active.
7. Test the behaviour
   Open (or create) an entity and set its Country field. Verify that the configured child field appears only when the correct country is selected, and is hidden otherwise.

For additional context, you can also refer to the existing documentation article on conditional fields: Entities – Conditional Fields Based on Country Standard Field.

✨ Tips & Best Practices

• Start with your most-used jurisdictions: Identify the countries where you manage the most entities and configure conditional logic for those first. This delivers the greatest immediate value.
• Group related fields: If several fields are specific to the same country (e.g., a local registration number, a specific legal form, a tax identifier), apply conditioning to all of them using the same parent Country value. This keeps forms clean for all jurisdictions at once.
• Use descriptive field names: Name your country-specific custom fields clearly (e.g., "SIRET Number (France)") so that administrators can easily understand their purpose when reviewing the configuration.
• Test across multiple countries: After configuring, test entity forms by switching between several countries to confirm that the correct fields appear and disappear as expected.
• Document your configuration choices: Keep an internal record of which custom fields are conditioned on which countries. This greatly simplifies future maintenance and onboarding of new administrators.
• Plan for "default" fields: Fields without any conditioning will always appear, regardless of country. Use this for truly universal fields (e.g., entity name, creation date) and reserve conditional logic for jurisdiction-specific data.

◼ Limitations & Known Constraints

• Country field only (at this stage): This initial release extends conditional logic to the Country standard field only. Other standard fields of type list (such as Legal Forms, Currencies, Mandate Position) are not yet supported as conditioning parent fields. Support for additional standard fields may be introduced in future releases.
• Custom fields as children only: The child fields (those that appear/disappear) must be custom fields. Standard fields cannot currently be used as child (conditioned) fields.
• List-type fields only: The Country field works as a conditioning parent because it is a list-type field. This feature does not apply to standard fields of other types (text, date, number, etc.).
• LEM Administrator access required: Only users with LEM Administrator rights can configure these conditional rules. Corporate secretaries and standard users cannot modify field conditioning settings.
• Existing data is not affected: Applying conditional logic to a field does not alter data already entered. It only affects what is displayed on entity forms going forward.

❓ Frequently Asked Questions

Can I use multiple country values to trigger the same child field?
Yes. When configuring the conditioning rule, you can select multiple country values. The child field will appear whenever any of the selected countries is chosen for the entity.

What happens to data already entered in a conditional field if the country changes?
If an entity's country is changed so that a previously visible conditional field is now hidden, the data entered in that field is retained in the system but no longer displayed on the form. It will reappear if the country is changed back to a triggering value.

Can I condition a field on Country AND another field at the same time?
Please check with your DiliTrust administrator or consult the latest product documentation, as combined (multi-level) conditioning rules may have specific constraints depending on your configuration.

Will this feature apply to all entity templates automatically?
No. You need to configure the conditioning rules manually for each entity template where you want this behaviour. It is not applied automatically across all templates.

When will other standard fields (Legal Forms, Currencies, etc.) support conditioning?
The Country field is the first standard field to support conditioning, as it has the highest impact. Additional standard list fields are on the product roadmap. Contact your DiliTrust account manager for information on upcoming releases.

Do I need to reconfigure existing conditional custom fields?
No. Existing conditional rules based on custom list fields continue to work exactly as before. This feature only adds new capability — it does not change existing behaviour.

Is this feature available on all DiliTrust LEM tenants?
Yes, this feature is available to all LEM tenants as part of the standard platform update. No additional activation is required.