Fix: Export of Order points (RTC-37152)

Adding, updating or deleting order points via user interface on store level triggers export to 3rd party in blob Item.ItemStoreOverride.Export. When performing these actions on order points on common level, blob Gateway.ItemChanges is exported. Export is triggered also when items are updated by import.

Fix: Excel import and export improvements (RTC-37263)

The store number field is not always checked by default in the export view. 
The Stores field and the Include common values option in the export view are hidden and appear when the Include values per store option in the Store local fields section is checked. Active assortment and Scale fields also appear as selectable for export after the above action. Store local values on the common level are not updated when the user does not have Update existing items permission.

Fix: ItemService package stopped after release (RTC-36451)

In a situation that ItemService package is restarted while there is a long execution of a job, it finishes with status 'CompletedWithWarnings' and is resumed after package is correctly started. 

Translation corrections (RTC-36650)

Translations for Quantity in supplier package, Min.ord quantity and Auto replenishment are correct.

Fix: Duplicated prices in the same file (RTC-36159)

When importing a file in which there are prices for the same item and store group, but with valid from date in the past, only one active price will be created. Its price value will be taken from last row imported (with valid from date set in the past). 

Fix: Currency and active status in wholesale price tab (RTC-34589)

Wholesale prices are shown with their supplier currency and amount. By default only active price is visible, but the user can change filter on 'status' column. There is only one active wholesale price for item, even when there are created multiple different prices with the same ValidFrom, then one of them will have status 'active' and the rest 'expired'.

Fix: Removed scales (RTC-35993)

In Excel export, which includes column 'scale', only those scales which are currently assigned to item are exported. Removed scales are not exported.

Fix: Moving items between models (RTC-36812)

Two situations in which it is possible to move model items are additionally supported:

First is importing file with updated items from the same model, but first is moved (by external model number) to another model and second stays in original model. Then items are correctly updated and moved accordingly to imported external model number.

Second is importing file, where item is found by alternative GTIN and is moved to model (by external model number) with the same color/size variant. Item is moved to model correctly, merged with duplicated item and alternative GTIN is assigned as main (previous main GTINs are now alternative). 

Fix: Filter item grid by item group hierarchy (RTC-35674)

It is possible to open side panel for filtering on item groups in items grid. User can select item groups to filter on from dropdown checkboxes segregated according to group hierarchy. Deactivating certain element of group hierarchy is possible only if all 'children' elements contained in it are inactive. There is an error message shown on the bottom of the page when the user tries to deactivate element when there are active 'children'.

Fix: Item-store link is created when a store is added to a profile (RTC-32934)

When creating prices for profiles or price zones (with system parameter 'active assortment' disabled) item-store links are created for every active store, which is contained in 'higher level' store group. If a new store is created and added to an existing profile, for which prices are already created, item-store links on items with these prices are created for this store. The same happens if an inactive store is activated or already existing store is moved to a profile. When the system parameter 'active assortment' is enabled, for newly added store item store-links are only created when the item is added to this store's active assortment. 

Break bulk flag instead of break bulk code register (RTC-34512)

Break bulk code is obsolete and not visible in the user interface, both in the register and item details. Break bulk is a flag, by default set to false, that can be defined on item. Break bulk flag can be exported to Excel and 3rd party, as well as imported (via Excel, Item.Item and RIGAL). Segments in item segmentation, which use break bulk filter can be counted. If item was created when register was still in use, in database in BreakBulkCodeId column in Item.Item table, there will be an old value, but for new items, there will be NULL.

Order proposal attributes and email for purchase orders (RTC-36339)

Supplier registers have following fields in the procurement section: Text field 'Email for purchase order', decimal  'Free freight' and flags 'Replenishment' and 'Generate order proposal'. Values can be imported and exported via Excel in accordingly named columns from supplier registers view. 'Free Freight' value cannot be lower than 0 and validation for 'Email for purchase order' to be in mail format is added. Export of Supplier register for 3rd party also contains these fields.

Currency rate (RTC-36058)

In contract CurrencyRate the flag 'isDefaultForCountry' indicates if exported currency is set as default one for country in which the store is located in.

Sales unit in Orderability details (RTC-36430)

