Dynamics 365 Commerce

Master products without configured variants can currently be sold in POS, which later causes transaction validation failures and blocks invoicing.

There is no built-in validation to prevent this, leading to inconsistent data and manual fixes.

Currently POS allows selling such products, but they fail during validation and posting later.

What should be implemented is a validation layer to block selling master products that don’t have valid variants configured.

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

When you click on "Withdrawal," "Deposit," "Initial Balance," "Cash Withdrawal," or "Cash Deposit," the cash drawer opens immediately after clicking the button, without this action being logged. Only then are the amount and receipt recorded or issued. From an audit and traceability perspective, this process is problematic because it allows physical access to cash without prior or accompanying documentation.

Proposed solutions:

(Preferred solution) Adjust the process sequence so that the cash drawer is opened only after another documented step has been completed.

Implement logging of cash drawer openings (time, user, context).

Auto charges and trade agreements both use the Account Code hierarchy (Table / Group / All) to determine which rules apply to a transaction. However, they resolve matching rules in fundamentally different ways. Trade agreements use "most specific wins" — if a Table-level price exists, Group and All are skipped. Auto charges use accumulative matching — if rules exist at both Group and All level, BOTH fire, causing double-stacking of charges on the same order.

This inconsistency is counter-intuitive for D365 practitioners, leads to unintended double-charging in common B2B/B2C scenarios, and forces workarounds (eliminating all "All" rules and assigning every customer to an explicit charge group) that increase configuration complexity and operational risk.

I propose aligning the auto charge Account Code resolution with the trade agreement pattern: most specific match wins, less specific levels are skipped. The AND logic already exists at the charge line level within a single header — it does not need to be duplicated at the header/account code level in my opinion.

The change is isolated to the ApplyAutoCharges method in the CRT Services layer, requires no database schema changes, and can be gated behind a configuration parameter for backward compatibility.

A detailed analysis with code-level evidence from the decompiled CSU V9.57/10.0.47 codebase is attached.

Currently, the Dynamics 365 Commerce Media Library displays error messages suggesting that .VTT and .TTML files are supported for video content. However, after technical consultation, it has been confirmed that the ability to upload and associate these transcript files with videos is not currently functional or available.

This creates a significant barrier for organizations striving to meet global accessibility standards, such as AODA (Accessibility for Ontarians with Disabilities Act) and ADA (Americans with Disabilities Act) compliance. Without native support for captions, businesses risk legal non-compliance and provide a sub-par experience for users who are deaf or hard-of-hearing. The system currently references these file types in error prompts, leading to user confusion and lost productivity.

We are requesting the full implementation of the Closed Caption upload feature within the Media Library. Specifically:

1. Direct Upload: Allow users to upload .VTT or .TTML files directly to a video asset's properties.
2. Multi-Language Support: The ability to associate multiple caption files for different locales.
3. Native Player Integration: Ensure the D365 Commerce video player module recognizes these files and displays the closed captions for end-users.

We believe this will enhance business value by:

• Accessibility: Ensures all customers can consume video content regardless of hearing ability.
• SEO Benefits: Properly indexed transcripts can improve searchability.
• Efficiency: Allows marketing teams to utilize pre-edited, high-quality transcripts directly within their existing workflow.

By enabling this feature, it will allow businesses to uphold their legal obligations and streamline the workflow for web administrators, ensuring that digital commerce remains inclusive, accessible, and barrier-free for all users.

Process a POS sales order that has broker commissions created from a broker contract. Broker commissions created against sales order line/s. Broker claim created on sales order invoice update.

Process a POS return (using the receipt number or via the journal view in POS) for the previous sales order.

Expected result: The broker commission should also be reversed against the negative sales order line.

Actual result: No broker commissions are created at all for the return.

This would be a useful feature especially considering there is a valid business case for it: We have a customer who are planning to go live soon, and this enhancement would be of great value.

Organizations using Microsoft Dynamics 365 Commerce Content Management System (CMS) require a structured and controlled content publishing process to ensure governance, compliance, and quality assurance.

Currently, the CMS does not provide a built-in approval workflow. Content created or modified by one user can be published without a mandatory review or approval step, forcing organizations to manage approvals outside the system. This creates operational inefficiencies, increases the risk of errors, and weakens governance controls.

We propose introducing a native approval workflow capability within D365 Commerce CMS with the following features:

• Multi-step approval workflows (e.g., Creator → Reviewer → Publisher)
• Ability to assign roles (e.g., Content Creator, Reviewer, Approver)
• Mandatory approval gating before content can be published
• Workflow status tracking (Draft, In Review, Approved, Rejected)
• Audit trail and version history for compliance and traceability
• Optional notifications/alerts for pending approvals
• Configurable workflows to support different business needs

Example Use Case

• User A creates or updates content (Draft)
• User B reviews and approves/rejects (In Review)
• Only approved content can be published to the live site

Business Impact

• Improves content governance and compliance
• Reduces dependency on manual/off-system processes
• Minimizes risk of incorrect or unapproved content going live
• Aligns CMS capabilities with enterprise content management standards

This enhancement would significantly strengthen the CMS capabilities within Dynamics 365 Commerce and better support organizations operating in regulated or large-scale environments.

Right Now:

Capability Evolution (Landmarks)

1. Current State – Role-Based Access

• Users are assigned roles (e.g., content author, editor)
• No enforced approval step before publishing
• Publishing control depends on user permissions only

With most of the customers, it is an issue that they want to capture the credit card payments as soon as the item is shipped or marked as delivered in d365. Currently, there is no way in the d365 to configure whether the payment should be captured at the time of packing slip posting or it should be done on invoicing as most of the time, invoicing is not done frequently especially for the partially shipped/delivered orders.

It would be a nice functionality to provide a configuration in the payment service setup whether to send the payment capture call at the time of packing slip posting or at the time of invoice posting.

Thanks.

FORCE full customer information on any transactions with Protection Plans - MUST HAVE INFORMATION POPULATED and Confirmed

We would like to have the Point Of Sale Email Receipt slider switch default to On when Customer Profile prefers emailed receipts. This is to ensure customers get emailed receipts when the Receipt formats Email behavior is set to Prompt user.

We need the Email behavior set to Prompt user so we can print Gift receipts for item load-out as necessary.

When prompted currently, both sliders default to "Off" regardless of the customer's preference.

This request is based on the result of the Microsoft ticket with TrackingID#2602020040010839.