0
On quote detail the system automatically sets Price Overridden (ispriceoverridden) to true when the user has override privilege. This design decision makes sense.
However, I find that I cannot execute the formContext attribute setValue(false) function. So, while the user can waste time setting it to false, a customizer cannot do it for him.
This design not only DOESN'T appear to add any utility, it actually goes out of its way to make matters worse.
According to support ticket #119122824000271, this is how the design team wants it. Please reconsider.
-ps this may be only under the circumstances of using the new feature of removing the price list requirement in the Phase 2 (Oct.2019) release.
However, I find that I cannot execute the formContext attribute setValue(false) function. So, while the user can waste time setting it to false, a customizer cannot do it for him.
This design not only DOESN'T appear to add any utility, it actually goes out of its way to make matters worse.
According to support ticket #119122824000271, this is how the design team wants it. Please reconsider.
-ps this may be only under the circumstances of using the new feature of removing the price list requirement in the Phase 2 (Oct.2019) release.
STATUS DETAILS
Declined
Bharath Varadarajan (administrator) on 8/28/2020 5:20:14 PM
Thanks for the feedback. The Pricing (Override Price vs Use default) field on product lines is relevant only when a price list is used and an existing product is added. When there is no price list or when adding a write-in product, there is no default price to pick; so the price is always considered overridden. When a price list is used and an existing product is added, the application will honor the default value defined as metadata of the Pricing field by the customizer.
Thanks,
Bharath Varadarajan
Dynamics 365 Sales