Reltio Connect

I have a generator configured for my Master Data Id field.

Now, I try editing the profile by updating the Name attribute:

Once, I hit the Save, this is what happens:

This is how the configuration of Master Data Id is specified in L3.

{	"label": "Master Data ID",	"name": "masterDataID",	"type": "String",	"hidden": false,	"important": false,	"system": false,	"faceted": false,	"searchable": true,	"autoGenerated": true,	"generator": "SEQ_MasterDataId",	"autoGenerationPattern": "{value}",	"generateIfEmpty": true,	"generateIfNotEmpty": false,	"generatedValueUniqueForCrosswalk": false,	"attributeOrdering": {	    "orderType": "ASC",	    "orderingStrategy": "LUD"	},	"uri": "configuration/entityTypes/ReferenceDataList/attributes/masterDataID",	"skipInDataAccess": false}

I don't want this to happen. I don't need the generator to create an id every time. Please advise.

@Chris Detzel, @Gino Fortunato, @Matthew Gagan, @Saurabh Agarwal, @Karthik Thomas, @Sergio Abraham,

Sorry for pulling you all. This is turning out to be a critical miss. Can we please look into this on priority?

I have a generator configured for my Master Data Id field.

Now, I try editing the profile by updating the Name attribute:

Once, I hit the Save, this is what happens:

This is how the configuration of Master Data Id is specified in L3.

{	"label": "Master Data ID",	"name": "masterDataID",	"type": "String",	"hidden": false,	"important": false,	"system": false,	"faceted": false,	"searchable": true,	"autoGenerated": true,	"generator": "SEQ_MasterDataId",	"autoGenerationPattern": "{value}",	"generateIfEmpty": true,	"generateIfNotEmpty": false,	"generatedValueUniqueForCrosswalk": false,	"attributeOrdering": {	    "orderType": "ASC",	    "orderingStrategy": "LUD"	},	"uri": "configuration/entityTypes/ReferenceDataList/attributes/masterDataID",	"skipInDataAccess": false}

I don't want this to happen. I don't need the generator to create an id every time. Please advise.

Hi Nidheesh,

I would advise you to log a Support ticket with Reltio providing details of your issue with the sequence generator. It would be a more structured and efficient way of finding an RCA for your issue.

@Chris Detzel, @Gino Fortunato, @Matthew Gagan, @Saurabh Agarwal, @Karthik Thomas, @Sergio Abraham,

Sorry for pulling you all. This is turning out to be a critical miss. Can we please look into this on priority?

I have a generator configured for my Master Data Id field.

Now, I try editing the profile by updating the Name attribute:

Once, I hit the Save, this is what happens:

This is how the configuration of Master Data Id is specified in L3.

{	"label": "Master Data ID",	"name": "masterDataID",	"type": "String",	"hidden": false,	"important": false,	"system": false,	"faceted": false,	"searchable": true,	"autoGenerated": true,	"generator": "SEQ_MasterDataId",	"autoGenerationPattern": "{value}",	"generateIfEmpty": true,	"generateIfNotEmpty": false,	"generatedValueUniqueForCrosswalk": false,	"attributeOrdering": {	    "orderType": "ASC",	    "orderingStrategy": "LUD"	},	"uri": "configuration/entityTypes/ReferenceDataList/attributes/masterDataID",	"skipInDataAccess": false}

I don't want this to happen. I don't need the generator to create an id every time. Please advise.

Hi @Karthik Thomas. Yes. We are yet to get access to the Reltio Support portal. But need to resolve this impediment without causing delays.

Hi Nidheesh,

I would advise you to log a Support ticket with Reltio providing details of your issue with the sequence generator. It would be a more structured and efficient way of finding an RCA for your issue.

@Chris Detzel, @Gino Fortunato, @Matthew Gagan, @Saurabh Agarwal, @Karthik Thomas, @Sergio Abraham,

Sorry for pulling you all. This is turning out to be a critical miss. Can we please look into this on priority?

I have a generator configured for my Master Data Id field.

Now, I try editing the profile by updating the Name attribute:

Once, I hit the Save, this is what happens:

This is how the configuration of Master Data Id is specified in L3.