API GetOrderabilityDetails includes 'localizedSalesUnits', which contains information on sales unit of scanned item (item, which is sent in request) in all languages that the unit has name in the registers.

Assortment code (RTC-36083)

Assortment code column is available in Label Printing grid (hidden by default). Only values on item level are shown. User can filter upon this column.

Export items and prices for new stores (RTC-22481)

All exports from Item Management are maintained via Export.BlobType table. After export we save data in the tables [Export].[ExportHistory] and [Export].[ExportHistoryBlob]. The data stored in the database is: start and end time of export, number of exported entities, type of the entity, blob url. This data is saved after the export of changes for which GenericExport job is responsible.

Import of stock status from Inventory (RTC-35573)

Database is extended with table Item.ItemStock, where information on item, store, different type of stock quantities and audit columns are stored. Stock changes are imported by job 'ItemStockImport' whenever Inventory.StockStatus.Export blob is exported. This blob contains maximum 500 rows and the job can process all of them in one execution. If stock is exported for an item or store, that does not exist in database, the job finishes with status 'CompletedWithWarnings'. 

Fix: Store Local Attributes cannot insert duplicate keys (RTC-36408)
It is possible to import multiple import items with store local attributes for the same item and store. Also, if item already exist in database with store local attributes for certain store, then user can update them and import new attributes for another store. When in import, there are different values for the same attributes on item, the last one imported is set on an item. 

ShelfLabel1 adjustments (RTC-35611)
Long supplier names are cut, if they exceed the length of barcode. Label text, supplier name and assortment code fonts are smaller, to not cut bottom parts of characters. Margins of labels were moved to fit perforated paper. 

Fix: Profile country code (RTC-36374)
Country code in profile is updated in database after changes in Store Management user interface. 

Fix: Import file with the same new items multiple times (RTC-36288)

The import can handle creating new items when the file contains copies of the same item.

Missing translations in Price Control and notifications (RTC-34620)

Norwegian and Swedish translations are added to Price control columns and side panel. Default name of the exported file is translated to correct language, depending on language settings when exporting 'Item and price' to excel. In price calculation view previously Margin(GP) is renamed to Margin(Gross Profit) and translated.

Fix: Showing the same row for multiple stores (RTC-35207)

In active assortment grid rows for each item-store pair are shown only once.

Moving items between models (RTC-34500)

Items can be moved between models using import (Excel mass update and Item API), according to the following rules:

• When importing already existing items and assigning external model number, which is already in database, these items are move to model with following external model number.

• If in model there exist item with the same size and color, GTIN from moved item is assigned as Main GTIN, while existing one becomes an alternative GTIN (tandem)

• When an item is imported with a new external model number and that number is available in our system - a new model is created and the item is moved to that model

These rules apply when creating new items as well. Models can consist of combination of variants, that does not follow the same pattern of having size, color or both.

Logging exceptions per item in import (RTC-36042)

If faulted data is imported, ApprovalImport job is finished with status 'CompletedWithWarnings'. Exception is not logged per item in job logs, but is saved in database.

Filtering on supplier number (RTC-36205)

Default filter operator for columns in items grid, which have 'number' in name has been changed to 'is equal to'. This results in faster searching for item by default filter.

Segmentation on external model number (RTC-35182)

The InList operator is available for string fields when creating groups in segmentation.

Database, Import and Export (3rd party) (RTC-19907)

Auto-replenishment, Can be ordered, Stop sale, Weight declaration are in Item.Item contract store local attributes section. 
Store local values can be imported by importing Item.Item.
Store local values are exported via Item.ItemStoreOverride.Export blob type, values for order points on the common level are exported to Item.Changes.

It is possible to import order points, edit and delete them.

Order points imported with a valid from date in the past will be imported with today's date and the user will receive warning about this during import. Order points imported with a valid from date in the past, when there is already an active value for a store/item pair, will be ignored during import and the user will be notified about it. Valid To date is ignored.

There is a validation in import that order point min must be greater than order point max and values must be greater than 0, the user is informed via an import error.
A table storing store local vales for store-item pairs is added to the database under the name [Item].[StoreLocalAttributes].

Price contract includes total supplier discount (RTC-35003)

