Mapping of catalog items to model in SAM

[mihirr]

I have a requirement where the end user should only have option to see the 'Visual Studio Professional' catalog item.
If he submits the catalog item we are directly reducing it from Visual Studio 2021 version through source request.
But we have multiple version like 2005,2007,2010 and so on with active entitlements.
Shall we create catalog item for each version or we can have one catalog item to cater all the version through source request. 
When Discussed with SAM team they stated they are only concerned with Visual studio professional license.
How can we have a cumulative license deduction for Visual studio professional.
DO we have any solution for this ? Have anyone implemented this.

[dreinhardt]

Hi @mihirr,

It is not uncommon for licenses for older versions to be available, but due to subscriptions, contracts, etc., only a certain version/edition is licensed and used, which may also cover older versions.

The SAM team should define at this point whether the older versions may still be used/installed at all - if this is not the case, then your current implementation is correct and the link to the model is fine.

if the SAM wants to decide with version will be deployed and is licensed - you should provide a cat item for each Version/edition as a hidden catalog item. The generic VS studio request needs to extended for the SAM team to select the edition/version and thus triggers one of the hidden models to allow the sourcing process as always.

best, Dennis