{	"label": "Master Data ID",	"name": "masterDataID",	"type": "String",	"hidden": false,	"important": false,	"system": false,	"faceted": false,	"searchable": true,	"autoGenerated": true,	"generator": "SEQ_MasterDataId",	"autoGenerationPattern": "{value}",	"generateIfEmpty": true,	"generateIfNotEmpty": false,	"generatedValueUniqueForCrosswalk": false,	"attributeOrdering": {	    "orderType": "ASC",	    "orderingStrategy": "LUD"	},	"uri": "configuration/entityTypes/ReferenceDataList/attributes/masterDataID",	"skipInDataAccess": false}

I don't want this to happen. I don't need the generator to create an id every time. Please advise.

Hi Nidheesh,

Try setting the "generatedValueUniqueForCrosswalk" to true. If true, and the object already has an existing  generated value by the crosswalk as in request, the existing value  will be reused instead of generating a new one.

Also, you can refine your survivorship for the generated value to let the oldest generated value to be OV

I hope that helps

Thanks 

Hi @Karthik Thomas. Yes. We are yet to get access to the Reltio Support portal. But need to resolve this impediment without causing delays.

Hi Nidheesh,

I would advise you to log a Support ticket with Reltio providing details of your issue with the sequence generator. It would be a more structured and efficient way of finding an RCA for your issue.

@Chris Detzel, @Gino Fortunato, @Matthew Gagan, @Saurabh Agarwal, @Karthik Thomas, @Sergio Abraham,

Sorry for pulling you all. This is turning out to be a critical miss. Can we please look into this on priority?

I have a generator configured for my Master Data Id field.

Now, I try editing the profile by updating the Name attribute:

Once, I hit the Save, this is what happens:

This is how the configuration of Master Data Id is specified in L3.

{	"label": "Master Data ID",	"name": "masterDataID",	"type": "String",	"hidden": false,	"important": false,	"system": false,	"faceted": false,	"searchable": true,	"autoGenerated": true,	"generator": "SEQ_MasterDataId",	"autoGenerationPattern": "{value}",	"generateIfEmpty": true,	"generateIfNotEmpty": false,	"generatedValueUniqueForCrosswalk": false,	"attributeOrdering": {	    "orderType": "ASC",	    "orderingStrategy": "LUD"	},	"uri": "configuration/entityTypes/ReferenceDataList/attributes/masterDataID",	"skipInDataAccess": false}

I don't want this to happen. I don't need the generator to create an id every time. Please advise.

Nidheesh, you were missing a survivorship rule for your generated ID.  I have set one up in your PoC to retain the oldest value.

Also, your comment stated "every edit mode".  Your existing data were imported using an externally identified source and ID for their crosswalks.  When you edit using the UI you are adding a Reltio crosswalk, which will cause an ID to be generated on behalf of that crosswalk.  The survivorship rule retains the original auto ID.  Any subsequent edit of that profile via the UI will not cause any more IDs to be generated.

Hi Nidheesh,

Try setting the "generatedValueUniqueForCrosswalk" to true. If true, and the object already has an existing  generated value by the crosswalk as in request, the existing value  will be reused instead of generating a new one.

Also, you can refine your survivorship for the generated value to let the oldest generated value to be OV

I hope that helps

Thanks 

Hi @Karthik Thomas. Yes. We are yet to get access to the Reltio Support portal. But need to resolve this impediment without causing delays.

Hi Nidheesh,

I would advise you to log a Support ticket with Reltio providing details of your issue with the sequence generator. It would be a more structured and efficient way of finding an RCA for your issue.

@Chris Detzel, @Gino Fortunato, @Matthew Gagan, @Saurabh Agarwal, @Karthik Thomas, @Sergio Abraham,

Sorry for pulling you all. This is turning out to be a critical miss. Can we please look into this on priority?

I have a generator configured for my Master Data Id field.

Now, I try editing the profile by updating the Name attribute:

Once, I hit the Save, this is what happens:

This is how the configuration of Master Data Id is specified in L3.

{	"label": "Master Data ID",	"name": "masterDataID",	"type": "String",	"hidden": false,	"important": false,	"system": false,	"faceted": false,	"searchable": true,	"autoGenerated": true,	"generator": "SEQ_MasterDataId",	"autoGenerationPattern": "{value}",	"generateIfEmpty": true,	"generateIfNotEmpty": false,	"generatedValueUniqueForCrosswalk": false,	"attributeOrdering": {	    "orderType": "ASC",	    "orderingStrategy": "LUD"	},	"uri": "configuration/entityTypes/ReferenceDataList/attributes/masterDataID",	"skipInDataAccess": false}

I don't want this to happen. I don't need the generator to create an id every time. Please advise.