Gateway.ItemPrice contract includes total supplier discount. This value is a sum of negative discounts based on wholesale price. Positive values are not included and in a situation, when price calculation rule has only positive discounts, in contract there is exported 'null' value. 

Performance when importing items and prices (RTC-18385)

Import performance is improved by around 50%. When importing from import grid or items in an import grid, validation and automatic import is done without the user having to perform an additional action.  If the validation ends with an error, the import is not carried out. If the validation contains warning, items are imported automatically. The button for PRICAT import and this type of import is removed. 
Files with duplicate new items are imported correctly.

Fix: Update of GTIN in import (RTC-35678)
GTIN can be updated only by users with "update existing items" permission.

Product series (RTC-34663)

Product series column is added in three grids: items grid, items in item list grid and store assortment. Column is hidden by default. It is possible to sort and filter on this column.

Fix: Item grid performance (RTC-35928)
Item grid query is faster.

Fix: Loading of store prices (RTC-35414)

Store prices are loading correctly and request is sent only once when opening StorePrices tab. Changing items between model results in showing correct prices (assign to correct item from this model). 

SKU without leading zeros (RTC-35799)

For new items, SKU is generated with no leading zeros. Next available number is assigned to an item. Updating already existing items has no influence on their SKU.

Order in export from Item Master (RTC-35867)
Whenever item with price is created and activated, the order of blobs exported from Item Management is Item, Price, Store link.

Item Order details (RTC-34627)

There is an API GetOrderabilityDetails to the ItemService endpoint, which returns information about whether an item is a consumer unit or a trading unit and information, item properties such as sales unit, whether item can be ordered, quantity in supplier packages, as well as link of linked consumer or trading unit items. When list of trading unit items is returned, default order unit is marked.

Import of wholesale price changes (RTC-34144)

In import details and items in import, there are columns "Wholesale price in supplier currency", which shows the price that is imported, and "Current wholesale price in supplier currency", which shows the price currently active for the given store/store group.  Wholesale prices are shown in these views with the currency code in which they are imported or exist.     
The Pre.Wholesale price column is still visible in the item details view, but will not be used so it is empty.

Fix: Performance when creating price (RTC-35567)

For systems containing big amount of labels, performance of inserting prices is improved. 

Fix: User can't add rows to price calculation setup (RTC-35103)

New rows can be added to the price calculation setup.

Fix: Allowing more filter groups than 32 (RTC-35181)

Segmentations can be created with more filter groups, limit of filter groups in one segmentation is set to 500. Old segmentations containing exactly or more than 32 groups cannot be accessed or changed, new segmentations must be created. For ones containing less filter groups, they can be accessed and calculations are correct. 

Fix: Assigning existing GLN to supplier (RTC-33221)
SupplierNO and GLN must be unique so the user sees a corresponding notification when these values do not meet the requirements.  Error 500 is no longer displayed and the user sees the message "This field must be unique".
Fix: Supplier web address (RTC-32191)
Adding a website address when creating a new supplier is possible.

Fix: Avoid copies of the price created at the same time (RTC-31566)

Updating active and future price does not create duplicate future price for an item.

Fix: Wholesale prices tab timeout (RTC-33359)

Opening wholesale prices tab, as well as filtering on columns is fast. There are no timeouts when loading wholesale prices for item. 

Creating new VAT codes (RTC-33528)

When user creates VAT code which is a first active VAT code for a specific country, this VAT code is automatically set as a default VAT code. Then, when creating prices for that country for new item, user does not need to fill-in field in item details regarding VAT codes.

Stability and performance of item imports (RTC-23586)

Working jobs interrupted by a package restart via Integration Platform management or via Integration Platform package release or via web job restart (in Azure), is resumed afterwards and completes its work.

Fix for: Assortment code per profile (RTC-33740)

Item is exported after change in assortment code per profile.

Fix: Letters typed in product information fields (RTC-33724)

Product information fields in item details can be filled with "w" and "r" without being taken to price calculation window. Other fields in item details can also be filled with hotkeys letters. 'W' and 'R' takes user to price calculation view with focus on accordingly wholesale and retail price fields, when user is not in any input field.

Order of labels in item lists (RTC-32816)

