alm hardware model update

[Royal1]

i want to update the model and model category to the assets in the table alm_hardrare, but these are readonly.

how these fields get updated in the alm_hardrare table?  can we do manual update 

[maroon_byte]

I believe the same would apply regardless of the type of source (Excel or REST API). The Model records are part of your foundation data which should be manually created/uploaded first with respective model categories before you upload data in the Hardware table. See if you can get an extract of model data from the source system and match them word-for-word against model data in your ServiceNow instance.

   "'Model' field on the Hardware record should exactly match with the 'Display Name' of the Model record in ServiceNow."

Regarding your question about relationship between alm_hardware and model table, model record is a reference field on an hardware table. Model info adds to the details/properties of the hardware record. Example: A laptop with serial number B67890 is an HP Elitebook model machine. The laptop goes into your alm_hardware table and the Model field in this table references to the HP Elitebook product model record in the product model table.

[Royal1]

how the model table will get updated ? OOB data or we need to create manually or any plugin data .

i know like we can create the new models, but already existing models , from which source its created in the system?

[Ashok Sasidhara]

Models can be created in the following ways:

1. Directly on the models table via manual entries of individual records or bulk data load by import sets.

2. Models which are present in the 'Model' field for data loads into Asset table and in the 'Model ID' field for data loads into CMDB table (including data populated by discovery or integrations) would create new entries in the product models table if there are no existing entries with the same name (unless the transform map is configured to ignore the creation in this scenario). So it is recommended to use a proper standardized name for each model (aligned with the existing names in product models table) to reduce the chance of duplication. Also the only way to reduce duplication to the maximum extent during automated data population is through the use of content service in HAM pro which will automatically normalize the data for most of the models.