How get SG-SCCM to set CI field to empty?

VanGoghJoe1
Tera Contributor

3 weeks ago

If the value in SCCM is empty for certain fields, we want to set it to empty in the CMDB.
Eg, for Assigned to or Description on the cmdb_ci_computer record.

How enable this? All updates work fine for non-empty values, but can't force it to set an empty value.

Tried adding a Reconciliation rule on Computer for SG-SCCM for All Attributes and added the fields I want to the Update on null list.

Also, in the RTE Entity operation script, I've tried setting output[i] to "", or null, or even '<EMPTY_STRING>'.

 

I can set the the attributes fine in script calling SNC.IdentificationEngineScriptableApi.createOrUpdateCI(), so I don't think it's the IRE. 

 

But no luck using the SG-SCCM Robust transform maps.


What's the trick?

0 Helpfuls
  • 427 Views
2 REPLIES 2

Vishnu-K
Tera Guru

3 weeks ago

Hi @VanGoghJoe1 , 

 

Sorry i'm bit lost here , as you want see the values which are empty in the SCCM should be empty as well in the ServiceNow so i think that's how it is already configured .

By any chance are you saying that there different sources where the data is coming from and you want to see the data exactly what is present in the SCCM ? If this is the case then you can create a reconciliation rule of highest priority (i.e lowest priority number) for SCCM and while creating the reconciliation rule add the fields into selected bucket to update with null 

Example:

VishnuK_0-1770181620273.png

and after that if data is coming from is updating the fields again then go to all navigator an search for the CMDB Properties > identification/reconciliation properties

VishnuK_1-1770182195123.png

There you can un check the property named "Allow the update of an empty field by a lower priority data source."

 

VishnuK_2-1770182245342.png

 

if that is not he case 
So can you please share an example how your data looks now and what you want to achieve, so that it would help to answer the question more perfectly 

 

Thanks,

Vishnu.

0 Helpfuls

VanGoghJoe1
Tera Contributor
In response to Vishnu-K

3 weeks ago

Thanks, @Vishnu-K 

 

I think it's finally working.   In addition to having to set the value on the target CI field to the literal string '<EMPTY_STRING>',  and setting the Reconciliation Rules I mentioned in my post, I had to run the SG-SCCM import by actually executing the Scheduled Data Import itself.  

To enable a faster test cycle, I hadn't been re-importing the data each time, I was simply running the robust transform from the Computer Identity data source.  However, apparently that doesn't run as the SG-SCCM discovery source, and so presumably the reconciliation rules didn't apply. 

0 Helpfuls