Report details

File name

0851_PaymentTypesPerShift.rdl

File name sub-reports:

1700_subSettlement.rdl, 1706_subStatistics.rdl

Data source

Analysis services (Cube)

Selections

Comment

Date from

Shows all shifts with stated date between Date from and Date to - Default today.

Date to

Shows all shifts with started date between Date from and Date to - Default today.

Retail store

Choose store.

Workstation

Default all.

Shift

Default all in chosen date range.

Columns - Report shows 2 sub reports.

Settlement: (1700_subSettlement.rdl). 1 row per payment type:

Received

Sum of received payments for payment type.

Balance

Sum of counted amount for payment type. This is only shown for Cash, Finance, Check and Total all coupons and Giftcards.

Difference

Difference between received amount and counted amount for payment types that have counted amount.

Quantity

Number of payments.

Statistics (1706_subStatistics.rdl):

Description

1 row per Cancelled receipts, Receipts with return, Returned items, Deposit refund received 12%, Deposit refund received 25%, Deleted items, Price change and Nullsale

Amount

Sum amount, only for Returned items, Deposit refund received 12%, Deposit refund received 25%, Deleted items.

Quantity

Quantity

Share

Share of the sale. Only for Returned items, Deposit refund received 12%, Deposit refund received 25%, Deleted items.

Customer

Import customer in ARTS XML format (RTC-13193)

When customer data is importing from ARTS Customer format, customer type is updated (employee etc.)

Gift card

Synchronizing gift cards to cloud (RTC-13372)

Gift cards are exported to the cloud also when there are committed transactions with amount =0.

Fix for regive of gift cards (RTC-12236)

When regive operation is done, ownerClaimType is set if it previously was empty.

Requirement:

Giftcards Integration package 1.4.0.

Invoicing

Fix for resend of EHF (RTC-12240)

When opening Resend EHF, list of not sent EHFs are displayed properly, without timeout. User can customize results by using filter in column sent.

Receipt journal

View workstation startup transaction (RTC-12756)

User can see workstation's starts in Receipt journal. They are located in Receipt type filter in System transactions -> Other.

Stocktaking

Check if update of stocktaking is completed (RTC-13035)

It is possible to enable/disable checking check if update of stocktaking is completed during creation of new stocktaking.

System Parameter: CheckForCompletedPosLogsInChainEnabled True/False that decide if we are checking the last POSLog in Chain Classic or not. The main functionality was implemented in RTC-776.

The Inventory transactions (POSLogs) that are cancelled (when the processing of all items will fail), will be excluded from check for the last processed transactions in Chain Classic during stocktaking creation. New column SourcePosLogCancelled was added in the StockAdjustmentBatch with the information if the POSLog was cancelled during the adjustment.

If all lines failed, then the receipt is cancelled, if there is at least one not failed line, then POSLog is not cancelled and the StockAdjustmentBatch will be marked with the default value False in SourcePosLogCancelled column.

File name

0850_ShiftSatistics.rdl

Data source

Analysis services (Cube)

Useful hidden parameter

pDeletedStatuses

Which deleted statuses to include for column "Deleted Amount" and "Deleted quantity".

Selections

Comment

Date from

Shows all shifts with stated date between Date from and Date to - Default today

Date to

Shows all shifts with stated date between Date from and Date to - Default today

Retail store

Default all.

Columns - one row per shift.

ShiftID

Shift ID

Start

Start time for shift.

Stop

Stop time for shift.

Cashier

Cashier name.

Customers

Number of customers for shift.

Nullsale

Number of nullsale and drawer openings for shift.

Deleted amount

Amount of deleted items.

Deleted quantity

Number of deleted items.

Avg amount

Average transaction value (sold amount / customers).

File name

0904_CashierStatistics

Data source

Lindbak POS Reporting cube (Olap).

Parameters

pCustomerGroupPersonell

Which customer group personell belongs to. Default value = 100.

pDiscountReasonCodeType

Which reasoncodetype to include in Manual discount - Default LineDiscount.

pManualDiscount

Which discount type to include in Manual discount - Default Line.

Filters

Comment

Date from

Default today.

Date to

Default today.

Retail store

Default all.

Operator

Default all.

Columns - one row per operator.

Cashier

No

Cashier number

Name

Cashier name

Returns

Qty

Quantity of returned articles.

