Reltio Connect

I understand that the Crosswalk Source System name is intended as part of the equivalent of a relational DB primary key.

Unfortunately, in order to get the required Survivorship behavior leveraging Source System we will likely be need to change the Source System name for the same value in some cases in order to get the required OV's. (There is a separate Community Post for the Survivorship Issue).

Is there anyway to do an actual update of the Source System Name, much as would be done for updateDate or deleteDate such that Survivorship would leverage the revised name and also any Generator provided values would remain the same, along with all other attributes?

I know we can delete the crosswalk or create a "duplicate" with the same ID  value, but different source system but do not want to create additional duplicates and also have to deal with additional crosswalks approach configuration limits and the loss of previously created values via the Generator.

Thanks,

Mark

I don't think changing a source name is allowed for an entity, however you can try reposting the data along with generator value with contributor provider crosswalk which would associate your existing data points within same entity but with a new source name and see if that works out for your use case.

I understand that the Crosswalk Source System name is intended as part of the equivalent of a relational DB primary key.

Unfortunately, in order to get the required Survivorship behavior leveraging Source System we will likely be need to change the Source System name for the same value in some cases in order to get the required OV's. (There is a separate Community Post for the Survivorship Issue).

Is there anyway to do an actual update of the Source System Name, much as would be done for updateDate or deleteDate such that Survivorship would leverage the revised name and also any Generator provided values would remain the same, along with all other attributes?

I know we can delete the crosswalk or create a "duplicate" with the same ID  value, but different source system but do not want to create additional duplicates and also have to deal with additional crosswalks approach configuration limits and the loss of previously created values via the Generator.

Thanks,

Mark

Ashish,

I appreciate the suggestion and you are correct that a new crosswalk created does keep the generator value passed in instead of taking the next value.  In fact the next value is not even incremented, so we wouldn't be artificially increasing the generated values.

This does address one of the concerns I raised but would still require alot of effort on our side and overhead to accommodate change in source system were we to go that way.

Much appreciated.

Thanks,

Mark

I don't think changing a source name is allowed for an entity, however you can try reposting the data along with generator value with contributor provider crosswalk which would associate your existing data points within same entity but with a new source name and see if that works out for your use case.

I understand that the Crosswalk Source System name is intended as part of the equivalent of a relational DB primary key.

Unfortunately, in order to get the required Survivorship behavior leveraging Source System we will likely be need to change the Source System name for the same value in some cases in order to get the required OV's. (There is a separate Community Post for the Survivorship Issue).

Is there anyway to do an actual update of the Source System Name, much as would be done for updateDate or deleteDate such that Survivorship would leverage the revised name and also any Generator provided values would remain the same, along with all other attributes?

I know we can delete the crosswalk or create a "duplicate" with the same ID  value, but different source system but do not want to create additional duplicates and also have to deal with additional crosswalks approach configuration limits and the loss of previously created values via the Generator.

Thanks,

Mark