FIX: CountryCode on VAT in item import should not be required (RTC-28989)

A country code for Vat in imported files is not required. When user imports one vat code without a country, the value is set to default country.

It is impossible to import only country code, vat code is required.

FIX: Importing item with changed supplier (RTC-28760)

It's possible to change supplier on item that has labels - both mass update and through import Item file.

System cleanup job (RTC-25652)

• During night we cleanup (delete) rows older than 30 days from [Label].[LabelExportLog] table, in batches of 200
• Parameters in config of this job: cleanupLabelExportBatchSize (default 200) and cleanupLabelExportOlderThanDays (default)
• Logs in job execution show how many rows were deleted.

Fix for exporting items to elastic search (RTC-27863)

SearchIndexingJob doesn't get stuck exporting items to elastic search and won't spam Application Insights with logs. 

• Creating new item and new price from RIGAL file with 'FixedPrice' (vtype = P or F), the price created is fixed price.
• Creating new price for existing item (which has an active store price that is not fixed price) and in RIGAL vtype = P or F, the price created is fixed price.
• RIGAL with a value Rab1, imports the value into the supplier discount field.
• RIGAL has VType2, set it to ItemType. Override value set by VType (If RIGAL has 'P' od 'F', in vtype then the price should still be set as fixed price).

Handling of price date from (RTC-27418)

Valid From date for price is changed to today's date when:

• The imported date is in the past
• Date is missing in import

User is informed, that ValidFromDate is set to today's date.

• The bottom and top margins when printng EkoPallet Label don't cut the data from label (both when printing from Label Printing grid or item details).
• Translations to the EkoPallet label type are added.
• EkoPallet promotions behavior is the same as for EkoMaxi and EkoMini (they're not triggered when assigning promotions).

Printing of deposit price (RTC-26545)

Store price of deposit item is printed on labels to print, next to "+pant" text.

• Current price of deposit item store price is chosen.
• If deposit item has price on many levels, the lowest level is chosen (Store, then Price Zone, then Profile).
• Change of deposit item price doesn't trigger creating new labels.
• Deposit price is shown on label only when store on the label and deposit store price are the same. If they're not, label has only "+pant" text
• Applies to EkoMaxi,EkoMini and EkoPallet labels

Length of item text fields (RTC-27135)

The ItemText, ItemReceiptText, LabelText1, LabelText2, and ItemGroupName fields are 255 characters.

Segmentation on item hierarchy (RTC-27619)

Segmentation can be done on all item hierarchy levels: Department, Item area, Item group and Item sub group.

Handling of scale links (RTC-26846)

• When removing scale links from item, links are marked as deleted, not permanently deleted from item.
• Applies to removing scale links via Item details or scale register, and import (mass update and default item).

Fix: Import price with ValidFrom before the Vat rate ValidFrom (RTC-26977)

When importing a price that has a ValidFrom in the past (before the first vat rate) the newest active vat rate is used.

Fix: No timeout when importing profile prices (RTC-27063)

• When importing store prices for profile containing more than 600 stores there is no timeout.

Item type column in Item import details (RTC-26773)

Columns "Item type" and "CurrentItemType" is available in the import details view. By default, they are hidden.

Item type imported with the item, is entered into the "ItemType" column. The "CurrentItemType" column shows the item type currently existing in the item (if any).

Import of deposit quantity (RTC-26746)

If an item has a deposit item, but deposit quantity is not given in import (or is set to 0), the default deposit quantity is set to 1 during import. This applies to mass update and item contract type of import.

Fix: Exception when manually validating/importing auto-approval import (RTC-22520)

Import scheduled for ValidationAndImport ends successful.

FIX: Ignore 0 for Trykkbilde in RIGAL (RTC-26898)

When fields Trykkbilde (scale label), Frigr2 (risk item), Behandlingstype (treatment type), Fra_og_med_tid has value 0, import is correctly processed. 

Scale label with non-existing code is created during import.

Reason for created label (RTC-25059)

When a label is created, the trigger reason is stored on the label. In the label printing grid the user can filter on the column for 'Label trigger' if for example price increases should be printed out first.

• If a single label was created by multiple 'reasons', the priority is:
  Promotion ends >  Promotion (is assigned to item) > Price increase > Price decrease > Item change.
• If label is not printed/exported and there are any changes to the item, the label trigger reason is assigned according to priority. 
• If label type don't track promotion related attributes, they cannot be created with attributes related to promotion.

Fix: Export to Myhrvold (RTC-25928)

OnPrem integration package: BackOfficeIntegration - ItemServiceOnPremIntegration

When getting a file from Item Management a label that has scale link, the code of the scale links is mapped to weightGroup, in comma-separated list) in the XML file converted by ConvertItemLabelToMyhrvold job.

Fix: Export to Myhrvold (RTC-26255)

Convert label to Myhrvold On-premises job is correctly processed when there is no value in UnitPriceFactor field in the label.

• Item scale links can be exported via Excel (only active ones).
• Item scale links can be imported via Item. Item JSON contract and Excel (only active ones).
• When unknown scale link is imported for an item, there is a warning in import, that some scale links will not be imported.
• Item scale links are imported/exported on store local values/attributes level.

Fix: Case insensitive reading of properties from FlatBatch MetaData (RTC-26499)

Reading properties from metadata is case insensitive.  The size of the letters in the metadata does not cause any problems during the import.

FIX: Import of alphanumeric GTINs (RTC-25443)

It is not possible to import items with alphanumeric GTIN.  

When importing default item file, item is deleted and an invalid GTIN error appears in the StagingFlatBatchJson table. When importing store price file, in the Import item table, the imported item appears with the error status and the error message about incorrect GTIN.

Maximum labels to print (RTC-26404)

Maximum quantity of labels to print is 1000. If user chooses more labels to print, there is a warning that only 1000 labels will be printed. Marking labels as printed is slightly faster than before.

Labe type register (RTC-24129)

Label types register is used for defining what label types is used by all stores or by specific stores.

• When adding label type on item, only pairs of Label Type and Store that are in the register can be added.
• • When label type in register is on all stores level, in item details it can be added on all stores as well as for specific store.
  • When label type is registered is for a specific store, in item details the label type can be added only for this store.

