Dynamics 365 Finance Account Structure Dimension Requirements
Short answer
B No, because the solution uses asterisks for all dimensions instead of using asterisk-quote combinations for optional ones like customer or project.
Question
whether the solution meets the stated goals. Some question sets might have more than one correct solution, while others might not have a correct
solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A customer uses Dynamics 365 Finance.
The controller notices incorrect postings to the ledger entered via journal.
The system must enforce the following:
✑ Expense accounts (6000-6998) require department, division, and project with all transactions. Customer dimension is optional.
✑ Revenue accounts (4000-4999) require department and division and allow project and customer dimensions.
✑ Liability accounts (2000-2999) should not have any dimensions posted.
✑ Expense account (6999) requires department, division, project and customer dimensions with all transactions.
You need to configure the account structure to meet the requirements.
Solution:
✑ Configure two account structures: one for liability accounts listing the (2000-2999) range with no following dimensions and one for Expense and Revenue
accounts.
✑ For Expense accounts (6000-6998) and Revenue accounts (4000-4999), configure asterisks in all dimension columns.
✑ For Expense account (6999), configure asterisks in all dimensions. Configure an asterisk and quotes in the customer dimension.
Does the solution meet the goal?
Key Takeaways
The trap is confusing mandatory () with optional (") dimensions; failing to distinguish them results in incorrect enforcement of posting rules.
Learn how to configure account structures in Dynamics 365 Finance using correct dimension syntax. The answer is B because optional dimensions require asterisk-quote pairs.
Common mistake: Many candidates choose 'Yes' because they recognize the need for two account structures but overlook the specific syntax required to mark dimensions as optional, leading to overly restrictive validation.
Expert Analysis
Dimension Configuration Syntax in Dynamics 365 Finance
The core of this question tests the precise syntax for defining required and optional dimensions within an Account Structure. In Dynamics 365 Finance, an asterisk () denotes a mandatory dimension value. To make a dimension optional (allowing blank entries), you must use an asterisk followed by double quotes ("). This specific syntax ensures that users can post without entering a value for that dimension.
Analysis of the Proposed Solution
The solution proposes using asterisks in all columns for Expense accounts (6000-6998) and Revenue accounts (4000-4999). However, the requirements explicitly state that for these ranges, certain dimensions are optional:
- Expense (6000-6998): Requires Department, Division, Project. Customer is optional. The solution fails to mark Customer as optional.
- Revenue (4000-4999): Requires Department, Division. Project and Customer are optional. The solution fails to mark Project and Customer as optional.
- Expense (6999): Requires Department, Division, Project, and Customer. All are mandatory. The solution incorrectly adds quotes to the Customer dimension, making it optional when it should be mandatory.
Because the solution does not apply the " syntax to the optional dimensions specified in the requirements, it enforces stricter validation than intended. For example, it would force users to enter a Customer ID for Expense account 6500, which violates the requirement that Customer is optional. Therefore, the solution does not meet the goal.
Operational Consequence
Configuring dimensions incorrectly leads to user frustration and potential data integrity issues. If mandatory dimensions are marked optional, financial reporting may become inaccurate due to missing segment data. Conversely, if optional dimensions are marked mandatory, valid transactions will be blocked, disrupting business operations. Understanding the difference between and "* is critical for accurate ledger configuration.
Exam Strategy
When configuring account structures, always map each requirement to a specific segment column. Use only an asterisk () for mandatory fields and asterisk-double-quotes (") for optional fields. Double-check every range against the requirement list to ensure no optional field is mistakenly made mandatory.
Frequently Asked Questions
What is the difference between * and *" in D365 Finance dimensions?
Why do I need separate account structures for different account ranges?
Community Votes
67% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
H_Incandenza 👍 5This is really tricky. The first account structure is correct. Your second account structure should look like this where the order of segments is department, division, project, and customer and backslashes separate each segment: -4000-4999: / / / ""; -6000-6998: / / ""; / ""; -6999: / / / So, comparing this to what the question states, the last value for 6999 should be an asterisk, not an asterisk and quote ("";*). Similarly, the last two segments for 6000-6998 should NOT be asterisks but asterisks and quotes; while the same is true for the last segment of accounts 4000-4999. Please, anyone, if I misstated this, correct me.
-
Yael_Shachen_Tov 👍 5Correct
-
c43d561 👍 2No, the solution does not fully meet the goal. Here’s why: Liability Accounts (2000-2999): The solution correctly configures an account structure for liability accounts with no dimensions, which is correct. Expense Accounts (6000-6998): The solution suggests configuring asterisks in all dimension columns. However, it should specifically require department, division, and project dimensions, and make the customer dimension optional. Revenue Accounts (4000-4999): The solution suggests configuring asterisks in all dimension columns, but it should specifically require department and division dimensions, and allow project and customer dimensions. Expense Account (6999): The solution suggests configuring asterisks in all dimensions and an asterisk and quotes in the customer dimension. However, it should specifically require department, division, project, and customer dimensions.
-
Daniel73847 👍 2 Answered B"For Expense accounts (6000-6998) and Revenue accounts (4000-4999), configure asterisks in all dimension columns", based on the requirement the customer dimension is optional, so the value could be blank, therefore it should be asterisk and quote.
-
WisanuMa 👍 1 Answered B- Configure two account structures is correct - For Expense accounts (6000-6998) is correct - Revenue accounts (4000-4999) should config asterisks and quotes - Expense account (6999) Should config asterisk (no quotes)
Show 1 more comment
-
Omniaa_abd_elmonem75 👍 1 Answered Aanswer must be yes
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All MB-310 Questions
Access 100 questions with complete answers and detailed explanations.
View Full MB-310 Practice Test →