When printing labels from item lists, it is possible to set order. Items added to item list via user interface have order '0' and will be printed in order by created date ascending. User can add items to item list also by 'use file' option in item list view, then order of labels to print will be set the same as the order of items in the file. Every item added by import gets next available number and will be printed after all items with order '0'. In a situation that user adds the same item multiple times, the order will be set as the last action of adding the item. When excluding items, the rest of the items stays in the same order. Order is not visible in the grid, only when user prints labels from item list. When including items to item list by 'use item list' option, the order of all added items is '0'.

Fix: Searching by Store Number in Store Assortment (RTC-33603)

It is possible to filter on store number in Active Assortment per store view. When the user has permissions to access only one store there is no store number column, so search on store is not possible.

Fix: Timeout when searching in item text column (RTC-33501)

Searching for items by item text column returns results within 30 seconds. Filtering in item texts includes item texts for multicountry localized text (for all system countries).
Following operators are available during the search: is equal to, starts with and contains.

Fix: Searching by GTIN (RTC-33563)

It is possible to search by GTIN in Items in import grid. 

New shelf label types (RTC-30500)

ShelfLabel1 label type is available for use in Item Management. Labels can be generated manually from item details, or when added to label type of specific item, they are triggered by changes in price, GTIN, LabelText1, UnitPriceFactor, UnitPiceUnit, Supplier Name and Assortment Code. On label there is visible unit price, which if is equal to zero ( no UnitPriceFactor and UnitPriceUnit) is shown as retail price value. Layout for printing on vertical sheet is 3 columns of labels and maximum 11 rows on single sheet.

Fix: Creating store price for an item that has a new VAT code (RTC-33555)

Prices are created correctly when VAT rate starts today.

Export currency rates (RTC-32361)

When a new store is created, export of a blob CurrencyRate with all currencies per store is triggered. If currency's End Date is in the past, it will not be exported.

Fix: Excel cannot be exported with VAT code and rate (RTC-33498)

Item is correctly exported to Excel file, when user is exporting VAT code and VAT rate.

Fixed price columns (RTC-18946)

In import items grid (both in items in import and in details of a specific import), user can add to view columns 'Current Fixed Price' and 'New Fixed Price'. Values of those columns are checkboxes, which if checked signify that imported price is fixed. 'Current Fixed Price' shows existing value of flag on an item or on store price and 'New Fixed Price' value of a flag after import of selected file. In import grid 'New Fixed Price' value is either taken from current store price or if there is no previous price for imported store number - from item. The value shown is the same which will be on an item/price after import.

Fix: Multi-language item text: truncate item and model name (RTC-33366)

Item text and model name are truncated to 255 characters when a longer value is imported. 
Items are correctly visible in the item grid and it is also possible to enter item details when there is no default language, or when the default language is different from the language for which the item text is saved.

Fix for gap in vat code rate validity (RTC-30494)

Start date and end date is created with an offset corresponding to the time zone of the country for which the vat rate was created. It is also possible to edit the vat rate if its start date is today or is in the future. Vat rate must be a whole number not a decimal value. The registry only shows vat codes for countries that may be system countries, this also applies to the creation of new ones.

Fix: Performance and filtering in Store Assortment grid (RTC-32926)

It is possible to filter on store number in active assortment view. Default value of filter is set to 'is equal to'. If user has access to only one store, store columns are not visible so it is not possible to filter upon it. Item area values are visible in the grid. 

Changes on item via import (RTC-31620)

Any change made on item via import results in exporting an blob with changed item. When the same file is imported twice or it does not change anything on item, blob with item will not be exported. The same happens, when the only change is in price. If changes are made on item that is a model item, exported blob contains all items from the model.

Fix for multicountry item text (RTC-33231)

CountryLanguage does not duplicate in the cache, so importing items is possible. 
ItemText containing special characters is correctly processed and exported by GenericExport job.

Item text in multiple languages - import and export (RTC-30882)

Wholesale price (RTC-31867)

Wholesale price table contains columns as: Valid from, Status, Valid to, Wholesale price and Net price. 
The table displays the wholesale price that is created during the creation of store price. Unique wholesale prices are shown, which means that even if several stores have the same price, it will be shown only once.
Clicking on the valid from corresponding to the wholesale price will take user to the store price, the open store price is the oldest one (that matches Valid from date).

