Multiple models being created when entering one PPN number at the entitlement level.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Currently we are renewing our Microsoft ELA, all previous model records do not have associated PPN's so they will be deleted. We have 22 new entitlements with PPN's, when bulk uploading the 22 entitlements over 1000 new models are created. Is this expected behavior? What is the best practice for this, should the unrelated models be deleted or kept for mapping? Is there any way to stop this from happening?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Yes, generating a large volume of software models during a bulk entitlement or Microsoft License Statement (MLS) import in ServiceNow Software Asset Management (SAM Pro) is a known behavior. The import process parses the publisher part numbers (PPNs) and automatically queries or expands records based on the content library mappings, causing hundreds or thousands of related or child/component shell models to spin up.
Best Practices for Unrelated Models
- Keep them for mapping: Do not manually delete the newly generated models if they were auto-created by the system engine.
- Impact of deletion: Deleting these models often breaks software reconciliation, normalization, and future entitlement linkages or upgrade/downgrade rights mapping.
- Cleanup alternative: Instead of hard deletion, rely on ServiceNow's normalization and Discovery Maps to let the system group or ignore unused variations cleanly.
