MB-800 · Question #155
Drag and Drop Question A company uses Business Central. The company recently restructured. The company has only a few posted entries. You need to change the Global Dimensions in Business Central to…
Changing Global Dimensions in Business Central - Explained Context Global Dimensions (1 and 2) are set in General Ledger Setup. Changing them after posting entries requires a dedicated workflow because all existing entries must be re-tagged. Business Central provides a Change…
Question
Exhibit
Options
- 1Update Global Dimensions in parallel order.
- 2Select Parallel processing on the Change Global Dimensions page.
- 3Select new dimension codes in the dimension fields.
- 4Update Global Dimensions in sequential order.
- 5On the General Ledger Setup page, select Change Global Dimensions.
Explanation
Changing Global Dimensions in Business Central - Explained
Context
Global Dimensions (1 and 2) are set in General Ledger Setup. Changing them after posting entries requires a dedicated workflow because all existing entries must be re-tagged. Business Central provides a Change Global Dimensions page with two processing modes: Sequential and Parallel.
The Correct Three-Step Sequence
| Step | Action | Why |
|---|---|---|
| 1 | On the General Ledger Setup page, select Change Global Dimensions | Entry point - this opens the dedicated change workflow. You cannot change Global Dimension codes directly on the GL Setup page once entries exist. |
| 2 | Select new dimension codes in the dimension fields | You specify the replacement codes for Global Dimension 1 and/or 2 here before any processing begins. No data is changed yet. |
| 3 | Select Parallel processing, then Update Global Dimensions in parallel order | This triggers the actual update across all tables (ledger entries, journals, etc.). |
Why Each Item Is Placed Where It Is
Item 5 → Step 1 ("On the General Ledger Setup page, select Change Global Dimensions") The GL Setup page is the only entry point. The "Change Global Dimensions" action opens a separate page designed for this workflow. You must go here first - there is no other way to initiate the process safely.
Item 3 → Step 2 ("Select new dimension codes in the dimension fields") Before triggering any update, you define what you're changing to. This is a configuration step, not a processing step. If you skip this and run the update, nothing meaningful happens.
Item 2 → Step 3a ("Select Parallel processing") You choose the processing mode before clicking Update. Parallel mode runs the re-tagging across database tables concurrently using background sessions.
Item 1 → Step 3b ("Update Global Dimensions in parallel order") This is the execution step - it commits the changes. It only becomes available after you've selected new codes and a processing mode.
Distractors and Common Mistakes
Item 4: "Update Global Dimensions in sequential order" This is the key distractor. Sequential processing runs table-by-table in a single session. It is technically valid but is typically chosen for very large datasets where parallel might cause lock contention - or, paradoxically, for very small datasets where the overhead of parallel sessions isn't worth it. Since the question states the company has only a few posted entries, sequential might seem like the intuitive choice - but exam questions in this domain often test that you know how to use the parallel workflow, so check your specific exam's answer key carefully. Some versions of this question use sequential as the correct answer precisely because of the "few posted entries" hint.
Reversing steps 2 and 3 A common mistake is trying to select the processing mode before selecting the new dimension codes. The UI does allow this, but logically you must define what to update before how to update it.
Skipping Step 1 entirely You cannot change Global Dimensions from the main GL Setup fields once entries are posted - Business Central will block it and direct you to use the Change Global Dimensions action. Step 1 is mandatory, not optional navigation.
Topics
Community Discussion
No community discussion yet for this question.