Myrhvold label is removed from register (it's has scale Category), LTG label is added to register.

Changes for label view (RTC-24565)

There is a new view of EkoMaxi and EkoMini labels during printing. Unit price is shown correctly, ConsumerUnitQuanity as well, there is Kr/UnitPrice under the price.

Scale register (RTC-25741)

Items can be linked to a scale to export item and price changes to 3rd party fresh food scales.

In scale register user specifies the scales available in the store (along with the scale group that they belong to).

It is also possible to add scales from scale group register.

Change tracking rules for label type EKOMaxi (RTC-25060)

• New labels are created/exported when any of the revelant attributes changes (depends on LabelType).
• Change of irrelevant attributes don't trigger creation or export of label.

Import performance (RTC-25861)

During import, the imported items are inserted in way that improve performance of StagingBatchExecutor and ApprovalImport jobs, so they are less likely to timeout.

Rows in PricatImport.ImportItem table are updated correctly.

Deleting store prices from RIGAL import (RTC-25468)

Store prices (past, active and future) are deleted when price on active store price is marked as 'U' in import for given store. It's applied for profile prices, as well, when profile price is marked as 'U' in import for given profile.

Item import performance (RTC-22701)

The performance of import tables is improved, and ImportItems fetch queries has also become faster.

JsonContent is moved to another table, and the new table record only appears when import row is modified the first time.

Print labels for changed items/prices (RTC-24126)

• Selected labels can be printed, when they're the same type of label and are in the same store.
• Selected labels can be marked as printed (without printing)
• 'Printed' column is added to the grid. 
• Only current labels are visible in the grid.

Mass update of Label type (RTC-24897)

It is possible to export label type. When "Include store local values" checkbox is selected it, the label types for all stores are also exported.

It is possible to import label types. When importing a file with no store local values, only default label types are updated. Importing a file from store local values allows you to change all label types.

Set Label type for item (RTC-24550)

In item details you can  define which label types should be used for given item. Label types can also be defined specific on store level.

Import/export of ProductID, Sales code and Bonus flag (RTC-23855)

Item attributes ProductID, Sales code and Bonus can be:

• Imported from JSON file (according to Item contract) and Excel (mass update - item details and prices) - both when creating new item or updating these fields for an item
• When ProductId is used in the ItemPrice contract import, the price is added to the correct item. 
• Exported to JSON and Excel
• In export to JSON every Item Identifier contains ProductID field
• In export to Excel there  are 5 additional fields that can be exported: `subst. item product id`, `deposit item product id`, `product id`, `bonus` and `sales code` with correct translations in NO and SV
• ProductID can be used as alternative identifier of an item.

RIGAL import files set to Done (RTC-23741)

When importing item that does not exist in Item Management (or its price), and if RIGAL file contain  rows with 'U', they are rejected and import is set as 'Done'

Do not lookup model based on externalItemNo if we don't generate it (RTC-20987)

If the "generateExternalItemNO" parameter is enabled and the item has size/color/ExternalItemNO (12 characters) then the imported item is a model.  First 6 digits of the identifier.externalItemNo is used to  lookup against the modelNo of existing models.
If this parameter is turned off, the imported item is a model only if it has color or size given. We are not looking at the number of characters in ExternalItemNO and we are not looking for an existing model using it.

Image for model items (RTC-23125)

Image can be uploaded to model and applied for all sizes/colors or all items. 

Fix for import of RIGAL files (RTC-23691)

It is possible to import RIGAL file when the import has StoreGroupId and the content of the file has store prices connected to that store group.

Use CSV file to manage lists (RTC-23170)

CSV file is validated properly when using it to manage selection in item list and item group list.

Performance for RIGAL import (RTC-23490)

Performance of validation of RIGAL files is improved.

Fix for timeout issue (RTC-23341)

Sometimes users have had to wait a long time for the import to be validated due to timeout that has be related to system tasks (health checks).

Import/export of item attributes (RTC-21946)

All attributes described below are exported to Excel and automatically to export file (blob). 

All attributes described below can be imported via standard JSON import/mass update, and some of them via RIGAL import.  

• Weight declaration
• Alarm item (RIGAL)
• Exclude from gross profit report
• Self-service weights
• Ordering blocked
• Supplier sales start (RIGAL)
• Scale label (RIGAL)
• Treatment type (RIGAL)
• Risk item (RIGAL)
• Manufacturer item
• Product series
• Product category
• Category manager
• Ready for sale
• Can be sold
• Publish to web

Additional item attributes in Item segmentation (RTC-21943)

Item segmentation includes additional item attributes:

• Weight declaration
• Alarm item
• Exclude from gross profit report
• Self-service weights
• Ordering blocked
• Supplier sales start
• Scale label
• Treatment type
• Risk item
• Product series
• Product category
• Category manager
• Ready for sale
• Can be sold
• Publish to web

Fix potential security vulnerabilities (RTC-23397)

Updated number of libraries to newer versions with patched potential security vulnerabilities (Nothing that would affect us directly though). Updated build definitions to fail when a new security vulnerabilities is discovered. 

Mass update import with both item attributes and store prices (RTC-17345)

The user can import items and prices at the same time using mass update. It is possible to import new items with store prices during mass update import type.

Import of store prices with wholesale price = 0 changes the price to 0.01.

When creating new store prices, and wholesale price or cost price elements are not provided, they are copied from the active store price at a given date. When calculation rulesets differ, a copy should not occur. "Fixed price" is copied always, regardless of calculation ruleset compatibility.

Fix for validation of PRICAT (RTC-23169)

Validation during PRICAT import is triggered immediately after following actions:

• Patch import item 
• Changing supplier 
• FixItemIdentifier 
• SelectModel

There is also new parameter TenantServiceBus in tenant admin.

Permission to manage items and store prices (RTC-18758)

Permission 'Manage local items' is a part of store level role.

On model level we have a flag that is called 'Managed by store'. 

A user with Manage local items permission can create only local items (managed by store flag set to true). The user needs to have View items permission and View register permission to make it work properly.

Modify item

Item with 'Managed by store' flag set to True and without any price can be modified by:

• User with Manage local items permission
• User with Manage item permission

Item with 'Managed by store' flag set to True and with price for store X can be modified by:

• User with Manage local items permission for the given store
• User with Manage item permission

Item with 'Managed by store' flag set to False and without any price can be modified by:

• User with Manage item permission

Manage prices

Price for item with 'Managed by store' flag set to True and without any price can be created by:

• User with Manage local items permission
• User with Manage item permission

Price for item with 'Managed by store' flag set to True and with price for store X can be created/modified by:

• User with Manage local items permission for the given store
• User with Manage item permission

Price for item with 'Managed by store' flag set to False and without any price can be created by:

• User with Manage item permission

Import of item hierarchy register (RTC-21554)

Item hierarchy can be imported to register by an Excel file. This can be done using 'import' button in the registers view. Import can be used to create new item hierarchy or update existing ones. File should contain every element's number and name (same file template as in export). Fields in the imported file are validated the same way as in the user interface. If there is a gap in the hierarchy, the 'children' are skipped. If 'parent' element is inactive, it's activated after import.

Retail prices equal 0,01 is exported as 0,00 (RTC-21906)

When store price is equal to 0.01 the Item Price export have 0.00 as value.

RIGAL import of MBXP items (RTC-22809)

MBXP item type in import has code that matches MBXP item type in POS - "MxbpWeb". It includes "X","Y" and "Z" item type import.

Segmentation on variant and model level (RTC-20639)

Items can be added to the offer using item segmentation on item, model or variant level. After selecting item segmentation and clicking 'add to the offer' button, there is a modal window which asks on what level user wants to add segmentation. The default selected value is item level.

After adding items, variants or models to the offer, in the 'Manage items' view, there is a message above the table about what level is used in the item segmentation. Columns in this view match selected level.

Export to blob:

• Items are exported with 'gtin', 'externalItemNo', 'sku' fields in the 'itemIdentifier' section.
• Models are exported with 'modelNo' field in 'modelIdentifier' section.
• Variants are exported with 'variantIdentifier' section which contains 'colorText' field and 'modelIdentifier' section.

Endpoint for item group lists (RTC-22233)

There is an endpoint in ItemService, which allows developers of other modules to get item groups assigned to item group list.

Export promotions to Breece ESL (RTC-19994)

When a label has a promotion price, both promotionStartDateUtc and promotionEndDateUtc are exported and visible in Breece.

No changes to promoitonEndDateUtc (i.e. it's not an actual end date of the promotion, but rather the end date of the label).

Activate/deactivate item group list (RTC-21540)

Item group lists can be activated and deactivated. Column 'Inactive' is added to the item group lists grid. If item group list is inactive, there is a message about it in the item group list details. Such list cannot be used in other item group list. Copy of inactive item group list is also inactive.

Showing date and time in grids (RTC-21537)

Time (in grey font) is visible in 'Created date', 'Modified date' in every grid in Item Management and in 'Last updated' column in Items in import view.

Filtering in these columns is at the date level.

Import promotions and offers (RTC-22463)

List of mix types in Item Service database is updated, so 'StagingBatchExecutor' job does not fail when importing blob with promotion which contains one of recently added mixes (6, 10, 11, 31, 34).

Stop sale reason code (RTC-22207)

Stop sale reason code is exported when changes are done in Item (Gateway.Item).

Merging export of items and store prices (RTC-17349)

It is possible to export item details and store prices at the same time.

User can select only one planning code during export of item details with store prices. 

When exporting data where items have multiple store prices, the items have multiple rows in Excel file. 

Manual import of RIGAL file (RTC-17388)

RIGAL files can be imported directly from Item Management. The import must be approved. 

It is possibly to add and update assortment code in item via RIGAL import. 

Immediate trigger of revalidation (RTC-21177)

Approval import job is scheduled for running every 30 minutes. We have topic in ServiceBus that is called ExecuteApprovalImport. When creating new import or revalidating existing rows or importing selected lines revalidation is performed right away without any delay.

Public and private item group lists (RTC-21562)

Item group list can be marked as private. Then only the user who marked it as private can see it, edit, copy and use in other list. Same as in item lists, item group list can be marked as private when creating new list or in 'Edit name and description' modal in item list view. When user is viewing a private list, a message about this is displayed in breadcrumbs. Private lists owned by the user are marked in the item group lists grid in 'Private column'. Lists owned by other users are not displayed in grid.

Activate/deactivate item list (RTC-19909)

Item lists can be activated and deactivated. Column 'Inactive' is added to the item list grid. If item list is inactive, there is a message about it in the item list details. Such list cannot be used in other item list or to create a promotion. Copy of inactive item list is also inactive.

Export of item hierarchy register (RTC-17635)

Item hierarchy register can be exported to Excel file. This can be done using button in registers view. Export is confirmed in modal, and exported file appears in notification when it is ready to download. File contains number and name of Department, Item area, Item group and Item subgroup. When group does not have any lower level group assigned, it will be exported as row with empty cells, e.g. Department without assigned Item areas is exported with only Department value in row - rest of cells are empty.

Fix for SearchIndexing on new tenants (RTC-22300)

SearchIndexing was developed when the latest Elasticsearch version was 7.x. Now, when installing new tenants, version 8.x is used for new instances - this caused problems and the job started to fail.
The root cause of this problem was a bug / broken backward compatibility in Elasticsearch. We have implemented a workaround for this.

Notifications when importing (RTC-18543)

There is no validation notification when import is auto-approval. 

After non-approval import of only one item, import-success-notification shows button "View item" 

In non-approval import of multiple items, after successfully imported items, system shows notification that "X items were imported successfully".

Fix for nutritons (RTC-17908)

The nutrition table and button in 'food' fieldset have been improved

Fix for create store price with currency SEK (RTC-21918)

If in db no currency has IsDefault=1 then set IsDefault=1 on currency which is set on MainCurrencyCode configuration parameter. 

Import of items with wholesale price = 0 (RTC-21492)

When importing a RIGAL file which has wholesale price = 0 (Engros field), store price is created and wholesale price is set to 0.01.

Fix for import of UnitPriceFactor in RIGAL import (RTC-21691)

Import RIGAL file with 0 in UnitPriceFactor value does not make any changes in value. 

Filtering of import row status (RTC-18224)

Only statuses that exist in the given import are visible in the status column.

Import (and export) of assortment codes per profile (RTC-19693)

UseAssortmentPerProfile config parameter == true, profile sub-columns are available for "AssortmentCode" and "AssortmentName" columns. All profiles that are active in the system are included
Reference is used instead of ExternalReference in excel to identify store group

Sorti field (7.1.47) is added to RIGAL import (assortment code)

"Unknown store group" validation error is added when profile not found during RIGAL import. 

Validation of multiple imports (RTC-21134)

When multiple imports are being validated in one job execution (e.g. two files uploaded at the same time), the 2nd file should no longer fail with an exception. 

Long texts in product information (RTC-21366)

Fields in Product information section are defined as long field. It means there is not limit of characters and full text is displayed when viewing item. There is no need to change size of the field manually as before. Field height is set automatically.

Show QR code in item details (RTC-18522)

In the 'Item' section on 'Item details' view, there is a 'Show QR code' link. After clicking it, QR code appears. It contains GTIN of the item. When QR code is displayed, there is a 'Hide QR code' link to hide it. By default, a QR code is hidden.

Import item groups from file (RTC-19404)

In item group list view, there is a 'Use file' button on bottom of the screen. It opens a modal in which the user can select a CSV file. Item group numbers in this file can be used to include or exclude item groups from the selection. Imported CSV file must contain one column with 'ItemGroupNo' header, and item group numbers as values in this column. When a file is invalid, a validation error is displayed. When a file contains item groups that do not exist in the system, there is a message at bottom of screen.

Public and private item lists (RTC-19624)

An item list can be marked as 'Private'. When item list is private, only owner can view and manage it. User can mark item list as private and assign it to himself using checkbox in 'Create item list' and 'Edit name and description' modals. Privacy of item lists is shown in 'Private' column in item lists grid. Item lists assigned to other users are not displayed in the grid. When editing item list, information about item list being private is displayed in breadcrumbs. When copying private item list, copy is private as well.
If promotion is created using private item list, offer group is not private and all users can manage item selection in offer.

RIGAL import with deleted store prices (RTC-20772)

RIGAL file with value  "U" in 7.1.5 field delete active store price in existing item. In cases when existing item does not have a store prices or item not exist, import is mark as rejected and does not make any changes. 

Label Processor does not create a label when store price is deleted.  
Price per unit is not available when store price is deleted. 
Values from deleted store price is not used to fill some field when creating new store price 

Edit import row (RTC-18566)

Edit row function is available for the following imports: PRICAT, Temalogic, Mass update-item details, RIGAL and Bladcentralen. This function lets the user modify the following values in the file without importing a new file: Item text, Color text, Size, Sales unit, Item group, Item subgroup and Brand. Clearing values is not supported. 

After saving changes (Done) the row is revalidated.

Null values when UsePlanningCodes is False (RTC-17801)

When UsePlanningCodes is set to "False" then two attriubtes get Null value: Planningid and Storegroupid (season.itemplanning table). Storegroupid gets Null regardless of defined value in system parameters (SingleWholesalerStoreGroupExternalReference)

Label text fields in RIGAL import (RTC-20649)

LabelText2 field is imported from the RIGAL file.

Import in Bladcentralen/Interpress format (RTC-15474)

New items/prices can be imported by uploading a CSV file in the Bladcentralen/Interpress format. The user must manually select the profiles/teams/stores for which the prices will be created. 

The functionality requires permission for "Bladcentralen import".

Model export and bundle items (RTC-20344)

Model and color can be exported to Excel properly using button in 'Item details' view.
Inactive items cannot be added to bundle item content.

Certificate handling (RTC-20381)

Modules will refresh issuer (Shell) signing keys every 24h.
There is no need to restart the module when the certificate used for signing tokens is changed (thus no 401 errors).

Permissions for view items (RTC-18670)

If logged user does not have "View prices permission" then we don`t send request for checking price when viewing item. It means that for such users 'Price per unit' field is hidden.

Import of alternative GTIN (RTC-19012)

When importing items we check if defined alternative GTINs is not used as main GTIN for existing items. If so then GTIN defined in file is skipped and rest of changes is imported.

If GTIN is already used by another item then user gets such validation warning: Tandem GTIN is already used.

RIGAL Import (RTC-19015)

Item attributes for 'Change VAT'-flag and unit price factor are supported in RIGAL item import.

• Change VAT - True / False
• Unit price factor - value and unit (for example 100 pcs)

While importing file we use such fields:

• Conversion factor is field 7.1.79 (Konvfak) in RIGAL file.
• Conversion unit is field 7.1.92 (Konvenh) in RIGAL file (For Unit we have such predefined units: 1 = piece, 2 = kg, 3 = liter, 4 = meter). 
• Change vat is field 7.1.149 (Chgmva) in RIGAL file.

Alternative GTIN in RIGAL import (RTC-18481)
Tandem (alternative) GTINs can be activated and deactivated using RIGAL import.

General performance improvement (RTC-17678)

Improved performance for uploading the Import files. Page cache is no longer loaded for ApprovalItemHandler.

Alternative GTIN problem (RTC-18773)

Duplicated alternative GTINs can be imported with RIGAL files.

Upload image from Item Management to EG POS (RTC-17338)

When uploading image in Item details in Item Management, a job in the Integration Platform (MediaBankIntegration package) will automatically upload the image to POS Mediabank.

A new validation error is added - 'Planning code cannot be created'. It appears when trying to create a new item with a planning code given in the file. 

Export store prices to Excel (RTC-15314)

Currency of 'Wholesale price in supplier currency' in store price can be exported to Excel. 'Wholesale price in supplier currency' cannot be exported without 'Currency' column.

Export of item file when item generations is not used (RTC-14141)

Export of item JSON blob works for both values of the parameter UsePlanningCodes (True/False).

Stability in import jobs (RTC-17209)

Jobs in Item management can be run together, also for longer runs.

Export prices to Excel based on price status RTC-16003)

There are two checkboxes in the Price state section in Export wholesale/store prices to Excel views: 'Include future prices' and 'Include historic prices'. When they are not checked, only active prices are exported. If they are checked, they are set to one year in the future/past by default. When they are used, prices from the selected date range are exported. Both checkboxes can be checked at the same time.

Mass-update of items with parameter UsePlanningCodes set to False (RTC-15621)

Import of mass-update items works with Parameter UsePlanningCodes=False. It means attributes related to item generations (planning code) can be imported without planning code value. 

Empty Break bulk code in RIGAL import (RTC-17487)

RIGAL import supports empty value in field 7.1.89 (Anbrekk) - Break bulk code. Empty value won't affect Break bulk code.

RIGAL import supporting more attributes (RTC-16410)

RIGAL import is extended with new fields: 

• Sub group
  7.1.19 Undergruppe
• Deposit item
  RIGAL: 7.1.58 Linknr We don't get quantity in the RIGAL, so qty = 1.
• Warranty type
  RIGAL: 7.1.93 Garantiklasse
• Quantity in supplier package
  RIGAL: 7.1.15 Antpkn
• Special group
  RIGAL 7.1.71 Seletering3
• Environmentally Friendly
  7.1.74 Miljøkode
• Ecological
  7.1.76 Økologisk
• Measures (width/depth/height)
  7.1.83 Bredde (width)
  7.1.84 Dybde (depth)
  7.1.85 Høyde (height)
  Values are in meters and kilograms
• Break bulk
  7.1.89 Anbrekk
  If True, the break bulk code in IM is set to default break bulk code
• ID Requirements
  7.1.94 IDkrav
• Shelf life
  7.1.98 Holdbarhet
• Tara
  7.1.99 Taranetto
  Kg
• Season code
  7.1.112 Sesongnr
• Product information
  7.1.128 Beskrivelse
• Active substance
  7.1.138 Fritekst5.

Show values from active store price (and price refactor) ( RTC-15276)

Columns 'Active %' and 'Active amount' are visible when creating new store prices. They are filled out if there exists an active store price for the same store/team/profile and price calculation rule on the item. When several stores/teams/profiles are selected, values are taken from the first one with the existing active store price. Currency is also copied from the active price. Currency rate, VAT code, and VAT rate, however, are taken from the item (two latter ones based on the selected 'Valid from'). 

Export alternative GTIN's (RTC-14427)

Alternative GTIN's are exported together with all item attributes to Gateway.ItemChanges. They are exported with their status active or inactive. Inactive alternative GTINs are included in the export for 14 days (are not exported if they were modified 14 days ago or earlier). This should be enough time for any subscribing system to update/delete data in their system. 

Hide item generations (planning codes) when not using season related attributes (RTC-14140)

Parameter UsePlanningCodes (set to True) allows using planning codes for all planning code attributes and wholesale prices. When the parameter is disabled (set to False) it is possible to use planning code related attributes without defining the planning code. There are available selected attributes of Procurement setting, Sales date, Assortment, Product information fieldsets (attributes, which are available: Procurement rule, Auto replenishment, Backorder allowed, Replenishment code, Service level, Consumer sales start, Consumer sales end, Supplier sales end, Base assortment, Collection, Assortment code, Sales purpose, Sorting code, Product information, Advertisement information, Technical information).

The field "Original planning code" is hidden.

The button "Manage item generations" is hidden.

Include code for store group (RTC-16305)

Store group's code (Reference in Chain.StoreGroup) is exported when changes are done in store prices (Gateway.ItemPrice) or in item details of an item using planning code (Gateway.ItemChanges).

Export item subgroup (RTC-16340)

Item subgroup's code and name are exported together with the other attributes when item changes are exported to blob.

Export of item hierarchy (RTC-15088)

Department, item area, item group and item subgroup are exported to file/blob. Active status flag is not exported.

Configurable price calculation rule in RIGAL import (RTC-15464)

The Price calculation setup register's default value for price calculation rules is used when importing RIGAL store prices. If no rule is set as default, the Default price calculation is used. It is possible to update a store price with RIGAL only if the same price rule is used while importing as the one set on the price. 

Mass update of item details (RTC-15737)

Additional item attributes which can be updated by import of Excel file:

• Default margin
• Deposit item
• Nonsale type
• Ready for sale
• Warranty type
• ID requirement
• Healthy
• Ecological
• Environmental friendly
• Country of origin
• Shelf life
• Allergens
• Nutritions
• Tara
• Substances

Some of these are registers values (Warranty type, Nonsale type, ID requirement and Substances). New register values will be created by import if register's code is unknown (before update user is informed that new register value will be created).

Manage tandem/alternative GTIN's (RTC-14421)

Alternative (tandem) GTIN's can be added to the item, and be deactivated, activated and set as main GTIN. It is not possible to add GTIN which is already used by another item.

Fix: Add supplier on store level (RTC-15446)

It's possible to add supplier on any level: store, store group or common, as well as edit supplier on any level. Dropdown for stores, store groups display data in format reference + name.

Tandem - change main GTIN (RTC-14429)

When GTIN is changed on an item, the old GTIN is saved as an alternative GTIN (in the Item.GTIN table, isMain=0). GTIN visible on the item in Item details is saved as the main GTIN (in Item.GTIN, isMain=1, visible in the Item.Item table). When a new item is created using a GTIN which is an alternative GTIN for existing item, this GTIN is removed from the old item and set as main GTIN on the newly added one. 

Mass update of store prices (RTC-15757)

There are 12 new columns in grid during import via mass update of store prices:

• New net price
• Current net price
• Difference net price
• Difference net price %
• New retail price
• Current retail price
• Difference retail price
• Difference retail price %
• New gross profit
• Current gross profit
• Difference gross profit
• Difference gross profit %

Creating users from Azure AD (RTC-15608)

First name and Last name, split from Display name, are added automatically to the user when creating it in User management. 

First name, Last name, Display name of existing users can be edited.

Users removed from Azure AD (RTP-13388)

When a user is removed from the Azure AD Group in source AAD the user is blocked from logging in in the destination AD. If the user is added to the Azure AD group again in the source AD we did not unblock the user in the destination AAD. This is fixed and we are checking the "Block sign in" flag on the user from the destination AAD. 

Store/team/profile name and number (RTC-15754)

Both number/reference and name of store group is displayed in views: "Export store prices to Excel" and "New/edit price calculation". New column "Store group code" is added to the store prices grid.

Correct signs in exported store prices (RTC-15923)

When exporting store prices to Excel correct positive/negative values are preserved.

Mass update of store prices from Excel (RTC-15756)

In case of duplicated store prices in the same import file, the last one is imported. In import items grid the duplicates will be still visible but only the last one will be imported.

Filtering store prices by permissions (RTC-14068)

All store prices, which the user has access to shown in the price grid. Same for store groups in multi-selects.

Exporting items after store price update (RTC-15577)

Items are not exported (to blob storage) after store prices are created or modified.

Active substance (RTC-14796)

There is a dropdown field Active substance visible as the last field before the checkboxes in the Sales section in Item details. Values visible in the dropdown are taken from the Active substances register. Only active values are available there.

ID requirements (RTC-15491)

ID requirements dropdown values in item details are displayed as 'code-name'.

Select Stores/Profiles/Teams when exporting store prices to Excel (RTC-14214)

It is possible to export store prices to Excel for desired stores, profiles or teams. The multiselect field placed below store level user can filter within stores, profiles or team (depending on the level and user roles) and choose which store prices should be exported and viewed in Excel sheet. 

Mass update of store prices from Excel (RTC-13234)

When selecting mass update from Item details grid or Import grid, you can select to update store prices. Use same Excel template as you get when exporting store prices to Excel.

There are a few validation rules:

• Item not found
• Price/Wholesale price is not defined
• Price/Wholesale price must be above 0
• "Valid to" in the past will be ignored.
• Only today or future dates are allowed for "Valid from".

Currency column in the export will be available in the coming weeks.

 There are mandatory fields, which if any is missing will cause exception and status "Error" on validation. Proper messages will be added later.

Mandatory fields:

• Item identifier (GTIN, Item number or SKU)
• Stores/Profiles/Teams
• Valid from date
• Wholesale price
• Retail price

Commission percentage (RTC-13046)

It's possible to enter/edit commission percentage with maximum of 2 decimal numbers. 

Active substances register (RTC-14797)

Active substance register is visible in Sale column in Item registers. It is possible to add new active substance by using Add-panel. Active substances can be deactivated or reactivated. One of the substances can be selected as default. Code of every record must be unique. It is possible to set max number of items in one receipt in "Allowed number in receipt" field.

Display price per CU in TU items (RTC-12087)

When an item is a TU item and Quantity in supplier package is provided, the store prices include an additional column with price values per CU item.

Users with pending invitations to Azure Active Directory (RTC-15096)

If a user has a pending invitation to a tenant and is added to User Management of this tenant, they will be granted access to this tenant when they try to login. When they select the tenant in the tenant selector, they will be presented with the window to accept the invitation and they will be immediately logged in after accepting it. 

Spaces not allowed in externalItemNo (RTC-14257)

Spaces at the beginning or end of the value for External Item Number (identifier) will be trimmed during Import. Same for "Use file" in item lists.

Columns in RIGAL export to Excel (RTC-13280)

The columns containing price information are exported together with item information columns when exporting 'Item details from import file' from a RIGAL import file. 

Reject items (RTC-14243)

There is a confirmation dialog before rejecting selected items in import.

Add size when creating new model (RTC-13918)

When creating new model or adding items to existing model, and when adding new size in size wizard, the'display size' field is set same as size name by default.

Save changes question in item list (RTC-13765)

Save changes question appears only when trying to leave the view using breadcrumbs or the browser's 'back' button while creating a new item list. 

Notifications for mass-update of prices (RTC-12237)

Notifications are displayed when uploading, revalidating, or importing a file for mass-update of prices. 

Import of profile prices in RIGAL format (RTC-13390)

RIGAL format with profile prices can be imported. Store groups of type profiles are matched with RIGAL store numbers. If the profile is not found, it will use store with this RIGAL store number. If both store and profile have the same value, the profile is taken.

Performance in import (RTC-14330)

The batch size is set to 6000 rows for inserts into staging tables to reduce the risk of timeouts.

Item fields 'Warranty type' and 'ID requirement' are added to the Sales section in Item details. Both fields are saved on the model level and are not mandatory. The fields are dropdowns containing active values from the corresponding registers. 

Shelf life (RTC-13430)

A field for "Shelf life" (saved on model level) is available in the "Food" section, below the "Country of origin" field.

External model number (RTC-11907)

External model number is shown in the 'Model' section in the item details view. This field can be edited using the manage model button, then selecting the option to change external model no. The value must be unique amongst all models.

Default margin (RTC-13261)

The field "Default margin (%)" field (item level) is available in "Price" section, below "VAT code" field. The value defined here will be used as default margin when creating a new price. Please note that business logic for the price functionality will be added later.

Adding new items to an only-color, only-size model (RTC-14067)

It is not possible to add a new item with color and size to only-color/only-size model. Missing size/color needs to be added first to an existing model. It is possible to add new items, which are the same type (only-color/only-size).

Item list from file (RTC-12687)

A validation message appears in the "Use file" popup when creating or updating an item list to inform a user that the header of the file is incorrect or missing. A message appears at the bottom of the page to inform that some items included in the file do not exist in the system. 

Export store prices to Excel (RTC-13232)

Store prices can be exported to Excel from Items grid, Item lists, Item segmentations, and Promotion offers. "Export prices" button expands into two options: "Export wholesale prices to Excel" and "Export store prices to Excel". 

Date and time picker (RTC-12971)

There is a date picker without a time picker in Export wholesale/store prices to Excel views and New wholesale/store price views when ordinary price type is selected. There is a date and time picker in New wholesale/store price views when campaign or member price type is selected.

Export to Excel of mass update files older than 14 days (RTC-13966)

Export to Excel for mass updates of price calculations that are older than 14 days are blocked. This is due to an automatic cleanup job which runs after 14 days and cleans up the data, resulting in the file being empty upon export.

Changes in Item details page (RTC-13685)

'Customs tariff no.' is moved above checkboxes in Procurement section. All checkboxes are moved to the bottom of the Product classification section. Sale section is split into Price section and Sale section. Food section is displayed as the last section (after Product information section).

Item list 

Item list/Item segmentation API - Include price (RTC-13019)

Requests including both store price and item information can be performed for Item lists and Item Segmentations. It can be filtered by date and store/store group.
Items without prices are also returned.

Reject rows in import (RTC-11553)

It is possible to set the 'Rejected' status on rows that were not imported in the Import details view of all import types using the button 'Reject items' placed in the toolbar. Rejected rows are hidden by default and can be seen separately from active rows when the Status filter is set to 'Rejected'. Rejected rows cannot be imported directly but they can be revalidated and then imported. 

Item and price control for RIGAL files (RTC-11551) 

When opening item details for RIGAL files the columns includes Store number, New retail price, Current retail price, Difference retail price, Difference retail price %, New net price, current net price, Difference net price, Difference net price %, New gross profit, Current gross profit, Difference gross profit, and Difference gross profit %. Values for 'Current...' columns are filled out only if there exists a currently active price for the same store on the item. 

Rounding rules for store prices (RTC-14058)

Rounding 0 (set in the rounding rules register) rounds prices to the closest value with 0 at the end of the price value. When 5 is the last digit it will round to the higher value. If for example you want to round to the nearest whole value for all prices below 10,5, set the rounding rule to be 1,2,3,4,5,6,7,8,9,0.

It won't be possible to round to the exact 0 value (price=0).

All roundings for a price will work with standard mathematic rules.

Import

Deposit item (RTC-12225)

The field named 'Deposit item' is visible at the end of the Sale section. In this field you can search and add a link to any item. After selecting an item from the dialog, the item name is displayed as a link and the 'Quantity' field appears. By default, this field is set to 1 and can be edited. After pressing ‘x’ icon on the item name, the 'Quantity' field is hidden and the search is available again.

Changing supplier on import items (RTC-7886)

Changing supplier in the Import grid is possible only for file type PRICAT. The main supplier for import items is taken from the whole import. OriginalJsonContent shows the original import file and JsonContent is updated with the import supplier when any change is applied. 

Item list

Permissions for item lists (RTC-11610)

Permission 'Manage item lists' is available under 'Item - item > 'Item list' section. This permission is required to create and update item lists in Item management. Export of prices and items within Item lists can be done without this permission. Item lists are accessible in read-only mode with the 'View items' permission. Item lists can be used in Promotion without the 'Manage item lists' permission. 

Import

Outdated validation of import (RTC-13665)

Import is counted as outdated when the last validation time is more than one day (24 hours).

Import

Validation improvement (RTC-13141)

Manual revalidation of import works. Revalidation of a partially imported model keeps status of already imported items.

Outdated validation of import (RTC-8074)

Any kind of import, which was revalidated 30 minutes or more from the moment of import will be stopped. If part of items selected to import was validated they will be imported. Outdated items (modified after validation time) will not be imported, and notification will be displayed. To get import done the user must revalidate before importing the items.

Item list

Edit item lists / Unsaved changes (RTC-11613)

Existing item lists are by default filtered to show only the selected items. After a list is created and reloaded, it also shows only the selected items. 

When creating an item list and trying to leave without saving the list, the 'Unsaved changes' modal appears. 

Item register

Nonsale type (RTC-12571)

Nonsale type register is available in item registers. It is possible to add, edit and deactivate rows in the register.

Price

Rounding of store prices (RTC-8438)

A button "Round price to {amount}" is available in store price details view, below the “Retail price” field, displaying the retail price amount after it will be rounded. The rounding is defined in Item register\Rounding rules.

Import

Show warning when modifying size (RTC-13250)

Modifying the size on an existing item with any kind of import will show the warning "Size is modified". Same for color with the warning "Color is modified".

Item details

Allergens and nutrition (RTC-13123)

Item details sections for allergens and nutrition is placed at the bottom of item details.

Item list

Use another item list to select or unselect (RTC-11457)

By using button 'Use item list', it is possible to include or exclude items within an item list that is being created or edited.

System

Delete items from database (RTC-12620)

Index is added to improve performance when deleting items manually from the database.

Item details

Items with multiple distribution packages (RTC-11873)

Items can have multiple distribution packages, for example boxes and pallets.  In item details it is shown which TU items a given CU item is linked to. If CU item is not linked to any TU item, Quantity in supplier package field is visible for defining packages without barcodes. Whenever a CU item is linked to a TU item, the field disappears and the number is taken from the TU item. Units of the packages visible in item details of a CU item are fetched from the TU item. 

Item list

Edit item list (RTC-12053)

Item lists added to promotions can be edited. Clearing selection changes ToDelete flag in the database to true so that unused lists and segments can be permanently deleted. 

Import

Allow store prices with date in the past (RTC-12992)

Store prices with the starting date in the past can be imported when using RIGAL import. 

Item details

Fix: Can't open or find items when text attributes contains a date format (RTC-12961)

Values with date format (XXXX-XX-XX) can be saved on every string field.

Item list

Create promotion from item list (RTC-11030)

It is possible to create a promotion from a new or an existing item list by clicking Create and Promotion in the Item list details view. Please note that you should not use this feature unless you are using the Promotion module.

Item segmentation

Bugfix: Segmentation fails when filtering with item group (RTC-12613)

A segment in item segmentation can include (and be recalculated) filter group with Item group or Subgroup as an attribute.

Import

Bugfix: SupplierDiscount from price rule not used (RTC-12884)

All discounts are added from the import rule when importing with PRICAT.

Import updates will always export the items to external systems.

Item details

Unsaved changes (RTC-698)

When there are unsaved changes in item details and user selects function to Add new items, Change color or Change size, unsaved changes dialog is shown (with 'Discard changes', 'Cancel' and 'Save changes').

Item segmentation

Failed calculation of segments (RTC-961)

When the segmentation calculation fails, the status of the segment will be reverted to the one before calculation. The user will get a notification that the calculation failed.

Mass update

Dynamic price calculation: Change price calculation rule of existing prices (RTC-915)

Mass update can be used to update an existing price with a new price calculation rule. All lines in one import file must contain the same price calculation rule. If not, a validation error appears saying: "Conflicting price calculation rule code".  If a price is exported with one rule and this rule is updated in the exported file to be imported as an update, field mapping takes place and values are one by one assigned to the subsequent cost price fields corresponding to the new price calculation rule. In Mass update summation rows are also mapped but they are not filled out. This will be changed in RTC-3569 [Dynamic price] Export. All cost price fields for the new rule must be provided in the file. 

Price

All price calculation values are required when importing (RTC-718)

All cost price values corresponding to the used price calculation rule must be provided when importing prices using Mass update or import through API (for example from Temalogic). If some values are not given in the import file, price is not imported and validation error appears: "Missing cost price values". Imports that use import rules work as before.  

System

Logging of tenant ID (RTC-764)

Logging in Application Insights for API calls (both OK and Failed) includes tenant ID, which will make it easier to identify and analyze error situations for different retailers.

User management

Hide disabled stores in user details view (RTC-971)

Inactive profiles, teams and stores will not show up in the store access list in user details view. When editing store access, it's not possible to select inactive stores, although they will still be visible in the dropdown menu. 

System administration

Support for cashier login with on premise as identity provider (RTC-878)

EG Cloud (Chain Web Shell) support a locally installed IdentityServer as identity provider in addition to Azure Active Directory. This can enables the feature of accessing Chain modules in the cloud by using simple cashier login on premise. The security is maintained since the device needs access to the store local network to log in. The access token issued by Chain Web Shell contains information that this login was done by cashier authentication and the different cloud modules can allow or disallow usage based on this information. Initially this feature will be used by Mobile POS app to make it more efficient for several users to share mobile devices, just using cashier logout/login when switching user.

Import

Min/max validation for price input fields in import rules (RTC-911)

For import rules, fields in the price calculation tab (item import rules details) have limited values. For positive fields it's a range between 0 - 9999% and for negative fields it's a range between -99% - 0%.

If the user tries to add a value above this range it will change it to boundary value, so no validation message needs to be displayed.

Mass-update of prices - wholesale price in currency (RTC-830)

It is possible to create/update currency on price calculations using mass-update.

The price will be counted for the field "Preorder Wholesale price in supplier currency".

If currency column is not included in the in mass-update import file or the value is empty, currency value will be set by default to MainCurrencyCode (NOK).

For now, it also affects updating planned prices with a different currency value (causing change of currency in planned price), which will be resolved separately (will be fixed in: RTC-9966)

Item details

Error message when saving item with inactive values (RTC-766)

When there is some deactivated register value which is used for an item, the user will get  information: validation "Inactive value selected". When the item has some inactive values it cannot be saved, and the user will get an error message.

Fix for item details in mobile view (RTC-725)

When opening item details in in mobile view, buttons etc. are displayed properly. 

User interface design for profile attributes (RTC-877)

Design for profile attributes in Item details view and Import rule details view is improved: Display of attribute fields is more clear and easer to read.

System

User interface improvements for notifications (RTC-819)

• Shadow around the notification panel

• The bell icon is lined up with 'Username'

• Hover on the bell icon works the same way as in the case of 'Username'.

Item segmentation

Filtering improvements (Work ID: 189194)

Filtering on measures are using centimeters. A problem with time range in date fields is fixed.

System

Item free-text search error handling (Work ID: 185966)

The item free-text search is using the search engine ElasticSearch. If updating ElasticSearch fails, the indexing job will retry to make sure the search data is updated.

Import

Using price calculation rules in import (Work ID: 188805)

Import of Pricat both from supplier and own brands, and import from Temalogic, are using price calculation rules defined in import rule or included in import file. The same business rules are applied as described in relation to price calculation in import rules.

• Pricat for suppliers (itemUnplanned): Prices created from an import rule use the specified price calculation rule, and cost price values are applied from the used import rule. Wholesale price, rec. retail price (sales price) and supplier discount (cost price) are taken from import file. If the calculation rule does not have supplier discount, then this value is ignored. Prices can be updated using import when the same price calculation rule is applied. It is not possible to update price using different price calculation rule since validation error appears on an import line. 

• Pricat for own brands (Pricat itemPlanning): Creating and updating all types of prices is possible when importing Pricat for own brands. When creating new price, price calculation rule is taken from the import rule. When updating existing prices, the same rule must be set in the import rule used as the one used to create this price. If not, validation error will appear. Value1, value2, etc. in the price contract are mapped one-one with the rank of our rule set rows (e.g. value5 is mapped to the fifth rule set row), however, summation rows are skipped.

• Import from Temalogic (using API, with only planning code and no price from date): Creating new ordinary prices is not possible with import from Temalogic. It is, however, possible to create campaign/member prices and for these the same calculation rule as on the existing ordinary price (active in time of campaign/member price start) is applied. Difference between planning code on the imported campaign/member price and the existing ordinary price does not matter - rule from the ordinary price with corresponding date range is used. When updating existing prices using Temalogic, the same rule is automatically applied as the one used to create this price. Value1, value2, etc. in the price contract are mapped one-one with the rank of our rule set rows (e.g. value5 is mapped to the fifth rule set row), however, summation rows are skipped.

System

Showing long texts in user interface (Work ID: 189234)

Long texts without spaces in fields will be wrapped.

User management

Access to stores for new users (Work ID: 191567)

Self provisioned users will by default not get access to any stores. This has to be given by administrator users.

Changing language (Work ID: 189149)

When user selects to change language and saves, the language will change immediately.

Item details

Item image in Item details overview tab (Work ID: 180985)

Images that do not fit the frame will be resized to fit the frame but without changing proportions or being truncated.

Item image in Item details overview tab (Work ID: 181986)

When there is only one color (variant) with image the same image will be displayed for all other items with no image in Color section. It takes the first item by size order and displays thumbnail image on all items in this color.

Item segmentation

Permission for item segmentation (Work ID: 182485)

Item segmentation has permission for "View item segmentation" and "Manage item segmentation". With "View item segmentation" permission the user can only view and export the segmentations, but cannot modify or recalculate (re-run the segment).

Price

Valid from filter with 'is equal to' operator (Work ID:182080)

When filtering with valid from the local time-zone is used.

System

Notification activity (Work ID: 184946)

In the notification grid the activity value shows what initiated the notification. Current values are Segmentation, Import and Export.

User management

System administrator role (Work ID: 188686)

All permissions are available for the System administrator role.

Export to Excel

Notification when Excel file is ready to download (Work ID: 181014)

When exporting items or prices to Excel the user will get a notification when the file is ready to download, or if an error occurred. The file can also be downloaded (later) when selecting view all notifications. This new feature makes it possible to export larger files with many items, without getting a timeout after 10 minutes. Please note that large export will take some time. A test with export of all item attributes for a given brand with 161.000 items resulted in a file of 96MB (161K rows x 180 columns), and took approx. 90 minutes to generate.

Export to Excel (Work ID: 175090)

The generated Excel file will get file name with date and hour based on the local PC settings. Date is generated based on time when clicking 'Export to Excel', not when the file is ready for download (in notifications).

Price

Column picker in price calculation and store prices grid (Work ID: 178775)

Column picker and new columns is added to Price calculation and Store prices grids. Locked columns feature has been implemented for them with drag and drop and resize columns functionalities. There is a navigation link (same as in item grid) on column 'Valid From' (both in Price calculations and Store prices). 'Valid From' column must always be visible and it is not possible to hide it. 

System

Fix for loading of menu (Work ID: 185083)

A minor issue related to loading the menu is fixed.

Global design change for buttons (Work ID: 178485)

Design and texts for buttons are modified to handle many buttons in a mobile view. Only buttons with enough space are displayed. New 'expand' button is added, which expands buttons grid and displays all of them.

User management

Synchronizing stores to User Management (Work ID: 183199)

Permission can be defined for specific stores or groups of stores. Stores are therefore synchronized from Store Management module (StoreService), using jobs in integration package IdentityServiceIntegration. The jobs are responsible for getting changes on stores from blob and moving them to staging tables in Identity database (StagingImport). Then from staging tables stores are imported to the actual store tables (StagingMerger). StagingMerger is run on Cron trigger with every 10 seconds as default. Default we do 10 retries when a data row is not processed first time. Default batch size is 5000 rows. StagingImport is triggered on change in blob (batchtoprocess > store).

Store permissions (Work ID: 180487)

Users can get access to selected stores, teams or profiles. User roles can be defined as common or for specific profiles, teams or stores. After access to a store is taken away from user, roles with access to this store are automatically deleted from this user. Role type cannot be changed after being created. 

This feature will not be in use before permissions for store prices is released later in October/November.

Import

Keep profile discounts when importing (Work ID: 183779)

In price calculation tab in import rule there is a flag for 'Keep profile discounts'. When using PRICAT import with the flag checked, profile discounts are taken from the previously existing ordinary prices for the same planning code on an item. Profile discounts are always copied from an ordinary price which is/will be active at the time when the imported price starts. It applies only for ordinary prices. If there exists only an expired price for given planning code, then values are copied from it. The flag has no effect on Temalogic import since import rules are not taken into account in this case.

Note: In case of adding a new size to an existing color by import, prices from a different (existing) item are copied to this newly created item. If the new item is imported together with new price info, discounts for this new price will be applied from the import rule just like there would be no other prices on this item. To have discounts copied from a different price (existing on different item and copied to this newly created item) new item must be created first with no new price info and the new price must be then added in a separate import.