
Off the top, let’s make it clear that I am a bit of a dimension fanatic in Business Central. When you really understand dimensions and what they are capable of, the use cases are extensive. Dimensions can go far beyond providing options for full P&L analysis, although that is a key value proposition. I won’t go deeper into the scenarios we’ve leveraged them to solve…maybe that will be another post.
Business Central dimensions are one of the most powerful out of the box configurations to facilitate analysis by key classifications. Want to manage profitability by product line? Perfect – create a dimension. Want to monitor departmental costs? Perfect – create a dimension. Want to manage costs by various categories against budgets? Perfect – create a dimension. You get the idea.
This brings us to the dimension dilemma. I recently met with one of our ISV reselling partners who said they advise their clients to not use more than two dimensions because the data gets too difficult to manage and there are limitations beyond the first two. When I heard that, I died a little inside…but I kept my composure. I couldn’t disagree more with this viewpoint, and this partner’s customers were definitely getting less value out of Business Central than they should. I don’t want to get off on a tangent here, but I think some partners and users view dimensions as a necessary evil and try to figure out what they can “use” to serve as global dimension 1 and 2. Again…completely missing the value this mechanism provides.
So, let’s dig into the reasons this partner touted for avoiding several dimensions, and I will absolutely admit that with out of the box Business Central there is some validity to the concerns raised. Base BC does only provide two “global” dimensions that are available for filtering application-wide. Additional dimensions can be relatively easy to work with (as shortcut dimensions) but they are generally not available for direct filtering and tools like analysis views are needed to report on them. While I would absolutely argue that this is not a good reason to avoid using more than two dimensions, the limitation is legitimate. So, in our DimensionPath app, we addressed this by making the 6 shortcut dimensions work like globals, as fully as we could. Simply installing our app makes up to 8 dimensions available for direct filtering across the application…challenge #1 solved.
Now, let’s look at the data management and user burden argument. Again, I fully agree that if users need to manually populate dimensions all over the place, on master records or transactions, this can be prone to error or being missed. Business Central does have controls like mandatory dimension settings on accounts to help catch issues, but sometimes these won’t be caught until the point of posting, causing delays while users address issues. So, I always push to find ways to automate the dimension flow. If users don’t even need to think about it, so that dimension classifications just happen with minimal user action…that is the ideal scenario.
Business Central has its Default Dimensions that can be attached to master records to default onto transactions automatically. For some scenarios, this does the job in and of itself. If you’re using the Projects module to track costs related to the respective projects, and you have a project that should have its costs hit the MARKETING department, this is easily accomplished by adding a default dimension for that department. Now, transactions for the project automatically hit the marketing department without relying on any action by users. Hooray….but this brings us to a big “BUT”…
BUT, what if there isn’t a master record to attach the default dimension(s) to? This is not a scenario specific to projects, but let’s continue with that example. What if the Project module isn’t being used (too much override…unnecessary functionality…whatever the decision criteria might be), but there is still a need to track expenditures against projects. All good…we use a PROJECT dimension instead, and post expenses to that project, not entirely unlike using an actual Project module record. But what about our need for everything posted to that project to hit the marketing department? We can’t attach a default dimension anywhere…users will be posting using items or G/L accounts that are used across many projects. At a G/L account level we can establish a mandatory dimension requirement for DEPARTMENT, but that isn’t caught until late in the process…and what if not all transactions to that account SHOULD have a department classification? This is where another DimensionPath feature plugs the gap.
DimensionPath provides a setup for Dimension Relations, to enable one dimension selection to populate a value for another dimension, and to lock the dimension values down (if desired) to ensure users do not mess with the relationship on transactions. So, with DimensionPath, we can define a firm relation from the SUPERBOWLAD project to the MARKETING department:

With that simple setup, magic happens. Now, when users select the SUPERBOWLAD project ANYWHERE in Business Central, the department automatically populates as MARKETING and attempts to change it are blocked. One simple setup and we are now capturing the department classification on transactions with zero steps by the user. Nothing to forget, nothing to get wrong…it just happens automatically.
The related dimension setup opens up all sorts of possibilities to manage and capture dimensions more easily and more accurately. As another example, consider a dimension value structure with parent/group classifications:

Here we have the Area dimension from the Business Central demo data (Cronus). The Area dimension has a nicely organized hierarchy of dimension values and totaling structures…it’s lovely, isn’t it? Where it gets ugly though, is on the usability and capability side. I’d like to see our financials at a glance for the European market, so I put a totals filter on the Chart of Accounts for Area 55 – the Europe total. This is where user frustration starts (and we’ll ignore the fact that Area 55 sounds like an extraterrestrial crash site):

Well…we got nada. Underlying entries aren’t posted to Area 55 directly, and the filter is very direct/literal…so we can’t filter for these higher level codes. Users need to constantly use filtered ranges, manually filtering for all values within a given group. While there are some places the totaling structure works, its usefulness is very limited. Thankfully, this is another great use case for DimensionPath and its dimension relations.
Using dimension relations for a far-more-powerful structure, we would replace the indented/grouped dimension structure for AREA with three separate dimensions. Let’s use REGION for the second level grouping (eg. Europe North) and MARKET for the broader grouping (Europe / America). Under this structure, we define the group/total options under REGION and MARKET. The AREA dimension then just has the direct/posting values, and each of those has a relation to the REGION they are in. Each of those regions then has a relation to the MARKET it is in. Dimension Relations work fine with a multi-level structure like this – all relevant related values will populate when the lowest-level one is selected.

With this setup in place, when a user selects Area 30 anywhere in Business Central, they will immediately see the Region fill in as EU-NOR and the Market as EUROPE. One simple selection and the rest of the work is done automatically.

And now we get the benefit of this setup. All three dimensions/values now carry through on posting so (as long as they are included in the 8 global dimensions) users can now filter at any level – Area, Region or Market:

There are other setups that can be used to control the data further (eg. require an AREA code whenever a posting is done for a REGION, to ensure the region can’t be posted directly without an area specified) but let’s not get bogged down in the weeds. Just know that you have many great options here. There is a better path!
Stay tuned for part two of this post where we’ll dive deeper into some gaps and the tools we have to address them, such as our Dimension Subsets to limit options for one dimension based on other dimension selections.
Learn more and download from AppSource and please visit our .
