Best practice for normalization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 01:16 PM
Hello,
If you have a product that has XYZ 1.12.123, do you usually normalize as 1.1 or 1.12 (I guess it depends on if its a major or minor release)?
What are the guidelines on normalizing the versions which can be tricky ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 01:56 PM
It depends on how do you want to save your data in your instance. It changes from customer to customer
It will make sense once you/team start using this data

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2024 07:56 PM
The answer to your question will depend on what you need this data for. In fact, your question does not specify whether you are discussing installation data or software model data. In Software Asset Management (SAM), there is an entire data model that governs products, software models, discovery models, software installations and software entitlements (licenses). In short, software installation data will often record version numbers quite differently to what is needed in SAM reports and recorded in the purchased entitlements. The reconciliation between entitlements and installations occurs via discovery models, and it is these discovery models that are normalized in SAM. Discovery models can be normalized to major or minor versions. Through filters (or discovery maps), software models will reference these discovery models and the associated installations.
Software publishers SKUs/Publisher Part Numbers (that is, for the license you purchase) typically refer to major versions and all minor versions within it.
For further learning may I recommend a short video on software normalization I created a while ago, as well as the Software Asset Management Professional Fundamentals training.