Fields

The fields are mapped according to the following scheme:

Multi-language support

Litium Studio flag "multi-language support for value of the field" is set for inRiver Locale String fields.

String fields

Litium Studio has three string types called Text long, Text middle and Text short, while inRiver only have a string field type. Following scheme is used when choosing the Litium Studio field type for inRiver string fields:

1. If the field is marked as display description in inRiver, the Litium Studio field is a text long field.
2. If the field is marked as a "AdvancedTextObject" field in inRiver, the Litium Studio field is a text long field.
3. If the field is explicitely marked with LsFieldDefinitionType field setting, the Litium Studio field is defined by this setting (see below)
4. In all other cases, each inRiver string field becomes a text short string in Litium Studio.

inRiver CVL Fields

inRiver CVL fields are mapped as Multivalue/Default value text short fields in Litium Studio. When the field is marked as Multi-Value in inRiver, the value set in Litium Studio is a comma seperated list of the value field.

inRiver does not allow spaces in the CVL key. If you already have a Litium Studio solution with spaces in multivalue/Default value keys, you need to rename them first.

Field data type mapping

The field data types are mapped between inRiver and Litium Studio according to the following scheme.

Converting inRiver fields to text fields in Litium Studio

The connector can be configured to use Litium Studio Text long, Text middle or Text short data type for any of the inRiver field data types by setting the custom field setting "LsFieldDefinitionType" to "LongText","LongSimpleText" or "Text" respectively. For example, following image shows how to set a inRiver Locale String data type to be treated as a Text long field in Litium Studio.

Renaming field type name

When transfering to Litium Studio, the default field type name generated is same as the inRiver field type id. To rename, use the LsFieldDefinitionName custom setting for the field type. Following example renames the ChannelNodeName to Name.

Use this feature with caution, if you have multiple fields with same name, their attributes need to be same, otherwise you may end up with unintended settings in the Litium Studio field and field template.

Excluding field type

A field type can be prevented from getting exported by setting the LsExclude field type attribute. The field will not be created in Litium Studio and its data are not exported.

Image and file fields

According to inRiver recomended practise, the file data type in inRiver should only be used with inRiver resource entity types. Therefore, for all other entity types, the File data type should not be used. The images and files for a entity are connected resource entities through appropriate link types. More information in image and file handling is presented here >>.

Litium Studio Field Group

This feature is new in InRiver connector 3.0.

By default the fields created by inRiver connector has the field group name set to the inRiver Category. However, inRiver does not allow spaces in the field category. To set the field group in Litium Studio to a value other than the inRiver field Category, use the LsFieldGroup custom setting for the field type.

Changing sort order of fields

To change the sort order of the generated fields, use the LsSortIndex custom setting for the inRiver field type. (see above image for an example, where index of the Litium Studio Color property is set to 1, using LsSortIndex flag).