Configure
Basic configuration options for the connector: how to configure the connector to generate appropriate field types and template, resource fields and product relationships.
Changing configuration options
After changing the configuration options, you must do the following for the smooth operation of the connector.
- Delete all the files and folders inside <integration folder>\InRiverStudioIntegration.
- Restart the connector from inRiver admin website.
- From Litium Studio backoffice, delete all articles and assortments.
- From Litium Studio backoffice control panel, delete all product catalog fields.
- Click the save button in Litium Studio backoffice\Control panel\Deploy\InRiver Connector. This will re-import the inRiver model changes to Litium Studio.
This section explains how fields are mapped from inRiver to Litium Studio and how to configure their names and data types.
This section explains how the display templates and field templates are generated and how to change the default names.
This section explains how images (and files) are exported from InRiver and Imported into Litium Studio.
inRiver link types that are not part of the normal entity structure (i.e. excluding ChannelNodes and Product-Item-Resource model links) becomes either Bidirectional or Directional links in Litium Studio where appropriate.
This article explains how to create product relationships in Litium Studio using inRiver connector.
inRiver specifications allow the Rich client users to dynamically create fields and enrich the products. This article explains how the specification fields are handled.
inRiver SKUs are the units by which the ERP system keeps track of items sold. Therefore, they are articles in Litium Studio. This article shows how to define Sku fields for default connector implementation. Projects may extend this functionality based on the merchant and ERP requirements.
product urls are generated from the display names and SEO title and description from item display name and display description. This article explains best practices to adopt.