Supplier register: Export to Excel (RTC-23340)

It is possible to export supplier registers from supplier register's view by 'Export to excel' button. They can be filtered on and file contains only visible in user interface suppliers and columns (except for audit columns). 'View registers' permission needed. Nulls instead of empty cells are allowed only for 'Lead time (days)' and 'Transport time (days)' columns.

Fix: Brand register: Export to Excel (RTC-23340)
Null brand category values ​​are exported as empty strings. 'View registers' permission is needed to export Excel file with brand.

'Manage assortment codes' button (http://RTC-32121)

Button name is translated to Norwegian and Swedish accordingly to user's choice of used language. 

Export to Excel (RTC-28823)

User can export items from store assortment from 'edit' view. Clicking on the Export items to excel button open a view where user can select store group level, and desired columns. Prices existing on the item for only chosen store group level will be exported, for the rest fields will be empty. Checkbox 'Include value per store' in store local fields is checked as default. For exporting items user has to have permissions 'export to excel from items grid'. If user has access to limited amount of  stores and does not choose which store to export prices or store local values from, they will be exported for all stores item has prices on and user has access to. 

FIX: Removing ID requirement in import (RTC-32757)

Entering 'null' as a value of idRequirement in Item. Item import results is removing it from an item.  When user uses 'mass update' import  'code' columns of Id Requirement have to be NULL in order to remove the values from an item.

FIX: Currency rate at the same day (RTC-32143)

It is possible to edit sales and cost rates in the currency register, when the start date is on today's date.

External model number and ID requirement (RTC-31591)

'External model number'  and 'ID requirement' can be used to create groups in segmentation

API for label printing (RTC-24130)

Sending a request GET api/gateway/Labels/labelType - without store specified - results in receiving a message with all registered label types. The same results will be returned when there is an incorrect store number in the request. In a situation that a store is chosen in request parameters, only label types registered for that store are returned. Sending a non-existing number will show no label types in results. API can choose a language to translate the names of label types by setting parameter 'culture' to nb-NO, en-US, sv-SE, but default language is set to English.

It is possible to add labels to label printing by sending request POST /api/gateway/Labels/print. Label of specified type can be created or be ready to be printed  by request, only when the item has an active price and label type assigned to the item. If the same label has already been printed, it would be set as not printed, but if it was not existing yet, new label will be created.

Import prices with 0 (RTC-32571)

User can import prices, where retail price, net price or both are equal to zero. There is a warning shown when retail price is equal to zero. 

Fix: Filtering on GTIN column with different values of checkboxes (RTC-32616)

User can filter on GTIN column - using GTIN or alternative item (tandem) as value - with all of the options of the checkbox in item lists. Correct results are returned based on filtering in the column and value of the checkbox.

Fix: Sticker 2/3 barcode problem (RTC-32342)

The barcode on Sticker1 and Sticker 2 labels is larger and therefore more visible and scannable.

Filtering on GTIN  (RTC-31155)

Default filtering on GTIN column in: Label printing, Import details, Items in import, Item lists view is "is equal to". User can look for an item using GTIN value in this column, as well as Tandem GTIN value.

Mass update import: Deleting prices (RTC-31884)

Importing item with price in mass update containing column "Price is deleted" will have following impact on prices: If value is set to TRUE, all of the prices for given store group (profile/price zone/store) are deleted for this item. When prices are deleted for profile or price zone and item has also price on store level - and store is part of that profile/price zone - store prices are deleted as well. Importing value FALSE is not deleting any of prices, as well as leaving values in column empty.

Fix: Item area column (RTC-32069)
Item area column shows correct values on items,  both in items grid and items lists view. It can be filtered and sorted upon. 

Use file (RTC-31872)
Including or excluding items in the item lists can be done using alternative GTIN (Tandem) as values in column GTIN. Tandem GTIN values are used only as a lookup for an item.

Multicountry: Store prices with time / Always create new price (not edit) (RTC-30820)

• Valid from date and time is displayed in store price details and in store price grid. It is possible to create a price with the selected time. 

• In the user interface it is not possible to edit active price. Only the future price can be edited via user interface. If the user wants to edit active price for given store, user creates a new price.

• When importing price that has valid from in the past (past = can be the same date, but 2 hours earlier) new price is created.

• Future prices can also be edited via import.

Price control grid (RTC-31424)
Column informing of price suggestion status is named 'Update type' and can have values such as 'New' or 'Price change'. There are links in price control and price control history grids, on the 'item text fields', that open item view for selected item. User can also click on a link on 'active' and 'new' retail price in price control grids, it will take it accordingly to a current store and source profile price view. In both price control and price control history grid, there are 3 frozen columns always visible to a user - 'Valid from', 'GTIN' and 'Item text'.

Brand register: Export to Excel (RTC-31001)
It is possible to export brand registers from brand registers view. They can be filtered on and file contains only visible in user interface brands and columns (except for columns containing dates/users). 

Fix: Item search modal (RTC-32232)

When selecting an item in item search modal (deposit and substitution item), the form is updated with it.

InternalSupplierNo in export of item changes (RTC-28310)

InternalSupplierNo value is added to supplier in export of item changes.

Barcode on sticker labels (RTC-31465)

• The barcode on sticker labels is taken from Sales code

• The barcode is encoded in code 128

• The labels are scannable

Price calculation (RTC-29715)

Margin (GP) % is calculated as (Retail Price excluding VAT-Net Price)/Retail Price excluding VAT. Boundary conditions for values are +100% and -10000%, when they are reached system parameter set in system is used for calculating its value. Very high or low values of margin percentage are rounded in UI to +100% or -10000%, but in calculations they're below this value (user can click on margin percentage and it's visible).

Import performance (RTC-27780)

Database queries are optimized to improve performance when importing items.

Weight declaration (RTC-31224)

Weight declaration field is 50 characters of width (more or less it depends on the characters). When editing this field user sees a horizontal scroll bar that informs about reaching the limit, the words that are behind the scroll bar are moved to the next line.

Database maintenance fix (RTC-27620)

ItemServiceJanitor: Deleting indexes in nightly trigger of jobs is refrased, so the job is not faulted.

Price import (RTC-31167)

When sending an Item.ItemPrice blob with 'deleted' status on price: if any prices for this store group exist on the item, they are removed. If there isn't any price for presented store group, contract is ignored and price is not created.

FIX: Fixed price on store price (RTC-31167)
If sent store price has ValidFromDate in the past and price is the same as it was before, but the flag on Fixed Price is different from current store price, price is updated.

Active Assortment (RTC-30823)

Columns in Active Assortment view can be filtered and sorted upon.

Fix: Print labels as store user (RTC-30196)

There is no 'Store' dropdown in print label modals if the user has access to only one store.

Changes have been made to the manual printing labels from item details and item list.

Better performance when exporting to Excel (RTC-30016)

When exporting all items/all store prices the performance is much faster.

FIX: New price created all the time when ValidFrom is in the past (RTC-30993)

• A new price is not created when it is the same as the currently existing price.  If the price in the system has a validFrom of 2021 and we update it with a price with a validFrom of 2022 but the prices are identical, new price is not created.

• A new price is created when it is different from the existing one. If the price in the system has a validFrom of 2021 and we update it with a price with a validFrom of 2022 but the prices are other than existing one, a new price is created. 

• A future price is always created.

• In case there are multiple prices within a single file for the same item/store/store group, where all of the prices have validFrom in the past, the last one (by order of appearance within the file) will be used.

Store prices in local time (RTC-25902)

Valid from in local time is exported with price in FromDate field. Obsolete version of valid from date is still exported in FromDateUtc field.

FIX: Keeping values when Excel import does not contain values (RTC-30617)

