Upgrade

Pre-requisites

• inRiver connector v.7 need Litium 7 and inRiver v 6.3 with inRiver connect.

Important changes from v.6 to v.7

1. Litium 7 has the new Sites API with Litium Field Framework. inRiver connector is updated to use this new API.
2. Litium 7 has some changes in VAT handling. InRiver connector is adjusted according to the new price handling.

Upgrading steps

1. Install inRiver Connector. Refer Install section for more details.
2. Delete xml files in the InRiverLitiumIntegration\Resource directory.
3. Configure the connector. Refer Configure section for more details.
4. Test connector with a new test assortment with atleast two product categories, one or two products, items and connected images. Makesure it all works ok with new test entities before proceeding. The very first changes may take time, depending on the size of your inRiver data.
5. Remove your test entities.
6. Do a full channel publish from inRiver.

Configuring publishing selector field type id.

After Litium 7, variants and categories are published on channels not on the website.You can still use the same CVL field in InRiver for that one but it has to contain channel ids in Litium as values.

Remove the following settings from the configuration file:

• categoryWebSiteSelectorFieldTypeId
• variantWebSiteSelectorFieldTypeId

Add the following settings to the configuration file:

• categoryChannelSelectorFieldTypeId
• variantChannelSelectorFieldTypeId

Channels that are created at the Litium BO has no Id set. Id has to be set via ett script in the database if it is missing.

UPDATE Globalizations.Channel SET Id = 'A unique id for the channel'

Important! Id that you are setting in Litium and the value of the CVL field in InRinver has to match. Don't forget to restart your webapplication after the database changes.

Configuring the price import.

After Litium 7, prices are not containing the vat percentage. This is handled via TaxClass on the base product. If you are importing the prices from InRiver you have to change the format of the "priceLists" setting in the configuration file and a new setting.

Old format: <FieldTypeId>:<PriceListName>:<Currency>:<PriceIncludesVAT? true or false>:<Vat fieldTypeId>:<Default VAT percentage, value between 0 and 1, use '.' as decimal seperator>, <FieldTypeId>:<PriceListName>:<Currency>:<PriceIncludesVAT? true or false>:<Vat fieldTypeId>:<Default VAT percentage, value between 0 and 1, use '.' as decimal seperator>

New format: <FieldTypeId>:<PriceListName>:<Currency>:<PriceIncludesVAT? true or false>, <FieldTypeId>:<PriceListName>:<Currency>:<PriceIncludesVAT? true or false>

Add the following setting to the configuration file: 

• taxClassFieldTypeId
  Use a CVL field in InRiver and it has to contain tax class ids in Litium as values.

TaxClasses that are created at the Litium BO has no Id set. Id has to be set via ett script in the database if it is missing.

UPDATE Globalizations.TaxClass SET Id = 'A unique id for the tax class'

Important! Id that you are setting in Litium and the value of the CVL field in InRinver has to match. Don't forget to restart your webapplication after the database changes.