Issue Description
When multiple reference data sets exist for the same field name (for example, Legal Structure Subcategory), the expected List of Values (LOV) may not be displayed correctly in the Map Lookup UI.
Example
For the field Legal Structure Subcategory, the expected LOV
Reference Data Name: Legal Structure Sub-Category (Trust)
is not displayed. Instead, a different LOV such as
Legal Structure Sub-Category ((VCC) – Singapore)
may appear unexpectedly.
Root Cause
When multiple data requirements share the same datakey but reference different lookup lists, the Fenergo SaaS system does not have a deterministic rule to decide which lookup should be prioritised.
As documented in Configuring Policy | Fenergo Document Portal, all requirements that share a datakey point to the same backend data source. When different lookup lists are attached to requirements using the same datakey, the system cannot reliably determine which lookup to return.
As a result, the lookup selection becomes arbitrary, which can lead to incorrect LOVs being displayed in the UI or returned during ETL processing.
Recommended Configuration (Best Practice)
As outlined in the policy configuration guide—particularly for ETL and migration policies—the following best practices should be followed:
Use a single lookup list for all requirements that share the same datakey
Avoid attaching multiple or different lookup lists (such as jurisdictional or regional variants) to the same datakey
Create separate datakeys if differentiation by jurisdiction, region, or business context is required