BeyondERP.Newsletter
Menu

Job page · Project management and accounting

Synchronize resource calendars capacity across all companies

A periodic job that fills the capacity hours of the calendars linked to resources, for all companies, into the ResCalendarCapacity table used to calculate resource availability.

Business process
Plan projects
Menu item
action:ResCalendarCapacitySynchronizationBatch
Main table
ResCalendarCapacity
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 periodic job that fills the capacity hours of the calendars linked to resources, for all companies, into the ResCalendarCapacity table used to calculate resource availability.
What you do hereUse it after turning on the resource scheduling performance feature, after any calendar change, and before scheduling beyond the last end date.
ExampleBEAT's calendar capacity is built to 12/31/2026. Before planning PRJ-0042 for 2027, the resource manager runs the job from 01/01/2027 to 12/31/2027 with Remove existing capacity records = No, so 2027 shows 8.00 hours per working day.
Synchronize resource calendars capacity across all companies 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 processPlan projects
Menu pathProject management and accounting › Periodic › Project resources › Synchronize resource calendars capacity across all companies
Set up firstCalendars Microsoft Learn
Used next byResource availability Microsoft Learn
Related pagesPopulate project resources across all companies 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.

When to run it

When to run itAfter the feature is turned on, after calendar changes (for example a new holiday), and before scheduling past the last end date.
How oftenAfter calendar changes and at least once a year to extend the end date.
Batch settingsRun as a batch job in one legal entity; it covers all companies.
What the output showsCapacity hours per resource calendar for the date range in ResCalendarCapacity.

Source: Microsoft Learn

Setup steps on this page

Keep calendar capacity built ahead

Make resource availability correct for future dates.

Steps from Microsoft

  1. Go to Project management and accounting > Periodic > Project resources > Synchronize resource calendars capacity across all companies.
  2. Set Remove existing capacity records to Yes to rebuild, or No to add a new date range.
  3. Select a Period code, or enter a start and end date beyond the furthest date you plan to schedule.
  4. Run it in one legal entity only; it fills the capacity for all companies.
  5. Open Resource availability for a resource with a recent calendar change and check the hours.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Remove existing capacity recordsYes removes previous data; No adds incremental data.Microsoft Learn No
Period codeThe period to generate data for; when set, start and end dates aren't needed.Microsoft Learn YEAR-2027
End dateWith the start date, the range to build when no period code is set; set it beyond the furthest scheduling date.Microsoft Learn 12/31/2027

Common errors and fixes

MessageWhat to do
Resources show zero capacity after a certain date.The data only goes up to the last end date; run the job again with a later end date. Microsoft Learn

Test checklist

  1. Check availability in January 2027: 0.00 hours.
  2. Run the job to 12/31/2027 with Remove = No.
  3. Availability shows 8.00 hours per working day in January 2027.
  4. December 2026 values are unchanged.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Keep calendar capacity built aheadRun yearly with an end date 12 months beyond the furthest planned work, and after every calendar change.Capacity only exists up to the end date of the last run.Rebuild or extend?Forgetting to extend the end date, so new projects show no capacity.Test: Extend capacity into next year

Feature management and licence

Feature to turn onEnable project resource scheduling performance enhancement feature
Licence or add-inOn the live system, Project manager and Resource manager use this page. Learn: run it after turning on Enable project resource scheduling performance enhancement feature (on by default from 10.0.36).

Microsoft Learn

Solution architect

5Design impact

Shared or per companyCross-company: run in one legal entity, it distributes capacity data to all companies. Microsoft Learn
Can it be undoneYes, by rerunning: Run again with Remove existing capacity records set to Yes to rebuild the data. Microsoft Learn
If you change it laterBuilds capacity only up to the end date; scheduling past it shows no capacity until the job runs again. Microsoft Learn
Technical architect

6Technical

Menu itemaction:ResCalendarCapacitySynchronizationBatch Checked in Dynamics 365
FormDialog Checked in Dynamics 365
TableResCalendarCapacityChecked in Dynamics 365
Roles to set it up and use itTo use itProject manager ProjProjectManagerResource manager ProjResourceManagerGive people one of these roles. On this system, 2 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:ResCalendarCapacitySynchronizationBatch
Data migrationLoad order: Synchronize resource calendars capacity across all companies has no data entity in Data management: it is a periodic job and keeps no records of its own. Migrate calendars and resources, then run the job in the target system.Microsoft Learn
Everyone

8Sources