Hello Utsa,
Increasing the limit is not recommended as it can create implications to performance (loading, search, match, etc.) and UI user experience. The payloads can also get significantly large and become difficult to handle/process downstream.
If not completed already, it is recommended to profile the entities that are being impacted by the limit and understand why the count is so high. In most cases, it is due to bad quality data or "test" profiles that should be cleaned up prior to loading into Reltio as well as only affecting a fractional (<1%) of the overall dataset.
The attribute configuration should also be reviewed to determine if the matchFieldURIs
parameter is configured correctly. There may be an opportunity to merge nested object together to reduce the count of total objects.
If you have completed the above steps and still believe there is a legitimate use case for increasing the limit, a support ticket should be raised for Reltio review. The use case should be documented along with profiling results of how many entities are impacted by the limit and the business impact of not being able to store the high volume data.
------------------------------
Bryant Barrenechea
Solution Architect | Professional Services
------------------------------
Original Message:
Sent: 09-27-2024 08:17
From: Utsa Das
Subject: Increase the limit of total nested Attribute for an entity
Hi ,
While loading the data through data loader we observed that for an entity maximum 1000 of a specific nested attribute can be added and anything beyond that are being rejected with the below error :-
Main Entity with crosswalks: will exceed Attribute values limit for the '<Nested Attribute URI>' attribute after we apply all changes from the request body. Limit: 1000, value to save: 1001.
Please let us know how we can increase this count so that we can have more nested attributes can be added for a particular entity .
------------------------------
Utsa Das
Novartis
------------------------------