Skip to main content

Suggested Configuration when Importing data into ServiceNow

A potential conflict exists between the enhanced Flexera primary key and the default ServiceNow behavior. When a conflict occurs, it can result in the creation of duplicate Software Discovery Models during import. To prevent ServiceNow's OOTB, Create a Software Normalization Business Rule from creating a duplicate Software Discovery Model, modify the Business Rule, Create a Software Normalization , in the Software Installation table with a filter so that the Business Rule runs only when the Discovery Source is not FlexeraOne .

This is a low-risk change that prevents duplicate software models, improves data quality, and avoids confusion in downstream reporting or license analysis.

Follow these steps to modify the Business Rule:

  1. Ensure you are in Global application scope.
  2. Navigate to System Definition > Business Rules .
  3. Open the Business Rule associated with the Software Installation table called Create a Software Normalization .
  4. Modify the Business Rule’s When to run filter to include AND Discovery Source is not FlexeraOne .

    • Notice, above, that there is no space between Flexera and One . Enter FlexeraOne without any spaces.

  5. Save changes.

This modification ensures the rule will not run for records where the Discovery Source is FlexeraOne , but will continue to apply for all other discovery sources (ServiceNow Discovery and SCCM, for example).