1 of 1 people found this helpful
The CMDB/Asset forms are not the same as the ITSM application forms such as the "HPD:Help Desk" form, which are standard "regular" forms.
The CMDB "regular" forms (as seen in the CDM) are actually "join" forms consisting of a regular form joined with an underlying regular "base" CMDB form e.g. BMC.CORE:BMC_BaseElement [the "base" CMDB form, where every CI will have an entry] with another regular form e.g. BMC.CORE:BMC_Application_ [note the underscore in the form name, which is the underlying "regular" form for the associated class] to create the form "BMC.CORE:BMC_Application" - which in the end is the CMDB class "join" form you see in the consoles.
The associated Asset form is then a self join (Cartesian) of the CMDB form, along with the AST:Attributes form, which creates the AST:xxxx forms.
So, when creating entries you need to identify the "regular" forms involved in the process to create the entries to receive an associated Entry ID when using the API.
For the CMDB, the class regular forms have the "_" appended to the form name.
If you target the join form (without the underscore), you will not receive an ID although the entry maybe created.
This is a byproduct of the way the API works as it cannot handle the "join" IDs (IDs from the 2 regular forms concatenated together).
If you use the join form e.g. "BMC.CORE:BMC_Application" to create the entry, you would need to query back this form to obtain any information on the created entry e.g. using the Asset name or some other criteria.
If you create the entry in the underlying "regular" form e.g. "BMC.CORE:BMC_Application_" then you would receive an associated ID back.
Hope this helps.