Using the ITAM Data Importer to update and existing asset cost record results in an error "Another user updated this record after it was loaded".

Document ID : KB000033166
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

Using the ITAM Data Importer to update an existing asset cost record results in an error "Another user updated this record after it was loaded".

Environment:

Applies to all supported environments for the specified releases.

Cause:

Mapping included an entry for %Version Number% mapped to 'Asset.Cost.Version Number'. This is a system generated value that is incremented by 1 each time the asset is updated in the user interface or by the importer.

The data file for the insert and update have the Version Number set to '0'. The initial insert will be successful creating the cost record since the data file has a Version Number equal to '0'. If a subsequent update only is performed using the same data file,  the update will be successful since the Version Numbers match. The cost record is then incremented automatically to Version Number = 1 after this update.

If subsequent updates are done where the data file and cost record version numbers are out of sync (e.g. Data file = 0 and cost record = 1 ) the import will fail with the resulting error: "Another user updated this record after it was loaded.".

The version number for the cost record and data file need to be in sync for the import to be successful.

Resolution:

You should remove the %Version Number% to 'Asset.Cost.Version Number' mapping since this is a system generated number.