Why Software Model field on Software Model Lifecycle report is empty in SAM Pro

[MercBuilding]

Hi,

  Recently i have created a separate dashboard for Software Owner's for one of the client and added few reports for their reference. In that one of the reports is 'End of Life Products'. The whole dashboard filters the data based on 'product Owner' on Software Model. But for End of Life products, since the Software model is empty, the filtering is not applicable. Just wanted to know why this field is empty ? and can we write a script to populate this field based on publisher, product, version and edition matching on software model? Is it complex to implement and is there any other better way to achieve this.

Thanks!!

[Community Alums]

Hi @MercBuilding ,

Check for any failed reconciliation and in case of reconciliation failure, please check the error logs and fix the reconciliation issue.

Once the reconciliation runs successfully, we should see the "Software Model Result" again in the "Software Installation" table.

[Amritraj]

Hi @MercBuilding,

The "Software model" field is depreciated and in place of the "Software Models" field is brought into place. This has been done to avoid duplicate records. Previously "Software model" field was a reference field and now the newly created field "Software Models" is a list type of field.

PFA URL for reference: Software models 

[MercBuilding]

Hi @Amritraj ,

   Thanks for the reply, but i dont understand why there will be duplicates if we use 'Software Model' with Publisher, product, version and edition matching conditions. Iam trying to populate this field with these matching values, since i want to filter these records based on Product owner. Does ServiceNow has plans to remove these fields in coming versions?

Thanks!!

[Amritraj]

If we have our instance directly in Vancouver and have not upgraded from previous versions, then we will be able to see only the "Software Models" field else case both the "Software Model", and "Software Models fields". fields would be visible 

Another thing is that the Software Model field is a reference type of field and even if you populate this it will contain one single software model, not multiple software models.

This issue we had also been facing and the newly created field Software Models was a list type of field that did not allow dot walking because of which we couldn't get Software Model fields such as asset product owner, software model ID, etc in the Software Lifecycle report table.

If you are looking for some reporting purpose I would suggest you have a software Model and Software Lifecycle Report table combined on database views