Migrating from 2009 to D365 and working on Dimension Setups - Is there an easy way to set up financial dimension values per legal entity without having to set up a legal entity override on ALL values? We have two dimensions (department and Product lines) with 20-30 values in each. There are 3 different legal entities with their own distinct values. Do we need to include ALL dimensions values and then just create a whole bunch of legal entity overrides so that the correct dimension values are seen by each legal entity? Would it be easier/better to set up different dimension (header) for each company? 'Department_CO1', Department_Co2', 'Department_Co3'? Then we can set the values distinctly in the appropriate dimension header, configure multiple account structures specific to each legal entity and use those account structure in the ledger setup for each legal entity?
I agree with Nuno's points below. Legal entity override is likely a cleaner solution as it will restrict the list of available dimensions in all forms so users will only see their own distinct values. Account structures don't restrict the dimensions on vendors, customers, etc.
There is a data entity that can be used, if needed, for the initial setup.
The other consideration is that it is possible two different companies are using the same dimension value for different purposes (different names). Example - Department 2000 might be R&D for company 'A', but Manufacturing for company 'B'
Nuno Maia
When you say 'dimensions override', how is that different than legal entity overrides?
Hi Andre,
Thanks for the response. Are you saying to use the account structures in a similar way to how you would use the legal entity overrides, only allowing the user to choose a department that is valid in the account structure? Do the account structures limit which values will be available in a form 'lookup'? I think users would be annoyed if they can see dimensions for other companies in their lookup. I'm imaging that the legal entity overrides would exclude values in the lookup that are blocked for your legal entity.
Thanks.
Hi Tim,
Next to the two options you mentioned, there is a third one. You can have single dimensions and different account structures per legal entity. On the account structure, you can define which values are valid per ledger.
To decide what to do, you should consider how users should work with the application, but also take reporting requirements into account and maintenance on new or deprecated dimension values.
From my point of view, create one FD for department and Product is more convenient from reporting and import and export perspective.
I have seen both approaches and both are valid.
In implementations where account structures are centralized and a modification is valid for all legal entities, it is preferred to have legal entity overrides. If you are using a centralized chart of accounts and account structure, I would go for dimensions override. Personal opinion
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CA Neeraj Kumar 2,317
André Arnaud de Cal... 918 Super User 2025 Season 2
Sohaib Cheema 656 User Group Leader
