POS Import v. 4.0.52
Date:
Import of POS Management Reason Codes from Cloud
Support for importing of reason codes exported from POS management cloud module has been added to POS Import.
Required
POS Master database v. 3.0.0.113 or higher
POS Import v. 4.0.51
Date:
Length for PromortionCode field extended
PromotionCode will be imported with maximum 50 characters.
Required
POS Master v. 3.0.0.110 or higher!
Import external customer number as customer number
Alphanumerical customer numbers exported from Chain Web will be imported to POS.
POS Import v. 4.0.50
Date:
Items with missing VAT in import to POS
Error handling of items received by POS Server without VAT code has been implemented in POS Import.
Performance of checking for unprocessed data
The performance of the SQL Stored procedure used by POS Import to find stores with un-processed data in POS Master staging tables has been improved. The procedure could previously use up to 30 seconds and result in timeout. It should now finish in less than 1 second.
If, for some reason, the procedure does not respond within 25s, all stores will be processed.
POS Import v. 4.0.49
Date:
Data is missing from bundle mixes
Group creation for mixmatch type 100 is now properly handled. Data is no longer missing from bundle mixes and prices are correct.
Product Series from Item Management
Support for importing product series from Item Management module has been added to POS Import.
Required: POS Master v3.0.0.99 or higher
"Can be sold" flag from Item Management as stopcode
Support for "Can be sold" flag exported from Item Management module has been added to POS Import. "Can be sold" = false flag from Item Management is now imported as stopcode = 3 in POS Master (FlatVPI table). Hard-coded stop reason "Not ready for sale".
Required: POS Master v 3.0.0.102 or higher
Promotion price in bundle
'Promotion price' offers marked as 'Bundle offers' are exported as 'soldInBundle' on item level.