Finance | Project Operations, Human Resources, ...

List of important Global Forms across all modules

(2) Share

Report

Posted on by MYGz

2,360

Hi,

I have a scenario where we are considering to implement a new legal entity of different region in the existing environment. Both existing and new legal entity will have commerce implementation with full setup.

There are 2 options:

1. Implement in same environment.

2. Create new UAT/Prod Environment and implement in new environment.

For this, I want the list of global forms that will be shared with the new Legal Entity. Below are few that I know of, looking for more inputs.

System Administration Module most forms

Organization Administration Module most forms

Chart of Accounts

Financial Dimensions

Purchase Requisition

All Retail Stores

Would appreciate if you can add to this list.

Is there a way to get the list with full path (i.e GL > COA > Fin Dim) through X++ script?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Abhilash Warrier 7,563 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Please find below list -

1. System administration
•   Batch groups
•   Email parameters
•   User setup & security roles
•   Workflow configurations
•   Print management (some parts)

2. Organization administration
•   Legal entities (obviously global definition)
•   Number sequences (if shared scope)
•   Organization hierarchies
•   Global address book (Customers, Vendors, Workers)

3. Financial
•   Chart of accounts (COA)
•   Account structures
•   Advanced rule structures
•   Financial dimensions
•   Dimension value sets
•   Currency setup
•   Exchange rates

4. Procurement & Sourcing
•   Procurement categories (shared)
•   Vendor master (global address book)
•   Approved vendor lists
•   Purchasing policies

5. Product Information Management
•   Released products
•   Product masters
•   Units of measure
•   Product categories
•   Product attributes

6. Inventory Management
•   Item model groups
•   Inventory dimensions (site/warehouse are legal entity specific, but structure is shared)
•   Tracking dimensions

7. Commerce / Retail
•   Retail channels
•   Retail product hierarchy
•   Assortments
•   Price groups
•   Discount definitions
•   Loyalty programs
•   Channel configuration
•   Payment methods (partially shared)

8. Project Management & Accounting
•   Project categories
•   Category groups
•   Billing rules templates

9. Human Resources
•   Workers
•   Positions
•   Organization hierarchies

If this helped, please mark it as "Verified" for others facing the same issue.
Keep in mind that it is possible to mark more than one answer as verified.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 304,908 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi MYGz,

In addition to your list, the next items are global as well:

Currencies, Exchange rate types and exchange rates

Address formats, Countries, Counties, States, Postal/Zip codes, Cities

Global address book, including addresses and contacts

Purchase requisitions

Fiscal calendars

Note that accounting entries are also stored in global tables, but the entries are separated by the Ledger field, representing the legal entity.

In case you are considering a new environment or use the existing one, note that you can separate data using Extensible Data Security (XDS).

About your side question: yes you can loop the menu structure and generate a list of menu items with the full path with X++ coding. I don't have an example available to share with you.

Was this reply helpful? Yes No
Suggested answer

AbdulSyed 9 on at

Like (1)

Report
Copy link

Link copied!
Great question and excellent list from Abhilash!

To add a few more global/shared forms that are often overlooked, especially in multi-legal-entity setups with Commerce:

10. General Ledger

Ledger calendars (fiscal year/period setup — shared structure, assigned per LE)

Allocation terms & rules

Journal names (worth noting: these are LE-specific but often duplicated — a common migration pain point)

11. Tax

Sales tax codes

Sales tax groups

Item sales tax groups

Withholding tax codes
(Note: Tax codes themselves are LE-specific, but the configuration pattern is replicated — important to flag during scoping)

12. Cash & Bank Management

Bank transaction types

Bank transaction groups

Check layouts

13. Fixed Assets

Fixed asset groups

Depreciation profiles

Value models/books
(These are LE-specific but the setup templates are usually globally designed)

14. Credit & Collections

Customer pools

Collection letter sequences

Aging period definitions

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On your two options (same env vs. new env):

From my experience, the decision often comes down to:

Same environment → faster go-live, shared master data immediately available, but higher risk of data contamination and governance complexity (especially with Commerce channel config)

New environment → cleaner separation, better for different regional compliance requirements (e.g. DACH vs. GCC), but duplicated licensing/infra cost and data sync overhead

For a full Commerce setup, I'd lean toward same environment with strict data governance — Commerce retail channels, product hierarchies, and price groups are global and reusable.

Was this reply helpful? Yes No