Dynamics 365 Commerce

f anyone from the engineering team is here. All of us will be grateful to you if you can add some more columns (Account Num, Sales Order Number, Transaction Time) to the online store transaction view. The form doesn't support saved views. The current columns (store name and date) are of no help.

https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=1966625555120128

When a purchase order is created from the POS and a note is added to the header or lines, it is reflected as an attachment on the purchase order in HQ (F&O), making it difficult to review the notes for each line.

It is suggested that these notes be added to a field at the header level as well as a field at the line level to quickly view them, avoiding having to review the attachments for both the header and each line. This helps optimize time.

Description: Site Builder in Dynamics 365 Commerce currently lacks a built-in capability to delete multiple Publish Groups simultaneously. This limitation can lead to inefficiencies in environments where frequent content updates and group reorganizations are required.

Proposed Enhancement: Introduce a bulk management feature within Site Builder that enables users to:

• Select multiple Publish Groups using a multi-select interface.
• Filter groups by creation date, last modified date, or usage status.
• Execute bulk deletion with confirmation prompts to prevent accidental removal.
• Optionally include audit logging for deleted groups to support traceability and governance.

Expected Benefits:

• Reduces time spent on manual deletion of outdated or unused Publish Groups.
• Improves operational efficiency and content management workflows.
• Minimizes human error by replacing repetitive manual actions with structured bulk operations.

I would like to suggest adding a configuration option that allows the POS to automatically log off even when there is an active or open transaction.

Business Need:

In our business operations, there are scenarios where it's necessary to enforce an automatic log-off from the POS, regardless of whether a transaction is currently open. Currently, the system only supports automatic log-off when there are no open transactions, which limits our ability to maintain security and compliance in certain use cases.

Having the flexibility to enable automatic log-off even with an open transaction would greatly enhance our control over POS sessions and help us better align with our operational requirements.

Thank you for considering this enhancement!

When creating buyer's push orders for warehouse in other legal entities (for example from DC legal entity to Store's legal entity), standard D365 takes the first intercompany customer-vendor relation that has been created.

But in a multicompany store setup, there will be a intercompany customer-vendor relation per store to enable correct manuel creation of replenishment orders from DC to store A, B or C in retail company (by using IC customer A, B or C).

But with buyer's push, this can't be configured resulting in incorrect intercompany customer-vendor that are taken.

IDEA:

Setup table with company - customer - vendor - company - warehouse that would be used by buyer's push when creating orders.

To harmonize the way D365 POS and D365 Call Center are applying currency rounding rules. In Call Center the Price Rounding Rule, which is set up at currency level, is used for the rounding of the unit price of a sales transation and the General Rounding Rule, which is set up at currency level, is used for therounding of the amounts (line, total, ...). In POS the Price Rounding Rule only is used for the rounding of all (unit prices and amounts) and also the number of decimals displayed on POS forms for prices and amounts is driven by the number of decimals in the Price Rounding Rule. This is creating an inconsistent behavior within the D365 Commerce (Call Center and POS) solution expecially for customer who wants to extend (by EDT extension) the number of decimals used for unit prices (e.g. from 2 to 4) but keeps amounts with 2 decimals and apply a different rounding rule for the unit price and for the amounts.

Coupon codes cannot be manually added to return orders for an unlinked return where the customer used a coupon. The parameter "Manual entry of coupon codes for return without receipt" only works on POS. Call center orders can only receive discounts either automatically for all existing coupons (regardless of activation or validity period) or not at all because the Coupons button is disabled for returns.

Call center returns should be capable to selectively apply coupons to return orders without an all or nothing approach that doesn't fit standard business practice.

It would be great to have a mode of delivery selection functionality that is more like an ecommerce experience when creating a call center sales order. instead of having to default or set the mode of delivery on the header/lines, the system should give you mode of delivery options at the order completion stage.

The new API in the bug fix 908017, which has been released in version 10.0.41, which is for any location-controlled item, even if the item has a specific location, it will still prompt the user for the receive or ship location. 

For example, in demo data, we have 3 inventory locations for Houston: 1- Houston 2- Houston defect 3- Houston return. so, for that it is logical to ask for a location, but some customers have only 1 location for the store, so it is not logical to prompt him to select a location.

This will be an additional step that is not required for this situation.

When creating a new customer from the form Retail and Commerce > Customers > Customer Service, you are returned to the Customer Service screen instead of the newly created Customer record. If you didn't make note of the Customer Account Id in the New Customer popout, it's very difficult to find the account you just created.

Suggestion: when creating a new customer within the Customer Service screen, you should be brought to the newly created customer record.