To add some context to the question at hand:

In the Assyst Wiki, under Product, the Model Item is introduced, but the details regarding its extent of use are rather lacking.

It’s mentioned in “Multiple Item Update,” but only in the context of updating existing items. Outside of this, it’s merely stated that it’s used in “data import” if other details are missing:

Model Item

This optional lookup field specifies the Model Item (if there is one) which will be used during data import as a default for this Configuration Item Type if the other details are missing. This therefore can be used as the baseline Configuration Item for this Product.

However, the Model Item does not seem to have any effect when trying to create an item in 11.8.3.

I’ve attempted to import new items into the CMDB using assystREST and assystETM as data import methods, without Product selected Model Item having any effect.

These different attempts have been made using both data import methods:

1. Using a bare-bones approach and only providing a shortCode: This returns the “Section is required,” “Building is required,” and “Supplier is required” validation error messages.
2. Using a slightly more fleshed-out version providing these mandatory values: The item is created as normal, however, none of the fields from the Model Item are applied to the imported item.

My questions:

• Are there particular parameters that generaly has to be applied in Assyst for model items to work?
• Are threre parameters that need to be present when using an assystREST POST query for some or all of these values to be used during an item import?
  • If so, what are the steps required to do so using REST
  • Can this also be used as a simplification when importing data using AssystETM?

Best Regards,
Richard