Damien Maspero Microsoft SENIOR PROGRAM MANAGER

Need a way to avoid sending central warehouse records to channel db so more customers can be addressed especially if they use offline mode which would double the space needed for INVENTDIM and INVENTDIM_Tracking table.

Launch AX client.

Retail > Setup > Retail scheduler > Channel integration > Channel database

In the channel database form, select HOUSTON and click Full data sync > 1040 Products

in sql management studio, open channel db and look at INVENTDIM table.

Actual result :

In customer environment, INVENTDIM  and INVENTDIM_Tracking tables take around 5GB and the whole db consequently reach the SQL Express 10 GB limit.

most records are related to their central warehouse

Add printer defaulting to allow a user to choose their default network printer among the list of available printers.

Microsoft internal reference : Dynamics 3738235

AX 2009 : When running Update.exe to update application when an existing object in customization layer has the same name than a new object in syp layer, update fails with not much details.

Idea would be to log more details about the cause using existing KTD label : 

A table, Extended Data Type, Base Enum or class called %2 already exists. Import of %1 aborted

Attribute Accumulated Loyalty Points is not available to present on Receipt document.

Such attribute was available in version AX2012 R2 but in higher version it was removed.

It is important to present current Accumulated Loyalty Points for customer on Receipt document.

For screens where XDS is applied, when the user opens the same data in Excel XDS rules should be applied.

(current design reference : 855909)

*** Troubleshooting Steps
Steps to reproduce
1. Go to USRT / Retail / Channel setup/ POS setup/ POS/ Screen layouts
2. Use Layout designer for Screen layout. Verify that Export/ Import option exists
3. Open designer for Button grid. Verify that there is not option to Export/ Import button grid
  
*** Actual Result:
Open designer for Button grid. Verify that there is not option to Export/ Import button grid
 
*** Expected result:
There should be option Export/ Import in Button grid design

*** What is the business impact to the customer?
We spend a lot of time creating a screenlayout and buttongrids. The screenlayout we can export/import through a button on the screenlayout designer app; an export is created in xml.

1. Start client on AOS1
2. AOS1: Open InventTable form; filter ItemId 000049*; save the query with the name 000049* 
3. Start client on AOS2
4. AOS2: Open InventTable form, open filter Dialog, the Filter 000049* is visible and the user can select it
5. AOS2: Filter ItemId 00000004B and save the query with the name 00000004B
6. AOS1: Open the filter dialog and select new saved Query 00000004B ==> This is not possible. The saved Query 00000004B is not visible. The Client does not recognize the new record in SysLastValue-Table
7. Start new Client on AOS1 and do step 6 ==> saved query stil not visible

This is suggestion for Retail.

When cashier opens POS then there are presented in top right corner of POS ShiftId and TerminalId in which shift was opened.

In case if Shift was opened in one Terminal and then Suspended and another user Recalls this Shift in another Terminal then original TerminalId in which Shift was opened is presented.

There can be presented both Terminals in top of POS: current TerminalId and TerminalId in which Shift was opened.

Repro steps:

1. Login to terminal Houston-1, open new Shift eg. 12.

2. Suspend shift in Houston-1

3. Login to Terminal-2 and recall shift from Houston-1 terminal

4. Verify that in top right corner there is presented Shift12 and Terminal Houston-1 even if current terminal is Houston-2.

There should be presented Terminal for which Shift was opened and also current TerminsaId.

When cashier opens POS then there are presented in top right corner of POS ShiftId and TerminalId in which shift was opened.

Business date from table RetailTransactionTable is not presented in AX. This is important information as it decides on which day retail transaction will be posted.

Go to form Retail transactions and verify that this value is not presented and it cannot be added to this form.