web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Supply chain | Supply Chain Management, Commerce
Suggested Answer

Sales lines attribute not taken in account in Unified Pricing management Discount.

(1) ShareShare
ReportReport
Posted on by 8
Hi,
 
I created an attribute "Forwarder" for sales line and a Sales line attribute group. 
It added the attribute to the sales order lines, in the sales order line I can set it in the Retail Button > Retail attributes.
My attribute "Forwarder" as 2 values (Yes/No) and is set to yes.
 
My idea is to have a discount if Forwarder = Yes and no discount if forwarder = No.
 
I created a simple discount taking account the attribute Forwarder = Yes and some specifics items but the discount is not take in account.
If I keep in the same discount the item selection but I don't fill the Forwarder value the discount is take in account.
It looks like the sales line attribute doesn't work as expected.
 
Did you have test it ? Is it ok for you ?
I have the same question (0)
  • Suggested answer
    Peter Kulikov (N.progression) Profile Picture
    588 Moderator on at

    Hello!
    Sales line attributes defined and set via the Retail attributes (Retail > Retail button > Attributes) are currently NOT supported in Unified Pricing Management discount logic. This is expected behavior, as these are Retail-specific extensible attributes and are not integrated with UPM as valid filters for pricing or discounts.

    • UPM supports Sales line attribute groups to classify sales lines, but this only works with attributes that are directly tied to pricing logic (e.g., stored on the SalesLine table or related pricing tables)

    • Attributes set via the Retail button → Attributes are part of the Retail channel context and are not used by UPM for price or discount calculation.

    Suggested solution:

    If your goal is to use a sales line attribute as a condition for a discount in UPM, then you should:

    • Create the attribute using Product information management > Setup > Attributes, not via Retail attributes.
    • Assign it to a Sales line attribute group that is referenced in UPM.
    • Ensure that the attribute is visible and its value is set before the discount is calculated.
    • If needed, consider extending the pricing logic via customization to support additional attributes not handled out-of-the-box.
     
  • Arnaud L'Hérondel Profile Picture
    8 on at
    Hi Peter,
     
    I did not set my attribute by the retail but into a Sales line attribute group that is referenced in UPM.
    but the only way I found to see my attribute on the sales line is the retail button.
     
    And I created the attribute using Product information management > Setup > Attributes, not via Retail attributes.
     
    So I think I done what I am supposed to. I created the attribute, added it in a sales lines attribute group.
    After that I set a discount taking in account this sales line attribute that is not out of the box but appear in the attribute list so I think it's supposed to work.
     
    If the way of setting a sales line attribute value in the sales line is not in the retail button where is it ? I didn't find any place elsewhere to set it in the sales line. And in the retail button I see my attribute so I think it's the correct way, but I'm not sure.
    Price attribute group.png
  • Suggested answer
    Peter Kulikov (N.progression) Profile Picture
    588 Moderator on at
    Hi Arnaud,
     

    Even though the attribute was created via Product information management > Setup > Attributes and added to a Sales line attribute group that is referenced in Unified Pricing Management (UPM), the value was assigned using the Retail > Attributes button on the sales order line.

    The issue is that, despite using the correct method to define the attribute and assign it to a group, setting its value through the Retail button stores it in retail-specific tables, which are not integrated with UPM pricing logic.

    Currently, UPM does not support reading attribute values assigned through the Retail interface. As a result, UPM cannot evaluate the condition properly and does not apply the discount.

    Here you can find several confirmations from unofficial sources that Order Line attributes are not considered in Unified Pricing Management (UPM):

    And here is an official confirmation from Microsoft that currently only Order Header attributes are supported, while support for Order Line attributes is planned for the future:

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 143 Super User 2026 Season 1

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 102 Super User 2026 Season 1

#3
Laurens vd Tang Profile Picture

Laurens vd Tang 96 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans