Module 2 · Set up Business Central · 150 min estimate
Dimensions, workflows and core implementation controls
By the end, you can
- Configure dimensions, values, global/shortcut dimensions, default rules, blocked combinations and priorities.
- Set up reports/layouts, number series and monitored job queues.
- Enable available Copilot/agent capabilities with appropriate data-governance and permissions, and configure approval users, groups and notifications.
Choose the control that fits the requirement
- Need analytical labels?Dimensions, defaults and priority rules.
- Need invalid combinations blocked?Dimension combinations and value-posting validation.
- Need independent authority?Approval user setup plus enabled workflow.
- Need unattended execution?Job queue entry with status and execution logs.
- Need AI assistance?Available capability, governance, permissions and human review.
Design analysis before the first posting
Northstar wants profit reporting by department and region without creating a new G/L account for every combination. Dimensions add analytical labels to transactions. Define a DEPARTMENT dimension with SALES and ADMIN values, and a REGION dimension with SOUTH and NORTH values. Agree definitions with finance: if two teams use SOUTH differently, a technically valid report is still misleading.
Choose the most widely used dimensions for the two global positions and the available shortcut positions. The two global dimensions are also shortcut dimensions; eight shortcut positions do not mean eight plus two separate shortcut fields. Default dimensions on customers, vendors, items and G/L accounts can populate transaction values. Value-posting rules can require a value, enforce a particular value or prohibit a dimension. Defaults improve consistency but must be tested against the actual posting scenario.
Use account-type defaults and the Default Dimensions-Multiple workspace where appropriate to apply a consistent rule across a selected set of accounts. Review the selected records before applying a bulk change. A requirement for every expense account to carry a department should become a tested value-posting rule, not a reminder in a spreadsheet.
Resolve competing defaults and invalid combinations
An ADMIN expense account defaults DEPARTMENT=ADMIN, while the document customer defaults DEPARTMENT=SALES. Before deciding which wins, inspect default-dimension priorities for the relevant source and account types. A priority rule resolves a conflict between defaults; it does not remove mandatory-value checks or legalise a blocked combination. Use dimension combinations to prohibit a whole pairing, or selected value combinations to block a narrower case.
For example, the business permits SOUTH with SALES but never NORTH with ADMIN for a restricted project. Enter one valid and one invalid training journal. Posting preview should accept the valid combination and reject the prohibited one. Then make a required department blank and verify that it also fails. A report filter cannot repair inconsistent dimensions after posting. Document the intended defaults, their precedence and a small table of positive and negative acceptance tests before users start entering live transactions.
Make background and document services observable
Number series control document identity. Decide which records need separate series, permitted manual numbering, date ranges and relationships before posting. Do not assume that every series guarantees gapless legal numbering. Validate local requirements and the selected numbering behaviour. Reusing the same number convention for unrelated documents makes investigation harder, even when the system permits it.
Report selection chooses which report is used for a document context; a layout controls the presentation of a report’s dataset. Changing a logo in a layout does not add a missing dataset field. Test the selected report and layout in the correct company and against representative documents. Job queues run scheduled application tasks. Configure recurrence, execution identity, category and retry expectations, then inspect status and log entries. A job marked Ready is scheduled, not proof of successful business processing. Investigate permissions, filters, dates and the application error before repeatedly restarting a failed task.
Approval is a controlled business transition
A native workflow combines an event, conditions and responses. For purchase approval, define who can request, the amount limit, approver or workflow group sequence, substitute and notification method. Enable the workflow only after testing. Northstar’s buyer requests an order for 8,000 while the buyer’s approval limit is 5,000. The expected result is an approval request to the authorised approver, a controlled document status and a usable notification, not silent self-approval.
Test the threshold boundary, cancellation, rejection and substitute path. A notification failure and an approval-routing failure are different defects. Inspect approval entries and workflow steps before changing email setup. Keep the requester and approver distinct where the control requires independent approval. When the needed event or response is unsupported by native workflow, evaluate an appropriate extension or Power Automate process rather than inventing a native switch.
Deploy Copilot and agents as governed capabilities
Use the Copilot & agent capabilities page to inspect features actually available to the Business Central online environment. Check prerequisites, regional availability, feature state and the user’s required permissions. Data movement controls may be relevant when processing crosses geographies. Never assume a missing capability is solved by granting SUPER or that every capability has identical permission controls.
Try one supported low-risk action, such as a number-series suggestion, with synthetic data. Compare the proposal with business rules before applying it. For a built-in agent, identify its permissions, supervision and actions that need review from that agent’s current documentation. A generated suggestion is not evidence that posting setup is correct. E-document mapping can be useful adjacent practice when available, but it is not a separate June 2026 skills-group heading. Keep any optional extension or preview exercise clearly separate from the core exam coverage.
Sandbox lab: Configure and challenge an approval-and-dimension policy
Use synthetic records in your authorised sandbox. Record the company and work date before posting. Never run this exercise in a customer’s production company.
- In a disposable company create DEPARTMENT and REGION values. Assign defaults and one mandatory-value rule.
- Set global/shortcut positions deliberately and record a conflicting default scenario with its expected priority.
- Block one dimension-value combination. Preview a valid journal, a missing-value journal and a blocked-combination journal.
- Create a purchase approval workflow with two distinct test users, an amount limit and a substitute. Configure notifications using only an authorised test destination.
- Test requests immediately below and above the limit, then rejection and cancellation. Record approval entries and document statuses.
- Review a report/layout selection and a safe job queue execution. Inspect one available Copilot capability and record whether it is active and accessible without changing production policy.
Expected observations
- Three dimension tests produce their documented accept/reject outcomes.
- Requests follow the intended approval authority and notifications reach only the test destination.
- Report output uses the intended layout and the job queue has a successful execution log.
Evidence to retain
- Dimension policy and test table
- Approval transition log
- Report-layout sample with fictitious data
- Job-queue execution result and capability checklist
Cleanup
Disable the training workflow and job queue, remove temporary notification destinations and restore capability settings if changed with permission. Keep synthetic evidence only.
Common pitfalls
- Counting global dimensions as additional positions beyond the eight shortcut positions.
- Expecting priority rules to override mandatory dimensions or blocked combinations.
- Treating notification delivery, Ready queue status or an AI suggestion as proof of successful approval/posting.
Check your understanding
1. A report displays the wrong logo but the values are correct. Which control is the first candidate?
The report layout selected for that company and report.
The presentation layout governs appearance. The report dataset governs available data.
2. A job queue entry is Ready. Has its scheduled business task succeeded?
No. Inspect its execution and error logs after it runs.
Ready indicates scheduling state. Business success requires a completed run and expected output.
3. Two master records suggest different department values. What should you investigate?
Default-dimension priorities and the relevant value-posting and combination rules.
Conflicting defaults, mandatory values and blocked combinations solve different validation needs.