Hi Kumar,
In order to get a CSV extract of values only from a single (or each) crosswalk, you need to look at the ROCS utilities that Reltio provides as-is.
Here is their (very small) page of documentation about the various ROCS utilities available:
https://docs.reltio.com/addonutilities/aboutaddons.htmlYou would need to click on each one to see the bit of additional documentation on each one individually on bitbucket. Here is the Data Extract utility that you specifically want to use:
https://bitbucket.org/reltio-ondemand/util-dataextract/src/master/By default it will give all values contributed from each of the crosswalks, with a single row for each crosswalk. You can add a parameter in the file to only include the source you are specifically interested in. You can also include a filter parameter to filter the initial export by (just like you would filter your exports by using the REST APIs in Postman and such). However, this export pays no attention to the OV=true or false. If a crosswalk contributed a value, it will be included, regardless of whether is was a surviving value or not. Also, this extract will always include a single value for each attribute that you list in the attributes file. If you might have more than 1 value from the crosswalk, then you will need to list it as lastName=3, but then you will "always" have 3 columns which are labeled lastName.1, lastName.2, lastName.3. There is no concept of "exploded" format like there is in the export APIs, so you would need to normalize that data yourself if that is something you need. I wrote a small Python script to do that for myself before loading it into a table. Others on my team have just loaded it into a database table as-is and then done the normalization using SQL into another table.
There are some seemingly undocumented parameters that can be used in these ROCS utilities, and unfortunately Reltio doesn't provide any support for the ROCS utilities, so it can take a bit of searching. Sometimes you need to search through the other utilities which the one you are using is dependent upon, like the "extract" utility is dependent upon the "export" utility.
All of the above is assuming that you need everything that is contributed (OV or not) by the crosswalk in question. However, if you are needing to see what the entity looked like before the merge, then you need to use the Get Entity API with the "time" query parameter instead, which just gives you the JSON of a single entity, like this:
GET {{tenantUrl}}/reltio/api/{{tenantId}}/entities/:entityID?time=1651622400000
https://docs.reltio.com/entitiesapi/getentity.html?hl=time
However you would need to know the ID of the entity from before the merge, if that crosswalk was not the "winner" of the merge. To find that, you can manually look it up on the History tab of the Profile page. Or you can use the merge report, which is another ROCS utility, which will give you these values (along with any other attributes you request: from the winner and loser before the merge. However, you have to search by the time range when the merge occurred.
"golden_Uri","win_Uri","lose_Uri","MergeRule","MergeReason","MergeUser","MergeTime","CreateTime"
Or you can export from the activities log API:
https://docs.reltio.com/activitylogapi/activitylogapi.htmlKind regards,
Trisha Miller
Dexcom