SAMP - How are discovery models normalized after software installation data is loaded?

Michal Sadowski · ‎11-13-2022

Hi SAM Superheroes,

I read and watched a lot of content about how discovery models are created and normalized, but I'm still a little confused. I ran an experiment based on this ServiceNow video (https://www.youtube.com/watch?v=ePi5WBqJcOI) and uploaded software installation records (see below).

The resulting discovery model came back as Match Not Found.

Am I foolish to expect SAM Pro to do the heavy lifting of automatically normalizing common software models (e.g. MS Project)?
What am I missing? Do I need to turn anything on for the automatic normalization process to work in my instance?
I tried it for other software installs and it was Match Not Found as well...
I was expecting this to match against ServiceNow provided software library and thus come back as Normalized or at least Partly normalized.

Could somebody help me understand why it is not?

dreinhardt · ‎11-14-2022

Hi @Michal Sadowski

I was able to reproduce the issue with the data you've provided in my PDI.

The solution is quite simple, but I hope that the community can provide us with more information about the behavior. Compared to other "MS Project" installations with the same version if found one difference in the wording, which has an impact on the normalization.

Microsoft Project Professional 2016 - en - us (your data)

Microsoft Project Professional 2016 - en-us (SAMP demo data)

When replacing the space between "en - us" the installation and the linked discovery model is normalized as expected.

Perhaps, @Daniel Slocum can give us more insights and tell us why in the first example at least the publisher was not normalized.

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

View solution in original post

dreinhardt · ‎11-14-2022

@Michal Sadowski , sure. Find attached the settings and my demo data xlsx. I didn't change anything to the transform map settings. Loaded data and created a transform map and I'm running the latest Tokyo PDI including the SAMP plugin installed

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

Michal Sadowski · ‎11-14-2022

Thanks a lot @dreinhardt. Loaded your file based on your transform map and it gives me Match Not Found for both rows in Discovery Models...

My PDI runs on San Diego but this shouldn't make any difference.

I have SAMP master plugin installed.

Is there any setting / property / business rule / scheduled job / related plugin / set-up or anything else that needs to be enabled (and is no by default) for normalization to work correctly?
Update: one of the rows did normalize to Partially normalized. That's some progress...

Update 2: Looks like the problem was with the data in the import file. Just as you said in your first reply. I ran more imports and made sure software install data was a better match and I ended up with Partially normalized and Normalized.