-
Channel Date for Finding Prices (All customers and all sales orders)
Suggested by Alexander KNAPP – New – 0 Comments
In the Price simulator you have the possibility to use the field "Channel Date and time". This date will be used to find prices on a specific date.
It would be great if there is a possibility to make this field (and functionality) also available in All customers and in All sales orders.
Because we have customers who don't accept a price increase right from the start and therefore it will help us if we can insert a date on the customer (and also to be flexible on the sales order) and the sales prices will be found due to this date.
Example: we have a price increase which is valid from 01.07.2023. The customer who doesn't accept the price increase for this date (he accepts the increase only a few months later), will get in All customers the "Channel Date" 30.06.2023. So the system finds the old prices which are valid before the price increase.
-
Enable button grid editing for :Online store transactions" form
Suggested by Shafeeque P. – New – 0 Comments
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
-
Give unit price with discount when quantity is greater than one (CalculateSalesDocument API endpoint)
Suggested by Junior DUSSOUILLEZ – New – 1 Comments
Context: We use the Commerce (CSU) OData API to get prices and send orders in D365 from a home-made website.
We are calling API endpoint "CalculateSalesDocument" to get prices for products. When there is a discount, we would like to get the discounted unit price to display it, even if the quantity is greater than 1.
Example: my product price is 3.27€, with a 15% discount. My discounted unit price is 2.78€.
When I call the API for quantity 1, no problem, I use "ExtendedPrice" to get the discounted unit price. But when quantity is greater than 1, I can't get the "2.78" value. It's not in CalculateSalesDocument endpoint response. Would it be possible to add it? It's very important value IMO.
POST xxxx/Commerce/CalculateSalesDocument
Content-Type: application/json
{
"salesDocument": {
"Id": "CalculateSalesDocument",
"CustomerId": "CS000003",
"CartLines": [
{
"ProductId": 5637197959,
"Quantity": 1,
"UnitOfMeasureSymbol": "Pcs"
}
]
}
}
Response:
{
"@odata.context": "...",
"CartLines": [
{
"Quantity": 1,
"Price": 3.27,
"ExtendedPrice": 2.78,
"TotalAmount": 2.78,
"NetAmountWithoutTax": 2.78,
"DiscountAmount": 0.49,
"LineDiscount": 0.49,
"LinePercentageDiscount": 15.000000000000000000000000,
"PriceLines": [
// ...
{
"RecordId": 5652434827,
"Value": 3.27,
"PriceMethod": "Fixed"
}
],
"DiscountLines": [
{
"EffectiveAmount": 0.49,
"EffectivePercentage": 14.98,
"Percentage": 15.000000000000000000000000
// ...
}
]
// ...
}
]
// ...
}
When I change quantity to 2, I can't find "2.78" anywhere in the response.
{
"@odata.context": "...",
"CartLines": [
{
"Quantity": 2,
"Price": 3.27,
"ExtendedPrice": 5.56,
"TotalAmount": 5.56,
"NetAmountWithoutTax": 5.56,
"DiscountAmount": 0.98,
"LineDiscount": 0.98,
"LinePercentageDiscount": 15.000000000000000000000000,
"PriceLines": [
// ...
{
"RecordId": 5652434827,
"Value": 3.27,
"PriceMethod": "Fixed"
}
],
"DiscountLines": [
{
"EffectiveAmount": 0.98,
"EffectivePercentage": 14.98,
"Percentage": 15.000000000000000000000000
// ...
}
]
// ...
}
]
// ...
}
Having "2.78" value in a new field "DiscountedUnitPrice" would be great.
-
Threshold discount :Apply Discount to Cheapest Eligible Product in Multi-Item Cart If Threshold Met and Calculation type: Discount lines
Suggested by Deepak Poddar – New – 1 Comments
Hi Team
Title:
Threshold discount: Apply Discount to Cheapest Eligible Product in Multi-Item Cart If Threshold Met and Calculation type: Discount lines
Idea Description:
As part of our ongoing efforts to optimize promotional pricing strategies within Microsoft Dynamics 365 Commerce, we propose introducing a configurable setup option for Threshold Discount Calculation Type = "Discount Line". This enhancement will allow for more granular control over discount application based on item-level criteria.
Proposed Enhancements:
Threshold Discounted Line Tab Configuration:
Enable selection of specific items, categories, or product variants to be eligible for threshold-based discounts. Introduce a mechanism to define whether the discount should apply to:
- The cheapest eligible item in the cart.
Threshold discount tires -Configuration Options:
A toggle or dropdown to select "Apply to Lowest Value Item" or "Apply to Highest Value Item".
Automation & Flexibility:
Once the predefined threshold is met, the system will automatically apply the discount to the selected item based on the configured rule.
"This feature would allow businesses to run promotions like “Buy 3 items, get the cheapest one at 10% off” and “Spend $100, get the lowest-priced item free,” and favoring retailer "
Problem Statement:
The existing implementation applies the discount to the highest-priced eligible item by default and favoring customer
Proposed Solution:
Set up option to threshold discount tires ->Calculation type: Discount lines
require option to Higher and lower value promotion configuration mechanism in Microsoft Commerce
Checks if the cart meets a defined threshold (e.g., total value or item count).
Identifies the cheapest eligible item based on defined criteria (e.g., product category, brand, etc.).
Applies a Calculation type: Discount lines to that item only.
-
PO notes created from POS arrive as an attachment to HQ.
Suggested by Leonardo Villanueva Arce (SONATA SOFTWARE NORTH AMERICA INC) – New – 0 Comments
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.
-
Bulk Deletion of Publish Groups in Site Builder – Dynamics 365 Commerce
Suggested by Alonso Bravo – New – 0 Comments
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.
-
Automatic Log Off even when a transaction is in place
Suggested by Daniel Delgado Candia – New – 0 Comments
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!
-
Buyer's Push: Configuration of customer/vendor relations to define which to take during intercompany order creation.
Suggested by Jan Cavens – New – 0 Comments
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.
-
Currency Rounding Rules in D365 Call Center and POS
Suggested by Umberto Cristiano – New – 0 Comments
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.
-
Enable coupons on call center returns
Suggested by Brandon Best – New – 2 Comments
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.
You’re offline. This is a read only version of the page.