When updating item via mass update (Excel file doesn't contain following columns) values from these fields are not removed:

• substitutionItem

• riskItem

• categoryManager

• productSeries

• scaleLabel

• treatmentType

Price control (RTC-12193)

Price control entry can be found in main menu, under "Item" section. In right top corner there's Price control and price control history switch grid button. It is possible to navigate to price control history from price control grid. To access this grid user needs permission "Approve prices" on store level. 

Improved performance of Swagger user interface (RTC-30314)

Performance of Swagger user interface is improved. Loading of docs takes visibly less time. There is a new button that copies file-type name to clipboard. 

Import of unit price factor (RTC-29077)

If any of the fields unit price factor or unit price unit are specified, both are required. When importing, there is a validation error if there is only one field specified in the import file.

Generation of model number (RTC-27887)

The smallest value of generated ModelNo is 100 000, and the biggest value is 99.999.999.

Label types for stickers (RTC-29281)

• Three label types: Sticker 1, Sticker 2, Sticker 3.

• It is possible to print the labels on a stickers in a roll.

• Label size is 75x33mm.

• Sticker size is 45x23mm.

• Information on the label (Sticker1):

  • Price

  • Item text

  • Barcode (Code128) containing Sales Code

  • Sales code

  • Comparing price (price/liter, price/Kilo etc.) when that exist

• Information on stickers (Sticker2 and Sticker3):

  • Sales code

  • Barcode (Code128) containing Sales Code

  • Printing date (Sticker2 only)

• The currency symbol on the labels is Euro.

• Number of sheets required in printing modal doesn't appear for Sticker1, Sticker2 and Sticker3. 

Revert to "ready for import" (RTC-29703)

Reverting import to "ready for import" changes status of an import and triggers revalidation. 

Label types section (RTC-29834)

When there is more than five stores in the label types section, only top five of them are shown. There is a button underneath them, which takes the user to another view with list of label types per store. Label types that are on 'All stores' level are shown first.

Printing labels from item list (RTC-24213)

• User can print/create labels for all items in the item list.

• When not all items within the item list have prices for the selected store, user will see a warning that X out of Y items don't have prices for selected store. 

• User can print/create max 1000 labels from one item list

• Stores in the model are filtered by the user permission 'Manage store local values'

• Label types are filtered by the label type register. 

• Items that do not have a price for the store, their number is shown to the user in the notification. It is still possible to create/print label for the remaining items.

Import of franchise store flag (RTC-29209)

Price control is used for franchise stores. The FranchiseStore flag is updated based on changes in Store Management. 

Import of supplier item number (RTC-28902)

Import of RIGAL format supports RIGAL field 7.1.125 as an alphanumeric supplier item number.

FIX: Update of Item name (RTC-29313)

In non-model items, the model name is changed to the value imported in the item text field.

Model name for non-model items is updatable after changing item text manually in item details view.

FIX: VAT code when switching items within model (RTC-29313)

VAT code does not disappear when moving between model items.

Warranty type (RTC-29463)

The maximum value for warranty months is 999.

FIX: Large number of rows in label printing grid (RTC-29787, RTC-29907))

There is no timeout when opening label printing grid, and filtering is fast.

FIX: Alternative GTINs (RTC-29827)

• To manage GTINs/alternative tandems user needs 'Update existing items' permission or 'Manage local items' permission and item needs to be manage in store (where user has permission).

• Managed by store checkbox is visible on non-model items.

Permissions for alternative GTINs (RTC-28462)

User that does not have 'Update items' permission cannot add or remove GTINs/alternative GTINs. User that has this permission or Manage local item (and the item is managed by store), can add or remove GTINs for items.

Grid in model/variant/item level (RTC-24923)

State of grid is kept when changing 'browsing by' levels and after a page refresh.

Weight declaration (RTC-28385)

• Weight declaration is shown in its own section (one column).

• The whole text is visible in the preview.

• Text is editable in modal, in a text area roughly 40 characters wide and 20 lines in height. If the text is longer scrolling appears.

• Modal has the ability to decide whether to save the change on all elements/sizes/colors of the model.

Processing of labels (RTC-29689)

LabelProcessor perfomence is slightly better.

Export of alternative GTINs (RTC-29328)

• Deleted alternative GTINs are exported as 'Deactivated'.

• When an alternative GTIN is 'moved' from item A to item B, then alternative GTIN is exported with item B and item A has null value.

Stability in approval import (RTC-23108)
When a long running job is running, and a package is restarted via Integration Platform Manager or via release of Integration Platform package there is no exception and validation/import is resumed in next job execution.

FIX: Export of labels to 3rd party (RTC-29473)

Only the latest labels are exported (if there are more labels not exported). Next job execution doesn't export older labels.

FIX: Converting PLU field (RTC-29401)

