Hi again,
Indeed, there were changes between API versions. But new API works as designed here, and there is no error, simply change of the API functionality and data. If you would like to request a new functionality, please create an idea in
Aha! portal and track the changes there.
Thank you.
------------------------------
Andrei Ionescu
IBM
Bucharest
------------------------------
Original Message:
Sent: Wed February 01, 2023 03:30 AM
From: Andrei Ionescu
Subject: Columns mapping between computer_systems and v2/computers REST API call
Hi York,
There is already a case opened with ILMT Support, once the investigation is done, we'll update both the case and this post.
Thank you.
------------------------------
Andrei Ionescu
IBM
Bucharest
Original Message:
Sent: Tue January 31, 2023 09:08 PM
From: York Ly
Subject: Columns mapping between computer_systems and v2/computers REST API call
Additional information:
The bottom line is to get the "id" column from the computer_systems REST API back to the v2/computers REST API. The v2/computers REST API call will generate the same 3 id information as from the old computer_systems REST API.
------------------------------
York Ly
Original Message:
Sent: Tue January 31, 2023 01:39 PM
From: York Ly
Subject: Columns mapping between computer_systems and v2/computers REST API call
Hi, with regard to this old computer_systems (deprecated) REST API as shown below, the columns mapping of a new v2/computers REST API are now a bit different.
https://www.ibm.com/docs/en/license-metric-tool?topic=deprecated-retrieval-computer-systems
Important: This REST API is planned to be entirely substituted with api/sam/v2/computers REST API. If you have custom tools or internal processes that are based on api/sam/computer_systems REST API, it is best to adjust the tools to use the new version of the API. For information, see: Mapping columns between computer_systems and v2/computers REST API.
According to this mapping link below,
https://www.ibm.com/docs/en/license-metric-tool?topic=mrav-mapping-columns-between-computer-systems-v2computers-rest-api#reference_yqq_2hd_b1b
the "id" from computer_systems is no longer available in v2/computers as it does not map to any thing.
the "computer_id" from computer_systems is now mapped to "id" in v2/computers.
the "computer_remote_id" from computer_systems is now mapped to "bigfix_id" in v2/computers
The issue is since the ServiceNow was initially integrated with ILMT using the computer_systems REST API which captured the "id" from computer_systems REST API, with a new v2/computers REST API, the "id" value is completely different as it is mapped the "computer_id" column from computer_systems REST API. Therefore, it causes some issues with ServiceNow integration where the value of "id" column from v2/computers is no longer able to map the existing "id" value in CMDB because the old value "id" was coming from the old computer_systems which is different value.
I would like to see the same "id" information from the old computer_systems REST API also available in v2/computers REST API. Maybe call it different name or something but at least the information is available in the v2/computers REST API. Please let me know if you need more clarification. The request is to restore/re-add the "id" information from computer_systems back to v2/computers REST API (maybe with a different column name or something).
------------------------------
York Ly
------------------------------