Update existing Objects

4 years ago

Hmm,

the statement from Laura may be misleading.

It depends on what you want to update and whether you want it doable by LM-GUI or by other means:

a) Bulk update (a set of objects) with the SAME change

b) bulk update (a set of objects) with different change for any member of the set.

a) can be done from within the LM-Interface (multi select objects in 'search for <object> reports' then select 'edit...'

b) may be achievable by exporting and then using Home->Import Data-> Update existing <ObjectType>

There are other way in achieving 'updates' as well. E.g.:

c) by Integration Managers 'Snow XML' connector

d) by using Import Service from "Snow License Manager Web Configurator" (see dialog tab 'Import Service' in after starting WebConfigurator.exe)

e) by crafting SQL and DB-Jobs with usage of Snows-StoredProcedures

like e.g. "PROCEDURE [dbo].[LicenseAddUpdate]"

NOTE:

Use of those procedures normally need prior retrieval of the input data needed for this procedure (not only feeding in the updated data) by prior usage of a corresponding 'Get' function/procedure. - e.g. "LicenseGet()"

There are even some 'MultiEditAddUpdate' versions of the object-specific AddUpdate procedures which need to craft a predefined (xml-)structure before.

Usually you need put this into some other sql-logic to do the lookup-/Sync-decision as to what object/attribute needs to be updated as well.

This is 'advanced' stuff and may need involving Snow-ProfServices and/or a skilled Snow-Partner as e.g. apogiz - spoiler: end of selfish advertising, I work for apogiz ;-)

This kind of data update is definitely 'doable' (Albeit not 'out of the box').

We use this approach to e.g. integrate with CMDBs for which snow currently does not provide an 'out-of-the-box' SIM-Connector for and where constant sync/update of snow-objecst are needed.

Expand Post

Community Manager (Flexera Software)
5 years ago
Unfortunately not.

The only way you could do this is by pulling all the objected into a spreadsheet and then perform you updates. Delete all the data in the object. Once complete, upload the new data back into the object.
Expand Post
ThomasH
4 years ago
Hmm,
the statement from Laura may be misleading.
It depends on what you want to update and whether you want it doable by LM-GUI or by other means:
a) Bulk update (a set of objects) with the SAME change
b) bulk update (a set of objects) with different change for any member of the set.

a) can be done from within the LM-Interface (multi select objects in 'search for <object> reports' then select 'edit...'
b) may be achievable by exporting and then using Home->Import Data-> Update existing <ObjectType>

There are other way in achieving 'updates' as well. E.g.:
c) by Integration Managers 'Snow XML' connector
d) by using Import Service from "Snow License Manager Web Configurator" (see dialog tab 'Import Service' in after starting WebConfigurator.exe)
e) by crafting SQL and DB-Jobs with usage of Snows-StoredProcedures
like e.g. "PROCEDURE [dbo].[LicenseAddUpdate]"
NOTE:
Use of those procedures normally need prior retrieval of the input data needed for this procedure (not only feeding in the updated data) by prior usage of a corresponding 'Get' function/procedure. - e.g. "LicenseGet()"
There are even some 'MultiEditAddUpdate' versions of the object-specific AddUpdate procedures which need to craft a predefined (xml-)structure before.
Usually you need put this into some other sql-logic to do the lookup-/Sync-decision as to what object/attribute needs to be updated as well.
This is 'advanced' stuff and may need involving Snow-ProfServices and/or a skilled Snow-Partner as e.g. apogiz - spoiler: end of selfish advertising, I work for apogiz ;-)
This kind of data update is definitely 'doable' (Albeit not 'out of the box').
We use this approach to e.g. integrate with CMDBs for which snow currently does not provide an 'out-of-the-box' SIM-Connector for and where constant sync/update of snow-objecst are needed.
Expand Post

Related Product Forums