Add Price List Unit Each in Dynamics 365 Sales
A company manufactures widgets. Widgets can be sold in the following ways:
The company discovers that customers in Europe want to purchase widgets individually. The company must update the EU price list to allow individual widget purchases.
You need to add a price list for the new unit named Each.
What should you do?
Community Insight
The question tests the configuration of Units of Measure where the smallest unit (Each) must be designated as the Primary Unit to enable direct pricing at that level.
To allow individual widget purchases in the EU price list, you must configure 'Each' as the primary unit of measure. This page explains how to set up units of measure hierarchies correctly in Dynamics 365 Sales.
Learners often choose to create 'Each' with 'Box' as the base unit (Option C), which reverses the hierarchy and prevents 'Each' from being used independently for pricing.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
In Microsoft Dynamics 365 Sales, the Units of Measure feature allows you to define different ways to measure products. To sell a product individually when it is typically sold by the box, you must ensure the smaller unit ('Each') is recognized as the standard or 'Primary' unit. Setting 'Each' as the primary unit allows the system to accept quantities in 'Each' directly on quotes and orders, satisfying the requirement to update the EU price list for individual purchases.Why the Other Options Are Wrong
Option B is incorrect because updating a larger unit (Box) with a smaller one (Each) as its base unit defines the relationship but doesn't make 'Each' the primary option for sales transactions. Option C is incorrect because it creates a reverse hierarchy; 'Box' should be based on 'Each', not the other way around, and simply creating it doesn't make it the primary choice. Option D is incorrect because making 'Each' the base unit for all units disrupts existing relationships (like Box and Pallet) and is not the standard method for enabling a new unit type without affecting others.Community Comment Notes
The community consensus strongly supports setting 'Each' as the primary unit. As user Shaiii102500 noted, setting 'Each' as the primary unit is sufficient to enable individual purchases, while other options either reverse the relationship or are insufficient on their own. The comment highlights that 'Each' needs to become the lowest/primary unit to be effective for pricing.Exam Strategy
When configuring Units of Measure, always identify the smallest unit of sale required. If customers need to buy in the smallest increment, that unit should be set as the Primary Unit to allow flexible pricing and ordering.
Frequently Asked Questions
Why can't I just create 'Each' with 'Box' as the base unit?
Creating 'Each' with 'Box' as the base unit reverses the hierarchy. 'Box' should be defined in terms of 'Each', not vice versa, to maintain logical consistency.
Does setting 'Each' as primary affect existing Box pricing?
No, setting 'Each' as the primary unit allows it to be used for pricing without disrupting the definition of larger units like Box, which can still reference 'Each'.
Related Analysis
Practice All AB-210 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AB-210 Practice Test →