How to automate multiple models error while entitlement upload ?

[kiran kumar m1]

Client has two companies , suppose both are using same software for example Visio online plan 1 
so I want to show the consumption company specific so what i did is i duplicated the software model for visio plan 1 and on one model kept a short description company A and tagged  it to one model and on another i kept short description B and tagged it to another model and i am getting the subscriptions from two different m365 connections , after adding the subscription conditions the subscriptions are tagging properly as per the company 

but when I tried to move this records into a higher instance i moved the two models , when i uploaded the entitlements through excel , its throwing error , saying multiple models are present , can we bypass this such as this error doesnt occur while importing the entitlements 
i tried with condition , platform , language but no use , is there any field which can seggereate this ?

[pavani_paluri]

Hi @kiran kumar m1 ,

If you want to keep the duplicate models approach, the cleanest fix is set different Publisher Part Numbers for each model. That way, the entitlement import won’t complain about “multiple models present.”

It's an OOB field available and standard field in ServiceNow’s Software Asset Management (SAM) module. It’s used to uniquely identify software models and entitlements, and the entitlement import process relies on it to match records correctly.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[dreinhardt]

Hi @kiran kumar m1 , @pavani_paluri ,

Not the best advice is to use different part numbers/custom part numbers., PPN are managed by the content team and you’ll loose all the benefits of content updates for your custom workaround PPN. On top, the invoice often references to a specific number and there is no option to „use a different“

I also do not recommend to duplicate the model (especially for SaaS integration) as they all are mapped 1:1 and it’s hard to split.

You could use the following OOTB features.

Upload the entitlements for each company including all the relevant details about company, department etc. to identify each record.

1. Use the new Zurich feature for ELP grouping. License Usage > ELP grouping

2. Use Consumption rules to separate / split entitlements between multiple companies an having unique results per consumption rule. Note: this requires that all relevant details grouping (like company) is available fo each user and computer ci record.

Best, Dennis

[pavani_paluri]

Thanks @dreinhardt  for explaining it clearly.

[MercBuilding]

Yes i completely agree with @dreinhardt , duplicating the models/PPN doesnt fetch you the results and it may cause complications during reconcilaition. Try out the consumption rules as mentioned below