Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Feature: Freedom from required price lists on OpportynityQuoteOrderInvoice entities.
On top of that, upon the user changing it on the form to "Use Default", the unit price field changes to zero and locks.
The particular use case is when the situation calls for custom pricing plugin. The ispriceoverridden field is important and depending on users to ALWAYS set it "off" is a certain risk. That's why we have default value setting on bools and optionsets, right? And even if the zero doesn't matter, it is a confusing user experience.
ps- the current behavior is that lacking a price list association the process goes and gets the price on the product's default price list, anyway. So it's not like the functionality calls for users to always override zero.
Oops! Maybe I shouldn't have pointed that out. I'll end up losing the wrong feature.
Business Applications communities