Appendix A: Setting Parent/Variants
Adding of Free fields (features/attributes):
In AccountView you have a defined set of variables. Therefor it can be difficult to achieve a functionality that does not naturally occur in AccountView. One of those functionalities is variants and their parents.
To facilitate this desired functionality, we offer the following solution. AccountView has the option to add additional fields that are freely to use for their software users, which do not have specific functionality attached to them. These fields must be available in the Article Business Object however. If the fields are in this Business Object, the integration will automatically assign these fields, if set in the settings. An explanation of this is below.
Configuring in ApiCenter
When the Accountview environment has been fully populated with technique described above, it is time to set ApiCenter to the correct configuration, to load in variant products and their parents.
First; you will need to specify which attribute is mapped to which attribute in the secondary application. Remember, an attribute is what makes a product unique, like size and colour for example. Do not include features in this mapping table.
Secondly; you need to define the features of a product. Remember a feature is what all variants of a model share, like the material the product was made from, or the country of manufacture for example
Thirdly; it is very important to set the defining attribute, to specify where the parent product reference can be found. If this setting is not set, ApiCenter will not recognize your product as a parent-variant pairing.