Inserting data into recently renamed Request Item ID field is failing

Products

• CA Service Management - Asset Portfolio Management
• CA IT Asset Manager
• CA Service Catalog

Issue/Introduction

After creating a new field called Request Item ID, data imports using Data Importer are failing

Extended field has string data type, Database Table Name :usp_owned_resource)

If the data importer data file has the value for this field we see the following:

#1. 88888/"88888" - asset created with serial number value, but Request Item ID field is not updated

#2. AAAAA/"AAAAA"  - Failed to convert parameter value from a String to a Int32.

Environment

All versions of Service Catalog

All version of IT Asset Manager

Cause

The extension is created by the field_name  'request_item_id', which is then created on usp_owned_resource table, the extension table for Assets.

However, there is an OOTB field by the same name 'request_item_id' on usm_link_subscription_asset table, the table that links request with the Fulfilled Assets.

Resolution

When an import has to create an asset with a value for extended field like request_item_id (which is a string in this case), the value is being mapped to the OOTB field request_item_id of usm_link_subscription_asset, which is an integer.

We recommend creating a new extended field with a different field_name like z_request_item_id  and use the same in their Import definition mapping.

Something more descriptive than Request ID is advised as this will not conflict with the already existing column.

In practice, it is always recommended to create extensions with a 'z_' prefix in field_name/attribute_name.

After creating a new extension as recommended above, the already created extended request_item_id on the configuration which is conflicting with the OOTB request_item_id need to hidden.

Additional Information

Direct database manipulation is always a sensitive operation so we recommend testing this in a non production environment first.