Dynamics 365 Commerce

General approval processes for prices for F&O in general. Linked to Unified Pricing capabilities in F&O.

Add the capability to turn on approvals for unit price or/and discount on for sales order/quotation.

Users that change prices manually on order would need to send changes through approval workflow.

Another request would be approval workflow for new price components such as discount, before an discount can be enabled a workflow must be run for approval, approval process activated as a parameter.

We know how important and widely the infocode functionality is used in Commerce (POS).

But there's not much we can use wrt infocodes in the sales order creation via call centres in D365, example product level infocodes.

One of the scenarios is for Alcohol and Spirits products, where it's mandate to ask customers to confirm they are above age 18.

For this we have setup product level infocode and when these products are scanned in POS, it pops-up infocode for cashiers to ask customers to confirm if they above age 18.

But, there's nothing similar when orders are created over phone via call centre channels to remind agents to ask and confirm from customers about the Age 18 prompt on specific products.

It would be lovely if we can extend the product level infocodes to D365 call centre order functionality,

In current design, the system does not support aggregating products in one single return label, so if you are printing return label for one line with 3 quantities, it will print 3 return receipt labels.

It would be great to have a feature in the future to support aggregating products in one single return label receipt when printing from POS.

Currently if you are fulfilling/returning a sales order, you are unable to add a gift card and refund the amount of the sales order. For cash and carry transactions you can add a gift card to the return transactions and can book the refund on the Gift card. The same cannot be done for sales order during the return. You either need to issue a gift card which you can only with min 0,01 cent which again creates a difference in the till. Then you can use the gift card payment method to refund this. There should be a possibility to do a refund by issuing a new gift card also during the return sales order process.

A common scenario for e-coms and retailers is to start and/or end a campaign at a specific time, e.g. "Buy product X at 50% discount as long as there are stock available".

D365 Commerce supports configuration of "Effective date" and "Exparation date", but nothing defining a particular start and/or end time. There is a the concept of "Date validation period", but that does not meet the requirement.

Idea:

1. Implement the possibility to define "Start time" together with "Effective date"
2. Implement the possibility to define "End time" together with "Expiration date"

Sales orders raised via online stores have the SalesLine Text field populated with the Product master description rather than the variant product description. The user should see the variant product description to identify different product variants involved in the transaction.

Problem Statement

When creating Virtual Tables using the Modern Power Apps Maker UI, the current experience introduces multiple limitations compared to the Classic (Advanced Settings) UI, making it unsuitable for enterprise and ALM-governed environments.

1. Connection Reference Reuse Limitation

In the Modern UI:

• Only connection references owned by the currently logged-in user are visible and selectable.
• Existing Virtual Table Data Sources created using a shared service account are not reusable by other developers.
• This forces each developer to create their own connection reference, even when the same backend SQL connection is already configured.

In contrast, the Classic UI:

• Surfaces Virtual Table Data Sources directly
• Allows all authorized users (e.g., System Customizers) to reuse existing data sources regardless of connection ownership.

2. Limited Control Over Column Definition and Schema Evolution

The customer also confirmed additional functional gaps in the Modern UI:

“The new UI for virtual tables is currently not fit for purpose and we will be continuing to use the classic UI for now.”

Specifically:

• The Modern UI provides very limited control over column data types during virtual table creation.
• It does not support future updates to Virtual Table schemas, such as:
• Adding new columns
• Modifying column definitions
• These capabilities are available in the Classic UI, where users retain full control, even if the process is more manual.

As a result, teams must continue relying on the Classic UI to:

• Properly model data types
• Maintain virtual table schemas over time
• Support evolving backend SQL structures

Expected / Desired Behavior

Enterprise customers expect the Modern Maker UI to reach parity with (or exceed) Classic UI capabilities:

1.Reuse Existing Virtual Table Data Sources

• Surface Virtual Table Data Sources directly in Modern UI
• Allow reuse regardless of connection reference ownership
• Respect environment-level permissions (e.g., System Customizer)

2.Full Column Control & Schema Maintenance

• Allow explicit control of column data types during creation
• Support updating Virtual Table schemas (e.g., add new columns)
• Enable safe, iterative virtual table evolution

Proposed Improvement

Align Modern Maker UI behavior with Classic UI for Virtual Tables

Surface Virtual Table Data Sources instead of restricting selection to user-owned connection references

Enhance the Modern UI to support:

• Column data type management
• Schema updates post-creation

Extensions are not showing on Store Commerce app on mobile. We have tried both IOS and Android but I didn' t work. It has to be flexible like CPOS. Our system has some of custom fields especially on the create customer page. We have more than 10000 cpos users and they do not able to use this app because of the issue.

Currently it's not possible to make a partial payment on the remaining amount of an invoiced sales order through POS. We should have the ability to conclude an invoice after making a partial payment on POS while leaving an unpaid amount to be paid at a later time.

Hello,

When DOM runs, it assigns GPS coordinates to address in order to calculate closest fulfillment location.

It turns out, the GPS coordinates assigned to address are NOT the coordinates of the address but instead are the coordinates of the postal code. This is confirmed by Microsoft here https://fix.lcs.dynamics.com/Issue/Details?bugId=976780&dbType=3&qc=2a3ef6689b475bbd2d23006f8ae5ae48cef467f0f242f6563e644bc8a55179a0

This causes the discrepancy when sales tax is calculated as the gps coordinates take priority over address.

The logic should be changed to assign the gps coordinates of the address.

Thanks.