Question
Customers may report that Data Validation Functions (DVFs) work correctly in the Reltio UI but do not trigger when entities are created or updated via the API.
Answer
| Symptom | Observation |
|---|---|
| DVFs trigger correctly through UI | Errors and warnings appear as expected |
| DVFs not triggered through API | Entities created without validation |
| No error or warning in API response | Entity saved successfully despite invalid data |
| Tenant: Production / API integration flow | High likelihood of parameter omission or misconfiguration |
DVFs are executed by the Logical Configuration Actions (LCA) engine.
By design, API calls must explicitly enable LCA execution using the executeLCA=true query parameter or corresponding header.
If executeLCA is omitted or set incorrectly, the platform skips validation logic for performance optimization.
Common Error Example:
POST https://<env>.reltio.com/reltio/api/<tenantId>/entities?executeLCACorrect Usage
Correct API Syntax
POST https://<env>.reltio.com/reltio/api/<tenantId>/entities?executeLCA=true
Alternate Header-Based Approach
X-Reltio-ExecuteLCA: trueThis ensures that the API execution path mirrors UI behavior and triggers all associated DVFs and LCAs.
Key Takeaway
Always confirm whether executeLCA=true is included in customer API calls when DVFs do not trigger via API.
This single flag determines whether the data validation logic executes on the server.
Comments
Please sign in to leave a comment.