Problem
After cloning a tenant in Reltio, you may observe that potential matches are visible when viewing an individual entity in the Reltio UI but are absent from the Potential Matches facet on the dashboard.
Solution
This discrepancy arises because the potential matches index may not be fully rebuilt during the cloning process. To resolve this, you should execute the Potential Matches Reindex Task, which reindexes potential matches information from scratch using the match tables.docs.reltio.com+1support.reltio.com+1
Execution Steps:
-
Initiate the Potential Matches Reindex Task:
Send a POST request to the following endpoint:
POST {ApplicationURL}/api/{tenantId}/rebuildpmcounters
Replace {ApplicationURL} with your Reltio application URL and {tenantId} with your tenant ID.
-
Optional Parameters:
-
distributed: Set to
trueto run the task in distributed mode. Default isfalse.docs.reltio.com+4docs.reltio.com+4docs.reltio.com+4 -
taskPartsCount: Specifies the maximum number of sub-tasks for distributed execution. Applicable only when
distributed=true.docs.reltio.com+2docs.reltio.com+2docs.reltio.com+2 - filter: Enables filtering by a condition to reindex potential matches for specific entities.docs.reltio.com+3docs.reltio.com+3support.reltio.com+3
For example, to run the task in distributed mode with 4 sub-tasks:
POST {ApplicationURL}/api/{tenantId}/rebuildpmcounters?distributed=true&taskPartsCount=4 -
distributed: Set to
Additional Considerations:
- Dashboard Configuration: Ensure that the Potential Matches facet is properly configured in your dashboard layout using the UI Modeler. For guidance, refer to the documentation on Configuring the Potential Matches facet in Dashboard Layout.docs.reltio.com+1community.reltio.com+1
-
Post-Cloning Tasks: After cloning a tenant, it's advisable to run consistency tasks such as
PotentialMatchesReindexTaskto ensure all indexes are correctly rebuilt.support.reltio.com
References:
Comments
Please sign in to leave a comment.