Damien Maspero Microsoft SENIOR PROGRAM MANAGER

The item is sold in POS. Retail statement created at the end of day. But during the day, the item setup has been changed: Released product details/Default order settings/ Sales order is marked as 'Stopped'.
This parameter is used for non-retail sales orders which should not be checked on statement posting.
All these items in the retail sales are already sold in the store and the customer has paid for the goods. Not all standard sales error check applies to the retail sales order and that needs to be reviewed.

*** Troubleshooting Steps
1. Open USRT company.
2. Sales order Stopped on Item:
Product information management/Common/Released products/select item 0016/Tab Manage inventory/Order settings/Default order settings/tab Sales order:
- Stopped= Yes
3. Run Distribute changes to POS:
Retail/Periodic/Data distribution/Distribution schedule/select 9999 All jobs/Run now.
Retail/Inquiries/Commerce Data Exchange/Download sessions/Process status messages/OK.
Check if the Status is Applied.
4. Sell an item 0016 in EPOS:
Open EPOS, log in.
Add item 0016.
Pay Cash.
Transaction completed with no issues and this is ok so far.
5. Run P-job:
Back to AX, USRT company.
Retail/Periodic/Data Distribution/Distribution Schedule/select the P-0001 job/Run now.
6. Create a retail statement:
Retail/Journals/Open statements/New statement/enter Store number HOUSTON/OK/Calculate statement/Yes.
 
*** Actual Result:
Try to Calculate Statement. In effect error message appears:
‘Item 0016 is on hold for transactions in Sales order on site .’
 
*** Expected result:
There should not be any error on creating or posting statement as the item sold as cash&carry transactions (not Sales order created in POS).
‘Stopped’ parameter is designed only for sales orders. When Sales order created in POS and the system does not allow to use this item, then this is a correct behavior. But if cash&carry transaction posted, the system should allow to create/post statement.
There is separate Blocking parameters for Retail purpose: Blocked at register
 

We wanted to centrally control the personalization of forms. Users should not be allowed to make their own form personalization. Only the a user with the System Administrator role is allowed to personalize the forms. Afterwards, the System admin will push the form personalization to other user. This should be possible under System administration > Setup > Personalization. There you can control whether one or more users are allowed to personalize all or just specific forms. However, after personalizing the "PurchTable" form for example and exporting it so that the form personalization could be shared with other users. If we then import the form personalization to another user, the form is not personalized unless the "Personalization allowed" and the "Explicit personalization" checkboxes are both activated for the user. Activating the "Explicit personalization allowed" checkbox enables the user to make additional or further personalization on the form (PurchTable) and this is something we want to prevent. The form PurchTable should be personalized by only having the "Personalization allowed" checkbox activated for that user.

*** Troubleshooting Steps (please include screenshots / do you have a VMAS machine to share?)
With Repro Steps
Steps to reproduce
1. Open Visual Studio as Admin
2. Go to AOT/ Data Model/ Data Entities and find RetailTransactionDiscountLineEntity
3. Go to AOT/ Data Model/ Views and find RetailTransactionDiscountTransView
 
*** Actual Result:
Go to AOT/ Data Model/ Views and find RetailTransactionDiscountTransView
 
This view doesn’t contain information like SalesOrderId and InvoiceId but contains info like SaleOrderSalesStatus.
There is no Data entity based on this view.
 
*** Expected result:
This view should additionally contain information like SalesOrderId and InvoiceId.
There should be Data entity based on this view.

AXService to compress HTTP request response data (Microsoft internal reference DCR 180702).