Specifications
inRiver specifications allow the Rich client users to dynamically create fields and enrich the products. This article explains how the specification fields are handled.
Specification fields
The inRiver connector transfers data from a specifications connected to an inRiver Item entity by creating the field types as requiered in Litium Studio article template. All specification fields will have the group Specification. Also, if the name does not include the Specification suffix, it will automatically be added to these fields. This make sure that the fields does not conflict with existing other normal fields created by the inRiver model tool.
example:

The default implementation only supports the Item-Specification links, and only one Specification for a given inRiver item. Projects can easily extend the functionality for inRiver products.
Adding specification fields
Add the specification fields the normal way you would add them in Rich Client. The fields will only be transfered when they are filled with values. So, you need to connect the specification to a inRiver item and fill in some values for the specification fields for the specification fields to be visible from Litium Studio.
Note that the first time you fill in value and click the Save button, the specification field will be created, but its value may not be transfered, but subsequent edits to the field or the item will make the value visible in Litium Studio.
Removing specification fields
Specification fields are not removed from the Litium Studio field templates automatically. Instead when the fields are removed, thier value is initialized to empty strings. In case they are numbers, its initialized to zero, and if its a date to sql minimum date.