Duplicate auto-numbering generation in filed configured as number maintenanceIssue Duplicate Configuration Item ID generation in cmdb_ci table. The field "CI ID" is configured as Number maintenance.ReleaseLondon Patch 6CauseThe CMDB Configuration Item import from the data source encountered a problem where an existing record of the type 'cmdb_ci_win_server' already existed.The source table "u_virtual_machine_host" received the Configuration Item ID from the data source and mapped it to the 'u_ci_id' field on 'cmdb_ci_esx_server'.The 'coalesce' option was activated on the 'u_ci_id' field, but the import set couldn't merge the field due to differences in class, resulting in new ESX records being created with the same 'u_ci_id'.ResolutionThe data source must not have the Configuration Item ID field. The Configuration Item ID field has been set up as Number Maintenance and will generate a unique number automatically.However, the Number Maintenance feature does not ensure uniqueness, so a business rule must be configured according to the Enforcing unique numbering provided to prevent duplicate number maintenance.Related LinksAdd auto-numbering records in a table