BeyondERP.Newsletter
Menu

Setup page · Human resources

Department hierarchy

A hierarchy designer page that shows departments in their organisational structure and lets you add departments to it.

Used by
Chief executive officer, Human resource manager, Payroll administrator and 1 more role
Business process
Develop people strategy
Menu item
HcmDepartmentHierarchy
Main table
TmpHierarchyDesigner
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA hierarchy designer page that shows departments in their organisational structure and lets you add departments to it.
What you do hereUse this page to add departments to the department hierarchy and publish the changes with an effective date.
ExampleFor example, BEAT inserts the new department Project billing under Finance in December 2026, saves a draft, and publishes it with effective date January 1, 2027, so the hierarchy shows it only from that date.
Department hierarchy page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processDevelop people strategy
Menu pathHuman resources › Departments › Department hierarchy
Set up firstDepartments Microsoft Learn
Used next byAll positions (Department) Microsoft Learn People by department report Microsoft Learn
Related pagesOrganization hierarchies Microsoft Learn
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Set up Department hierarchy

Use this page to add departments to the department hierarchy and publish the changes with an effective date.

Steps from Microsoft

  1. Go to Human resources > Departments > Department hierarchy.
  2. Select Edit, and then select the organization that the department should be under.
  3. Select Insert, and select Department in the list.
  4. Select the department to add to the hierarchy.
  5. Save your changes as a draft.
  6. Select Publish and enter an effective date.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Effective dateThe date and time the published changes take effect; it can be in the future.Microsoft Learn 1/1/2027 00:00
Describe changesA note on what the publish changes.Microsoft Learn Add Project billing under Finance

Common errors and fixes

MessageWhat to do
A department added today doesn't show in the hierarchyThe change is still a draft, or it was published with a future effective date. Publish the draft, or view the hierarchy as of the effective date. Microsoft Learn
A department can't be found in Insert > DepartmentIt doesn't exist yet. Create it on the Departments page first. Microsoft Learn

Test checklist

  1. Select Edit, select the parent organization, then Insert > Department and pick a department.
  2. Save and check the message that a draft version was created.
  3. Publish with a future effective date and check the department is not in the hierarchy as of today.
  4. View the hierarchy as of the effective date and check the department appears.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Department hierarchyMake changes in draft, then Publish with an effective date; use a future effective date for planned restructuresSaving creates a draft; Publish applies the changes on the effective date you enter, which can be in the future, for example the first day of the next year.How are department changes published?Letting many users edit the published hierarchy in production. Microsoft recommends limiting who can add or remove organizations, because mistakes are costly to correct.Test: Future-dated department hierarchy change

Feature management and licence

Licence or add-inOn BEAT the page is run by Human resource manager, Payroll administrator, Payroll manager and Chief executive officer; the full list is under the page's security roles. No Feature management feature is needed for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyShared: departments are operating units, which Data management lists as shared, so the department hierarchy is the same in every legal entity. Checked in Dynamics 365
Can it be undoneHard to reverse: Published changes take effect on their effective date. To undo, edit in draft and publish again; plan restructures with effective dates and draft mode first. Microsoft Learn
If you change it laterPublished changes take effect on the effective date entered, which can be in the future. Microsoft Learn
Technical architect

6Technical

Menu itemHcmDepartmentHierarchy Checked in Dynamics 365
FormHierarchyDesigner Checked in Dynamics 365
TableTmpHierarchyDesignerShown as “TMPHIERARCHYDESIGNER” in Record infoChecked in Dynamics 365
Who can open itPrivilegesPlace holder menu item OMPlaceHolderItemMaintainExt OMPlaceHolderItemViewExtDutiesReview organizational information HcmOrganizationalReviewView organizational information HcmOrganizationalView
4 security rolesChief executive officer CompanyChiefExecutiveOfficerHuman resource manager HcmHumanResourceManagerPayroll administrator HcmPayrollAdministratorPayroll manager HcmPayrollManager
Checked in Dynamics 365
Roles to set it up and use itTo use itHuman resource manager HcmHumanResourceManagerPayroll administrator HcmPayrollAdministratorPayroll manager HcmPayrollManagerChief executive officer CompanyChiefExecutiveOfficerGive people one of these roles. On this system, 4 roles can run this page.Checked in Dynamics 365
Actions on the page(Action Pane without tabs): Hierarchy details, Organization details, Purposes, Hide or show preview paneChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=HcmDepartmentHierarchy
Data migrationLoad order: Departments load with the Operating unit entity; the hierarchy is then published from the hierarchy designer in each environment, with the go-live date as effective date.Load first: OMOperatingUnitEntityMicrosoft Learn
Everyone

8Sources