Service and Model Id connection in serviceNow. Means why only one model ID can be connected?

[snehal1]

Hello SNOW techies

Currently having one query regarding ANY Product model lets take software model from servicenow and need to associate it with  service (cmdb_ci_service) so one service can choose only one Model id that is any Product model or in this case software model. 

so IS there any way we can attach multiple model ID with one service.

just FYI,

example.

created one SQL License software model in software model and through Model id --> service related list we need to attach it to one service called Remote License. then again i have another software model created and i need to attach it to same Remote License then how to do it?? is it even possible!

Please let me know if you have any Ans to my que. 

let me know if you need more info. 

Thanks in advance.

[CMDB Whisperer]

No, it is not possible and it seems you may be using your models and services incorrectly.  A software model, generally speaking, represents a versioned piece of software, and it is used not for a specific CI but for software license tracking of that model of software.  I assume from your context you are trying to manage SQL licenses but you do not own SAM Professional.  In that case your options of effectively managing software licenses in ServiceNow are limited, and that is probably worth a separate discussion thread to determine the best methods of doing so.  In any case, a software license is not something that should even be associated with a Service at all.  Whether one or multiple, this is the wrong association.  Services should be associated with a Service model (or no model at all.)  In addition the name "Remote License" sounds suspiciously like a misuse of the Service concept, but I would need to understand what you are trying to do before providing further commentary on that.  Regardless, no CI can have multiple models, regardless of the CI class or Product Model class you are using.  Product Models can have model components but based on what I'm reading here I doubt this is applicable to your intended use case.