Upgrading to a New Major Version

Customizations

If any customized web components for Lime CPQ are used in a solution, the major version of @limetech/limepkg-cpq-order in package.json must match the major version in pyproject.toml. Make sure not to miss this step when upgrading.

Upgrading to v2.x.y

The tables for quotations and orders as well as the table in the quotation template are now sorted by a new field position.

1. Add this field to the dealarticle and orderrow table:

   Field	Field type	Invisible	Required	Default Value	NULL is permitted	Readonly
   position	Integer	False	True	1	True	True

   Translations:

   Swedish	English	Danish	Norwegian	Finnish	German	Dutch
   Position	Position	Position	Posisjon	Asema	Position	Positie

2. In Lime Admin open the code editor on "CPQ" and "Order". For each section rename the propertyRowId to propertyPosition and change the mapping to the new field.

Upgrading to v1.x.y

Lime CPQ is a new product, but some of its tables and fields are base on ERP Order. If ERP Order has been previously installed, the installation will add/update existing tables and fields.

ERP Order Migration

Before CPQ Installation

• Export the Lime Admin config for ERP Order for inspiration (many of the field mappings are the same in the limepkg-cpq-order package)
• Remove the limepkg-erp-order dependency from the solution
• Delete ControlsHandlerOrder from the VBA Class Module GeneralControlsHandler
• Delete m_Explorers_BeforeActiveExplorerChanged from the VBA Class Module GeneralExplorerHandler
• Delete SQL on update expressions for dealarticle.totalvalue, orderrow.row_id and orderrow.totalvalue
• Delete custom limeobjects that were added through the ERP Order installation (dealarticle, order, orderrow)

After CPQ Installation

• Verify installation didn't create duplicates for already existing fields
• Verify that the readonly settings for fields match the LIP package