Jaroslaw Piekarz Escalation engineer

There is wrong Payment Status = Not submitted for Cash and carry transaction in HQ after posting Statement.

*** Troubleshooting Steps (including screenshots)

1. Login to POS

2. Register cash&carry transaction.

3. Pay by credit card, register payment by Adyen connector

4. Run P job

5. Validate retail transactions

6. Create, Calculate and Post retail Statement

7. Verify that Payment status for new posted Sales order is ‘Not submitted’

*** Actual results:

Create, Calculate and Post retail Statement.

Verify that Payment status for new posted Sales order is ‘Not submitted’.

*** Expected results:

Payment status for new posted Sales order is ‘Paid’.

There are two scenarios when Batch number for Return transactions are not taken from sales transaction:

1. When return transaction is registered in POS without reference to sales transaction
2. When return transaction is registered in POS with reference to sales transaction but both transactions are posted in the same Statement

In both two scenarios when Batch number for return transaction is not taken from sales transaction there is required to setup Batch number group in Released product to enter new Batch number from sequence.

It is standard behavior but in effect it generates many new not necessary Batch numbers.

It would be better to use Default Batch number instead Batch number from sequence in such case like it is for cash&carry sales transaction.

Repro steps with 2 scenarios:

1. Register Return product operation in POS for Item with Batch number tracked (no reference to sales order),

• Upload by P job to HQ,
• Run Validation of retail transaction,
• Calculate and try to Post Statement

1. Register Sales transaction in POS for Item with Batch number tracked,

• Go to Show journal and select new created sales transaction,
• Register return transaction,
• Upload by P job to HQ,
• Run Validation of retail transaction,
• Calculate and try to Post Statement

In both cases there is presented error message in Statement:

While processing the state Customer order invoiced, generic exception encountered in retail statement xxx post aggregate controller while aggregating the transactions: 

Posting Posting Sales order: yyyy Item: zzz Batch number group is not specified on item and can therefore not automatically be created 

Posting Posting Sales order: yyyy Item: zzz Inventory dimension Batch number must be specified. 

Posting Posting Sales order: yyyy Item: zzz Update has been canceled. .

It would be better to assign Default Batch number id for return transaction instead of generating new ones from sequence number

The Store Commerce app may get multiple updates / fixes on a single day, but the LCS Shared asset library Store Commerce asset does not include or show release notes behind the Versions view of the said component.

Customer expects that when they are choosing the new Store Commerce App version on LCS, they will have information what has been changed in Store Commerce App 10.0.28 Version 23 and 10.0.28 Version 36 as an example.

Here is what is expected in more details:

• Go to LCS Shared Asset Library (1)
• Shared asset library -- Microsoft Dynamics Lifecycle Services
• Select asset type node Retail Self-service package (2)
• Scroll down to 10.0.28 – Store Commerce line on the list
• Mark the checkbox on this line (3)
• Click on “Versions” on the top of the list (4)
• LCS opens a side dialog containing all of the downloadable links for Store Commerce 10.0.28 app (5)
• For example the customer is using Store Commerce App 10.0.28 version 23 at the moment (released on Aug 31, 2022) (6) and they need to know what has been changed between app versions 23 and 36 (release on September 20, 2022)
• The Release notes column (9) is empty ; that could contain the aggregated release notes containing all of the changes in app 10.0.28
• The general article of the 10.0.28 does not contain detailed information of the Store Commerce App versions (here 10.0.28/23 & 10.0.28/36)
• The customer can download the desired version using the version download link (8), but it’s just the installer, and contains no documentation regarding the contents of the changes in this downloaded version

It can’t be just “download and install the newest version of the app” if customer doesn’t know what the actual difference is between these 2 app versions. 

We, as Microsoft publish new Store Commerce App versions at a fast pace that customer can’t keep up with the new versions if they don’t know what really has been changed in the newer versions.

When Store should be closed/ deactivated it would be great to add in future possibility to disable Store directly in Store setup.

When we stop using one Store and we would like to somehow deactivate this Store by stopping:

• The CDX jobs should be stopped for this Store,
• Products syncing should be stopped for this Store,
• Registers of the store should be inactive etc.