IntegrationHub ETL & how to handle assets?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hey-oh! So it seems that ServiceNow decided to remove alm_asset from "glide.identification_engine.non_cmdb_tables" - property Why was "alm_asset" is removed from the system property "glide.identification_engine.non_cmdb_table… .
Raised a case to HI to find out what's the way we're supposed to update assets on CMDB integrations from now on :
One of my colleagues created a solution that passes the asset parameters from ETL to Flow designer and we handle the updates in that manner but i would've thought that ServiceNow had an OOB solution prepared before removing the possibility to update asset fields from ETL.
Interested on hearing how the community has tackled this issue!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @KN ,
I believe this approach has been implemented in ServiceNow to prevent ownership conflicts and address certain technical considerations. At present, from KB , it is clear- there is no alternative.
"the alm_asset table is owned and managed by the IT Asset Management (ITAM) team, and IRE is not the recommended method for ingesting data into this table.
IRE team does not maintain the alm_asset table, and the ITAM team has requested that clients not use IRE for data ingestion into this table, citing concerns about the impact on their process scalability"