When converting scale labels to Myhrvold in ItemServiceOnPremIntegration package, field PLU contains digits 3-8 from the GTIN. When these digits have leading zeros, they are removed. 

FIX: Manually printing label (RTC-29349)

When manually printing a label, the generated label is compared to the latest one, not the first one created.

FIX: CountryCode in profile/team (RTC-29383)

StagingBatchExecutor job is not aborted when a store is imported from Store Service with CountryCode = '' (empty string) in profile or team.

Printing future labels (RTC-25130)
In Label printing grid default filtering on Valid From column is 'before or equal' and labels are shown in ascending order. Current date (today) is visible in column header. User can filter on Valid From column and print future labels. After printing labels they're marked as printed in Printed column.

Import of country linked to stores (RTC-23087

• CountryCode is updated only when storeGroup has 'Profile' type 

• New column in Chain.Store table - AddressId

• Store address is saved in the dbo.address table. The correct address id is assigned to the store

• All stores have AddressId (possibility to assign address to it)

Export of external model number (RTC-29023)

ExternalModelNo is exported from Item Management to JSON file.

FIX: Print of amount on labels (RTC-28948)

When store price amount is in whole kroner, the .00 øre is printed.

Fix for Myhrvold scales (RTC-28851)

ConvertItemLabelToMyhrvold job doesn't fail when exporting labels on items that don't have unit price unit and unit price unit different than stk.

FIX: New item without supplierNo (RTC-28459)

• SupplierNo is a mandatory element of the imported new item. If it is not in the import, there is a validation error informing the user about it.

• ItemGroupNo is a mandatory element of the imported new item. If it is not in the import, there is a validation error informing the user about it.

Export to Myhrvold scales (RTC-27932)

• Unit and calculateUnitPriceInScale flag are exported in lowercase.

• Unit piece is exported as stk.

• The delete action is sent for items that have deleted item store links and for items that have been deactivated.

Multi country VAT code (RTC-22544)

• List for VAT codes for countries appears when there are multiple system countries in the country register

• Only system countries are exported (both Excel and blob)

• If there is no attached VAT for the country in the import of the item, the default is set. If VAT exists in the import, it is assigned to the item, (non-system countries are skipped, with an appropriate warning)

• The default VAT code for a country is assigned when creating a new item. If the default VAT code is not set in the registry, the field remains without VAT value

• VAT code is required only for the default country when editing item.

Print label from item details (RTC-28033)

• User can print labels for a specific item from the item details view.

• The button is visible only when the user has the label printing permission

• The store picker in the modal shows only the stores that the user has permission

• User can manually create label or add it to label printing

• Label can only be created for a store that has a price

• Store that has 'None' label type or no label type assigned in the register is unable to create a label (the choice of label type is blocked)

• The label type picker in the modal shows only the label types that are in label type register

• Labels created manually have a Manual label trigger reason

Fix: Import from Promotion module (RTC-28648)

There is no timeout in StagingBatchExecutor  when importing  and staging a lot of OfferItems from Promotion Module. The promotion package is updated to 1.6 and new type of offer mix type (100) is supported.

Export of item status to 3rd party (RTC-26850)

• Scale labels are exported with Item Status.

• Exported scales have their status exported as well (Active or Deleted).

• When scale link is deleted from item, their scale status is exported only once.

View and manage labels for store users (RTC-26783)

• For label printing there are permissions: 'Manage store local attributes' and 'View store local attributes'.

• In order to view label types on the item, user needs 'View store local attributes'. No matter the level of role with this permission, user will always see the label types on the 'all level'. For other levels, the visibility should be filtered by the access of that permissions.

• If the user does not have the manage store local attributes, the 'manage label types' button is hidden.

• In order to modify label types on item, user needs 'Manage store local attributes'.

• User needs the permission on 'all stores' to be able to add the attribute on 'all stores level'. Otherwise, he can only manage it on stores that he has access to. 

• When a user has 'Manage store  local attributes' on store 100 (and no 'View store local attributes') he should still be able to view the store local attributes on store 100. I.e. 'Manage' permission should implicitly give 'view' on all stores (that have the manage permission + labels on all store level).

• Without those permissions, user does not see label types on item at all.