Duplicate change numbers created.

[mmr]

Hi Team,

We have faced one issue in change management, duplicate change records created when user created a new change by copying it from another change. When we checked in the logs, there was nothing logged in the log related to the duplicate change numbers related issue. Please assist if there was any particular reason there behind this duplicate numbers creation.

[sachin_namjoshi]

Do these changes have same sys_id? They should have different sys_id

By default we do not enforce "number" column to be unique, which means you can end up with duplicate numbers. Forcing unique (in the Dictionary record for "Number" column) should be done after careful consideration as if you already have duplicates it will not work.

Regards,

Sachin

[mmr]

They have different sys_id's. Can we implement the uniqueness by marking the Unique checkbox in the field dictionary? If we enable it, will it cause any other issues, for ex: while importing data into the tables as this number field is from the task table?

[Goran WitchDoc]

You got something else that is buggy. This isn't how it should work OOB. solving some bug/customization but another customization is going down the dark hole...

//Göran

[Allen Andreas]

I've already commented and said basically this exact same thing initially. Most do not enable unique through dictionary (due to other possible issues) and instead follow the BR method as is described in the documentation from SN that I linked you to.

However, to Goran's point, that may solve the one issue, but something else is going wrong here.

[sachin_namjoshi]

You can enable unique dictionary for change_request table.

I implemented same in various implementation and i didn't find any issues.

Regards,

Sachin