Amount 

Amount of returned articles.

Deleted receipts

Qty

Quantity of deleted receipts.

Amount

Amount of deleted receipts.

Deleted item lines

Qty

Quantity of deleted item lines

Amount

Amount of deleted item lines

Manual discount (discounts filtered by parameter pManualDiscount and pDiscountReasonCodeType )

Qty

Quantity of manual discounts 

Amount

Amount of manual discounts

Diff settlement (difference between tender cash and balance cash)

Amount

Difference in amount.

Deleted web orders (orders with order type "WebShop Order" and order status "Deleted")

Qty

Quantity of deleted web orders.

Amount

Amount of deleted web orders.

New customer orders (orders with order type "Store Order" and status "Created")

Qty

Quantity of new customer orders

Amount

Amount of new customer orders

Offline coupons (tender coupons with coupon type = "O"

Qty

Quantity of offline coupons.

Amount

Amount of offline coupons.

Personell discount (discount with customers from customer group in parameter pCustomerGroupPersonell)

Qty

Number of receipts containing personell discount.

Balance

Historical exchange rate in Balance (RTC-12275)

If parameter UseCalculatedExchangeRateInBalance is set to True in POS Configuration for POS WCF, the correct historical exchange rate is used when registering Balance in Chain Web.

Customer

Import of customers without SSN (RTC-12873)

When creating or updating customer by using import of customers in ARTS XML format. Social Security Number is not set on customer in Lindbak Retail database if it is not present in import file.

Customer order

Deleting an order line in payment mode in POS should not delete order line in Chain Web (RTC-12235)

Lines deleted in payment mode in POS are properly processed in Chain Web and are not deleted from the order.

Dispatch orders

Dispatch Orders - Performance improvement (RTC-11645)

Loading of rows in Dispatch Orders grid has been optimized. The loading time is not significantly visible for the user when opening the Dispatch Orders grid or when scrolling through the Dispatch Orders list.

Dispatch rules

Item

Performance improvement in Item grid (RTC-10402)

When opening Items grid, list of items is displayed. User can narrow and customize results by using filters in columns or write key word in simple search window to find a specific item.

POS Configuration

Reports

Sales per department (RTC-12048)

To make PDF print look better we have made minor adjustment to column widths.

The formatting of some columns are improved to only show two decimals.

• Changed report 0453_SalesByProductAreaOrGroup.

Account Receivable

Validation of payment date (RTC-10893)

When adding payment to invoice, payment date cannot be earlier than invoice creation date.

ChainToCloudIntegration

Add support for new file types (RTM-236)

Added support in ChainToCloudJob to support new file types which are sent to cloud. New supported file types: budsjett (budget), vareliste (item list), stock.

Required:

ChainToCloudIntegration package version 1.6.

Customer

Importing item list to customer group (RTC-9646)

When an item does not have a price in selected store during import of item list to customer group, an error message is displayed to inform the user of what the problem is.

Import of customers with SSN (RTC-11762)

When creating or updating customer by using import of customers in ARTS XML format, Social Security Number is updated properly on customer in Lindbak Retail database.

Default invoice by email to customers with email address (RTC-9742)

When customers (private and credit) are created with email address in POS, the customer will default be updated with the flag checked for 'Invoice by email'.

Inactive customer groups are default hidden (RTC-10439)

When opening Customer Groups, inactive groups are default hidden. In order to see hidden groups, user needs to change filters in Inactive column. User can also narrow and customize search results by using filters in columns.

Customer order

Bugfix: Calculation of gross profit (RTC-11944)

When adding new items to customer order and changing the unit price and net cost, gross profit is calculated according to the new values.

Offer expiration date (RTC-9887)

When creating new offer, "Valid to" field is set by default to the expiration date (14 days from today's date). User can change it by date picker. It is also possible to change the default value under the "DefaultOfferExpirationDays" parameter in Chain Web system parameters. When viewing already created offer, "Date" and "Valid to"  fields are set according to the offer's creation date and expiration date.

Disable the order locking functionality by default (RTC-11511)

The Customer Order locking feature is disabled by default, the user need to change the value of Chain Web system parameter "CustomerOrderLockingEnabled" to True, to enable it.

Parameter description: 

If set to True Customer Orders will be blocked from being handled in POS and Chain Web at the same time.

Customers blocked for credit (RTC-11586)

When opening a Customer Order with status Draft, Changed or Active, or when creating a new order directly from customer view, a message is shown to user when the customer is blocked for credit.

Preventing simultaneously changes to a customer order (RTC-908)

When a customer order is being changed from POS, it will be locked for simultaneously changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later.

Additional technical information:

Order locking feature will work with versions EG POS 3.0.0.12401 or newer.
For more information about changes in POS, please read release notes related to "Don't allow editing the same order in POS and Chain Web".

Homepage dashboard

Refresh data automatically when changing store (RTL-133)

Data in Homepage dashboard is refreshed automatically when the store is changed to another one.
Additionally, when 'View for all stores' is checked, the data in Homepage dashboard is refreshed automatically.

Wrong Mapping For Sales Per Hour (RTC-3144)

The mapping for sales per hour was corrected and presents correct values for customers per hour and sales per hour. Both comparison and main date are correctly loaded and return correct results. Furthermore, setting the comparison date greater than the main date and main date lower than the comparison date is impossible, and dates are automatically changed into the greatest or the lowest one possible. When setting the comparison date greater than the main date, it is automatically changed into the greatest one possible equal to the main date. The same happens when setting the main date lower than the comparison date.

Invoicing

Summation per receipt (RTC-9721)

When the invoice contains multiple receipts, there is an additional line with summation per receipt of total excluding VAT and total including VAT.

Item

Performance improvement in Item grid (RTC-10402)

When opening Items grid, list of items is displayed. User can narrow and customize results by using filters in columns or write key word in simple search window to find a specific item.

Order dispatch

Partially delivered dispatch orders (RTC-10302)

When dispatch order is partially delivered, after removing the item line from the not-delivered order, the freight item is reassigned to the delivered line with correct quantity delivered amount (should be 1). This previously did not work as intended and has now been corrected.

Update picking order with shipment number when delivered from AutoStore (RTC-7709)

The picking order's ShipmentNumber is updated by Chain Web based on ShipmentTrackingNumber from POSLog provided by AutoStore. This gives the ability for the tracking link to be included in the email sent to the customer.

Order management

Rejected order lines (RTC-10838)

In order to display number of rejected order lines, Reporting imports this status from Retail database.

This is done by existing package FactOrderRetail.

This package require Retail database version 2.10.0.7 or higher because of new procedures.

Note: There are some limitations to this functionality: To get rejected status we need to fetch changes in Retail db and changes in POSLog. In some cases this can result in incorrect status for Order lines.

• Case1: We update changes in Retail database in one Rt-job, but not changes from POSLog. Status for order line will be ONLY Rejected. Before we update POSLog we will not have assign status for new store.

• Case2: We update changes in POSLog in one Rt-job, but not changes from Retail db. In this case Rejected lines will have status "Reassigned" before we update correct status from Retail db.

• Case3: We create order, reject it in Chain Web. If we update changes from Retail db before all POSLogs, we will only have reassigned status in Reporting.

Reports

Swedish translations (RTC-12047)

Swedish translation corrected for "Subvendor" in reports 0013, 0110, 0452.

Stocktaking

View and filter stocktaking's (RTC-12540)

User can edit and view all types of stocktaking's. Additionally, when viewing selected stocktaking, it's possible to filter results in Out Of Scope column.

Dispatch rules

Fix translations for Order Dispatch (RTC-12098)

Translations in Dispatch Rules has been improved and English and Norwegian version is working as expected.

Reports

Swedish translations (RTC-12047)

Swedish translation corrected for "Subvendor" in reports 0013, 0110, 0452.

Sales per department (RTC-12048)

To make PDF print look better we have made minor adjustment to column widths.

We have also improved formatting of some columns to only show two decimals.

Changed report 0453_SalesByProductAreaOrGroup.

Stocktaking

View and filter stocktaking's (RTC-12540)

User can edit and view all types of stocktaking's. Also, when viewing selected stocktaking, it's possible to filter results in Out Of Scope column.

Customer order

Customers blocked for credit (RTC-11586)

When opening a Customer Order with status Draft, Changed or Active, or when creating a new order directly from customer view, a message is shown to user when the customer is blocked for credit.

Order dispatch

Partially delivered dispatch orders (RTC-10302)

When dispatch order is partially delivered, after removing the item line from the not-delivered order, the freight item is reassigned to the delivered line with correct quantity delivered amount (should be 1). This previously did not work as intended and has now been corrected.

Customer order

Disable the order locking functionality by default (RTC-11511)

The Customer Order locking feature is disabled by default, the user need to change the value of Chain Web system parameter "CustomerOrderLockingEnabled" to True, to enable it.

Parameter description: 

If set to True Customer Orders will be blocked from being handled in POS and Chain Web at the same time.

Preventing simultaneously changes to a customer order (RTC-908)

When a customer order is being changed from POS, it will be locked for simultaneously changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later.

Additional technical information:

Order locking feature will work with versions EG POS 3.0.0.12401 or newer.
For more information about changes in POS, please read release notes related to "Don't allow editing the same order in POS and Chain Web".

Order management

Rejected order lines (RTC-10838)

In order to display number of rejected order lines, Reporting imports this status from Retail database.

This is done by existing package FactOrderRetail.

This package require Retail database version 2.10.0.7 because of new procedures.

Note: There are some limitations to this functionality: To get rejected status we need to fetch changes in Retail db and changes in POSLog. In some cases this can result in incorrect status for Order lines.

• Case1: We update changes in Retail database in one Rt-job, but not changes from POSLog. Status for order line will be ONLY Rejected. Before we update POSLog we will not have assign status for new store.

• Case2: We update changes in POSLog in one Rt-job, but not changes from Retail db. In this case Rejected lines will have status "Reassigned" before we update correct status from Retail db.

• Case3: We create order, reject it in Chain Web. If we update changes from Retail db before all POSLogs, we will only have reassigned status in Reporting.

System

Upload RIGAL files to Cloud (RTC-849)

DirectoryListnerJob job in FileListener Integration package can upload any files to FileService based on a list of predefined content type or a list of Regex'es. 

The job can be configured to upload Chain/POS files (butikk, vpi, pris and so on), RIGAL files (V, K, M, Varetran and so on) or custom files types based on Regex. 

Detailed documentation on how the job works and how to set it up can be found in the documentation tab in Integration Platform Management App.

Report details for Item transaction list

File name

0452_BreakageAndWasteTransactions

Data source

Analysis services (Cube)

Relevant parameters

pTransactiontypesToExclude

List of transaction types not to be included in Report. Default following transaciton types are excluded: ArticleService, StockAdjustment, Shrinkage, Inventory, InternalUse, InternalTransfer and DockingArea

Selections/filters

Comment

Date from

Default today.

Date to

Default today.

Retail store

Default all. If store user, store.

Subvendor

Default all.

Article area

Default all.

Article group

Default all.

Transaction type

Default all (does not show types excluded in pTransactiontypesToExclude).

Reason code

Default all.

Columns - one row per transaction. Grouping per store / supplier / EAN.

Item name

Item name.

Item number

Item number.

Number

Operator number.

Transaction type

Transaction type.

Reason code

Reason code used for transaction.

Date

Date for transaction.

Net amount

Net amount for transaction.

Quantity

Quantity for transaction.

Amount

Amount for transaction.

Report details for Sales by product area / Sales by product group

File name

0453_SalesByProductAreaOrGroup

Data source

Analysis services (Cube)

Selections/filters

Comment

Report type

If report should be based on article area or article group - Default area.

Date from

Default today.

Date to

Default today.

Comparable date from

Default same day in same week last year.

Date to comparable

Default same day in same week last year.

Article area

Default all (does not show if report type is Group).

Article group

Default all (does not show if report type is Area).

Retail store

Default all.

Columns - one row per article area / article group

Item area

Item area number and name

Date 1, based on sales between Date from and Date to

Sales

Sales Incl. VAT

Sales including VAT for Date 1.

Sales ex. VAT

Sales excluding VAT for Date 1.

Records

Quantity

Number of sold items for Date 1.

Price pr. Art

Average price per article for Date 1.

Gross profit

Amount

Gross profit amount for Date 1.

%

Gross profit percentage for Date 1

Date 2, Based on sales between Comparable date from and Date to comparable.

Compare incl. VAT

Sales incl. VAT

Sales including VAT for Date 2.

Diff.

Difference in sales amount (including VAT) for Date 1 and Date 2.

Diff %

Difference in sales between Date 1 and Date 2 in percentage.

Customer

Remove reference text demand from local EHF (RTC-9743)

When the customer is marked to "Save electronic invoice locally" , the checkbox "Reference number required" is editable. When "Reference number required" is set to False, reference number and reference text are not required when creating credit sales and customer orders. This feature makes the sales process more efficient when invoicing is done in a 3rd party system.

Customer order

Customer with credit blocked (RTC-9880)

When creating customer order and adding customer with credit blocked, a warning message is displayed. Order can be saved but it is not possible to pay it by credit. For such customers credit sales cannot be created.

Autosave for customer orders that are not submitted (RTC-3503)

The integration job OrderSubmitter, included in the BackOfficeIntegrationSubscriber package, is responsible for submitting orders with statuses Draft and Changed which have not been submitted within a defined number of minutes. By default the job is executed every hour.

Invoicing

Invoice text "Foretaksregisteret" (RTC-10601)

Field name on top of the invoice was changed in English and Norwegian version to "Foretaksregisteret" to align with legal requirements. Text in Swedish is previously defined according to Swedish legal requirements.

Reports

Translations in Report (RTC-10828)

The Swedish translations of the price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following Swedish translations:

• Chain Web

• Manuell kassa

• InStore App

• Självscanning (SU)

• Mobilsjälvscanning

• Självbetjäning (SCO)

Additionally, parameter pWorkstationType two values has new translations (“ITAB” is now changed to “ISA” and “SU” is now changed to “SCO”).
Furthermore, pWorkstationType has two new items in the list (Web shop and Other).

Translations (RTC-10894)

The Swedish and Norwegian translation of the workstation type name "Other" in the dropdown list of parameter pWorkstationType (used in reports 0705/0706 and others) is updated with the following values:

• Swedish: Övriga

• Norwegian: Andre

• Additionally, the text "Web shop" is changed to “Webshop”, according to requirements.

Translations (https://jira.eg.dk/browse/RTC-10988)

The Swedish translations of two price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following:

• ShopAndGoCheckOut - Självbetjäning (SCO)

• ShopAndGoCheckTerminal - Självscanning (SU)

Stocktaking

Count group status (RTC-10659)

When logging into Chain Web as a store user and navigating to the Count groups, only count groups available in the grid will be count groups that should be counted in the given store. The column "#items in stock" will display the number of items in the count group that the given store is expected to count.

Improved transparency in count group grid (RTC-10793)

When the counting of a count group has not yet started (including when counting was cancelled), the following fields will be blank: counted at, counted by and modified by. This was previously not the case and was confusing for the user. A modified date will be added for the count group with status "Not started", when the counting was cancelled, in order to show the user when it was cancelled.

Show items added outside the count group (RTC-948)

Added column “Out of scope” to the Count list view to show items that is added outside of Count group in InStore App.

Reports

Translations (RTC-10894)

The Swedish and Norwegian translation of the workstation type name "Other" in the dropdown list of parameter pWorkstationType (used in reports 0705/0706 and others) is updated with the following values:

• Swedish: Övriga

• Norwegian: Andre

• Additionally, the text "Web shop" is changed to “Webshop”

Translations (https://jira.eg.dk/browse/RTC-10988)

The Swedish translations of two price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following:

• ShopAndGoCheckOut - Självbetjäning (SCO)

• ShopAndGoCheckTerminal - Självscanning (SU)

Reports

Translations in Report (RTC-10828)

The Swedish translations of the price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following Swedish translations:

• Chain Web

• Manuell kassa

• InStore App

• Självscanning (SU)

• Mobilsjälvscanning

• Självbetjäning (SCO)

Additionally, parameter pWorkstationType two values has new translations (“ITAB” is now changed to “ISA” and “SU” is now changed to “SCO”).
Furthermore, pWorkstationType has two new items in the list (Web shop and Other).

Stocktaking

Count group status tab (RTC-10659)

When logging into Chain Web as a store user and navigating to the Count groups, only count groups available in the grid will be count groups that should be counted in the given store. The column "#items in stock" will display the number of items in the count group that the given store is expected to count.

Cashiers

Default price channel should be "None" (RTC-10067)

When creating new user, default price channel is not set by default.

N

Accounts receivable

Roundings in EHF files (RTC-9092)

The PayableAmountRounding field is saved in EHF files only when there is a rounding amount (different than 0).

Rounding of credit sale (RTC-7089)

In some instances, the rounding of items was wrongly calculated when creating a credit sale, causing a subtotal rounding of 0,01. This issue has been resolved.

Balance

Registered balances can be edited (RTP-4041)

It is possible to edit balances after registration when system parameter "NewBalanceRegistrationEnabled" is True.

Cashiers

Export e-mail for cashier to POS (RTP-4001)

Cashier e-mail will be exported to POS when updating cashier info in Chain Web and when mass exporting cashiers from Chain Web.

Customer order

Preventing simultaneous changes to a customer order (RTC-832)

When a customer order is being changed from POS, it will be locked for simultaneous changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later.

Slow processing of customer orders (RTC-9676)

Performance when updating customers is much faster after improving code related to handling of communication channels.

Order dispatch

Not possible to delete "last not delivered" item (RTC-7099)

Corrected an issue related to removing last line from "in picking".

Error handling of CompletePickingCriticalExceptions (RTC-10050)

An issue with storing the DeliveryReceiptID caused internal transfers to not be performed correctly for some dispatch orders. This is corrected and values like DeliveryReceiptId and ShipmentNumber are stored correctly in the database.

POS Configuration

Stocktaking

Store number and store name in count group view (RTC-791)

Stocktaking results can be filtered on counted/not counted counting groups per store per day.

Splitting count groups which exceed 50 items (RTC-902)

Import of count groups with more than 50 items per department will be split into several count groups so that more store staff can be involved in the stocktaking of a department.

This is configured in the integration job CountingGroupImportProcessor in the parameter splitCountgroupsEnabled (default value False - splitting is disabled) and maxItems (default value 50).

System

Default region/language for cashiers (RTC-800)

When creating a new cashier the region and language is based on the user who are creating the cashier.

POS Configuration

Configuration group - can't find store (RTP-3652)

Stores are properly returned and can be added in the store group configuration section

Balance

Registered balances can be edited (RTP-4041)

It is possible to edit balances after registration when system parameter "NewBalanceRegistrationEnabled" is True.

Stocktaking

Edit counted amount for weight items (RTC-713)

When editing the counted amount of item in stocktaking results view, weight items can be saved with decimals.

Performance and retry mechanism for export of large stocktakings (RTC-733)

Performance when exporting stocktaking results to 3rd party (inventory control) is improved for large stocktakings (>300K items). If something fails, a retry mechanism will wait a configured number of seconds before the next retry execution for this stocktaking.

Inventory per item area

File name

0451_StockTakingItemAreaLevel.rdl

Data source

 Lindbak Retail (database)

Selections

Comment

Date from

Default today.

Date to

Default today.

Retail store

Which store to run report for.

Stocktaking

Shows all stocktaking's for selected store within date from - to range.

Report shows inventory date and store number and name.

Columns, one row per item area.

Item area

Area number

Area name

Area name

Inventory value, Cost price

Sum cost price

Inventory value, Ex. VAT

Sum salesprice ex. VAT.

Inventory value, Sales amount inc. VAT

Sum salesprice inc. VAT.

Customer

 Line note in Customer Sales grid (TFS: 185458)

When expanding the details on an item row, there is a column for Line Note. When searching for an item in the filter "Item name", the first 16 rows containing this item is automatically expanded. More rows can be expanded manually. This will enhance the user experience when looking through historical sales for a customer.

Invoices

Show the amount that is rounded in the invoice (TFS: 184868)

Sum of rounding is visible on the invoice to make the rounding more transparant.

Reason codes

Reason codes for overridden price (TFS: 189485)

The support for new reason code type "Change price" has been added. These reason codes can be created and maintained in Chain Web. 

Requirements: BackOfficeBatchGenerator 1.2.13, ChainIntegration 1.5.1

Report

Able to use hyphen when renaming reports (TFS: 189086)

It is possible to use hyphen when renaming reports.

Stocktaking

Random count - refresh stock status in count lists (TFS: 184420)

The stock level in a new count list can be refreshed when a count list is added to a stocktaking or activated. To refresh the stock level, the checkbox "Get stock level again for items in selected count lists" must be checked. The stocktaking status will then be "Creating" while the stock levels are being updated for the count list. If the stock level is not refreshed, the stock level for when the count list was submitted, is kept.

New configuration parameters:

• SynchronousUpdateCountListMaximumSize - counted based on sum of all lines (unique SkuNumber) from all used count lists

- default value: 1000

ReuseStockLevelExpiryTimeInMinutes - it is relevant, only for a small count lists (if sum of count lists lines < SynchronousUpdateCountListMaximumSize)

- default value: 60

Don't allow creating new stocktaking if last stocktaking is not updated in Chain Classic (TFS: 189347)

The user will not be able to create a new stocktaking in Chain Web (also with the refreshed stock level for the assigned countlists) inside the same store, until the last POSLog related to previous stocktaking (previous stock results) will be processed/ updated in Chain Classic.

Related Chain Classic PBI with the requirements: Product Backlog Item 190077: 2.1.1: Sport1: Stocktaking: New proxy for checking that last stocktaking is finished

Accounts receivable

Roundings in EHF files (RTC-9092)

The PayableAmountRounding field is saved in EHF files only when there is a rounding amount (different than 0).

Rounding of credit sale (RTC-7089)

In some instances, the rounding of items was wrongly calculated when creating a credit sale, causing a subtotal rounding of 0,01. This issue has been resolved.

Stocktaking

Don't allow creating new stocktaking if last stocktaking is not updated in Chain Classic (TFS: 189347)

Now the user will not be able to create a new stocktaking in Chain Web (also with the refreshed stock level for the assigned countlists) inside the same store, until the last POSLog related to previous stocktaking (previous stock results) will be processed/ updated in Chain Classic.

Related Chain Classic PBI with the requirements: Product Backlog Item 190077: 2.1.1: Sport1: Stocktaking: New proxy for checking that last stocktaking is finished

Customer order

Search for active orders shows both active and cancelled orders (TFS: 186790)

The flag IsCancelled has been added to the response of the GetCustomerOrders3 method in CustomerOrder service. It shows if an order is cancelled or not.

Requirements:

POS Services 7.76.03703

Credit sale

Block "correction of credit sale" when original receipt was partly paid by another tender type (TFS: 169266)

When credit sale contains other tender type than Credit, correction is not allowed.

Dependencies to another products:

  POS WCF in version 3.0.0.12003 or 4.0.0.12002 or higher required.

Invoice

EHFs rejected due to missing ref. number / ref. text (TFS: 188224)

If a customer is changed to receive EHF invoices, after credit sale have been created, the reference number and text is set to 'None' when invoicing is done, so that the EHF won't fail due to missing input in these fields.

Price guarantee

File name

0115_PriceGuaranteeReconciliation.rdl

Data source

 Database “Lindbak POS Reporting DW”

Selections

Comment

Date from

Selection for sold date - default today

Date to

Selection for sold date - default today

Parameters:

pMainTeamTypeKey

Teamtypekey for business units- default 1.

Columns for transactions

Team sold

Team number where item is sold

Teamname 

Team name where item is sold

Store sold

Store number where item is sold

Storename

Store name where item is sold

Receipt

Receipt number where item is sold

Sold date

Date when item is sold

Team returned

Team number where item is returned

Teamname

Team name where item is returned

Store returned

Store number where item is returned

Storename

Store name where item is returned

Discount

Difference between returned price and sold price for same item.

Date returned

Date when item is returned

Columns for Settlement

Payer

Team who owes money

Receiver

Team who receive money

Amount

Amount

Cashier

Fields in Cashiers view should not be case sensitive (TFS: 166535)

Search fields in Cashiers view are no longer case sensitive.

Credit sales

View credit sales created by another user or from POS (TFS: 184581)

To be able to edit credit sales created by another user or from POS, the user must have the access: "Edit credit sales". 

Customer

Invoice fee created for member with 0 credit (TFS: 183083)

An Invoice fee receipt is created, regardless of the customer's credit limit. This can cause the credit limit to be exceeded by the invoice fee.

Gift cards view

All column for owner email (TFS: 185904)

A new column for 'Email' has been added to the Gift cards' grid. 

Homepage

Minor improvements (TFS: 181606)

Swedish translations have been added for Default Settings component and the Change Settings component. Furthermore, margin settings have margin intervals on the same row with proper headers and more customer friendly translations.  

The Popup for comparison date has different margin colors compatible with settings to enable users to track stores or department performance in a better way.

Department KIP in Homepage dashboard (TFS: 186140)

'Sales per Department' component displays a list of 1 to 8 department (according to user's settings) with their percentage performing values and appropriate margin colors (according to user's settings). Furthermore, the 'Sales per Department' component was expanded to view more details when comparing percentage values from the same date last year or day set by user itself. After clicking on a specific department more details displayed to the right in a a pop up window.
In addition to that, 'Sales per Hour' and 'Customers per Hour' components displays the correct amount of Sales and Customers per concrete hour and day . They are compatible with loaded data and present visual results with appropriate/matching colors. It is also possible to click at this components and see a pop up with details in comparison with the same date last year or date set by user itself (same as in 'Sales per Department' component). 

Inventory Control

Max 1000 items in counting Group (TFS: 176822)

The maximum amount of items in count groups has been limited to 1000. It applies to both count group imported via Inventory Control integration and count groups created in Chain Web. 

Invoices

Electronic invoice should not contain an empty "Description" field (TFS: 179958)

When the line note on the line in the order or credit sale only contains white spaces, then the description field will not be created for this line in the Electronic invoice xml file. This change is made to avoid sending an empty description field, which causes an error when validating the EHF invoice.

Changes to the PDF Invoice and user interface (TFS: 185463)

For Swedish stores, the invoice shows information about:

• Approved for F-tax

• Registered office

• IBAN/BIC is always printed on the invoice

• Organization number, in addition to the VAT number 

Sum total VAT amount on Invoice (TFS: 186891)

The Invoice has a new field for the total VAT amount.

Reporting

New colors in reports (TFS: 175400)

Changed color scheme for graphs in all reports to match the new EG design.

Discount quantity (TFS: 191692

In sub report 1406_subDiscounts. Number of discounts are changed from number of articles to number of receipts.

Reporting on cancelled receipts (TFS: 187201)

We have updated the way we report on cancelled receipts in some reports. Cancelled receipts now include receipts cancelled with status "DeletedFromUnfinishedReceipt".

Following reports are changed:

0018_CashierStatistics_std
0059_CashierStatistics
0062_DashboardCashRegister_1
0066_DashboardCashRegister_PerTeam
0071_SecurityStatistics
0111_CashierSecurityStatistics
0160_CashRegisterReport
0301_CashierStatistics
0517_DashboardCashregister_std
3002_DashboardCashRegister_PerTeam
1011_subStatistics
1706_subStatistics

Stocktaking

Permanent solution for saving model items (TFS: 182799)

The process of resolving model number has been solved permanently. Previously, some customers had issues with saving model items in retail database during synchronization of items. Additionally, improved logging in case of failed events has been added, so problems in the future will be easier to identify.

Virtual scroll in Archive view (TFS: 183194)

When working in the stocktaking archive view the bottom scroll is improved. Previously, there was a visual error causing the scroll bar to not stay in the bottom of the screen.

Completed date in stocktaking view (TFS 185122)

The "Completed date" column has been added to the stocktaking grid in Overview tab and also to the grid in Stocktaking tab. Users no longer have to open each stocktaking to see the completed date. This change is implemented to make it easier to work with stocktaking.

Item sync: Support comma and backslash in the 'error' file name (TFS: 185487)

Comma as a first sign is supported in the decimal fields. The date format included in "error message" file name will always have the same format "yyyy-MM-dd" - e.g. Failed single from batch ItemChanged 2020-09-29.txt. This is changed to avoid item synchronization to fail due to poor data quality.

Increase stability in count list import (TFS: 185489)

When the count list contains an item which doesn't exist in Chain Web and was attempted added more than once - it will not stop the import of the whole count list. Information about the one failed item will be logged.

Support deleting one EAN when item processing type = full (TFS: 185490)

 It is possible to delete just one EAN from a count lists, regardless of the parameter value for ModelItemsProcessingType.

Store

Support hyphen in account number for Swedish customers (TFS: 186256)

Hyphen in bank account number is supported. The account number can look like this: 123-4567.

System

Team view in Chain Web (TFS: 178777)

All stores that are part of a team are displayed in Chain Web Team menu.

User

First/Last Name is not mandatory for Azure users (TFS: 172957)

It is possible to create Azure User in Chain Web without First/Last Name, which is still mandatory for standard user.