Hi Utsa,
We encountered this problem about 7 months ago as well. In our case the problem originated because our RDM tenant was populated with dependent values e.g. Country RDM values like US and CA had child State RDM values like [AK, CA, DE...] and [AB, BC, ON...] and the MDM tenant's L3 did not have any corresponding dependency declared. To fix the problem we changed the definition for our Location.Country attribute in the L3 to the following (adding "dependentLookupAttributes"):
{
"label": "Country",
"name": "Country",
"description": "The country of the location's postal address",
"type": "String",
"hidden": false,
"important": false,
"system": false,
"faceted": true,
"searchable": true,
"attributeOrdering": {
"orderType": "ASC",
"orderingStrategy": "LUD"
},
"dependentLookupAttributes": [
"configuration/entityTypes/Location/attributes/StateProvince"
],
"uri": "configuration/entityTypes/Location/attributes/Country",
"lookupCode": "rdm/lookupTypes/Countries",
"skipInDataAccess": false
}
Please let me know if this helps.
Regards,
Matt
------------------------------
Matthew Gagan
------------------------------
Original Message:
Sent: 09-17-2024 00:42
From: Utsa Das
Subject: Lookup attributes are coming very late after clicking in the UI
Hi ,
Please let us know is there any resolution for the same.
------------------------------
Utsa Das
Novartis
------------------------------
Original Message:
Sent: 09-14-2024 01:11
From: Utsa Das
Subject: Lookup attributes are coming very late after clicking in the UI
Hi All ,
Please let us know if there any update about the same.
------------------------------
Utsa Das
Novartis