Exploring the possibility of having one software model links to multiple software catalog items

[Maggie2]

Hi,  

We are exploring an idea to name software catalog items with an end-user-oriented approach.  What we are thinking is instead of using the software license name as the cat item, we would like to use the application name that built by the software.  For example, we use D365 Customer Service to build an app called "App ABC", anyone needs to access "App ABC" will require a D365 Customer Service license.  So, instead of publishing a cat item under the name of D365 Customer Service from software model D365 Customer Service, we want to name it "App ABC".  This way end users will not be confused on which software license they need for the app they use.  

But, here comes the issue, we have multiple applications built by D365 Customer Service and we can only publish/link one software cat item to one software model.  It seems like if we want to go with this approach, we will have to create multiple software model records for the same software license which I don't think it's a good practice.  

So, does anyone have tried this approach for software catalog items? 

Also, it looks like Vendor Catalog Item allows to create multiple records within the same software model.  I wonder if it can be used as a solution?

Thanks in advance for all your suggestions and advice!

[dreinhardt]

Hi @Maggie2,

If I have understood it correctly, then the actual goal is that every user who orders a D365 custom service app from the catalog necessarily needs a D365 custom service subscription in the Dynamics portal, right?

My suggestion is that you either link each catalog item to the D365 license (software model) and thus trigger a brief check and, if necessary, allocation for each order.

For more transparency, however, you could also repeatedly call up the catalog item for the D365 subscription from the respective custom apps and thus control the license check/allocation. 

Best. Dennis