ExternalStoreNo and storeNo in 3rd party import (RTC-32637)

If at least one of the 'storeNo' and 'externalStoreNo' is correctly specified when importing the store and the other is null, the null value is ignored.

Import file with thousands of rows (RTC-34237)

StagingImport job does not fail when one imported file contains over 4000 of JSON rows.

External store number (RTC-31286)

There is a validation while importing Excel file with stores: External store number must be unique within a company. If there are two or more shops with the same company and the same external store number in the file then only the first record from the file will be added.

Global location number is unique (RTC-33526)

Global location number of store is globally unique value. Validation occurs when value is already used, when creating or updating store. In case of existing duplicates, global location number is set only for the first store, for the remaining null is assigned. In import from BackOffice, duplicates are saved with null value. In import from 3rd party, row with duplicate is validated and not imported. In import of Excel, validation in user interface happens if duplicate exists in database, and row is ignored if there are duplicates in one file (to be handled with warning notification in future).

GLN translations (RTC-32596)

Global location number (GLN) translation to Norwegian and Swedish is changed.

Database compatibility level (RTC-32039)

Compatibility level on databases is set to 150.