Applies to Product -Dynamics 365 Project Operations
What’s happening?
The msdyn_SaveCalendar action is not consistently setting the Resource Calendar Working Hours, particularly when processing multiple weeks in succession.
Reason:
The msdyn_SaveCalendar function is not designed to handle concurrent updates on the same resource due to complex validation processes. When actions time out, it can lead to improper setting of the calendar if multiple timeouts occur in a row.
Resolution:
- It is recommended to avoid concurrent updates on the same resource when using the msdyn_SaveCalendar function.
- For repetitive patterns, utilize weekly or daily recurrences to reduce the number of entries.
- If processing for an extended period (e.g., several years), break down the flow to act per bookable resource and per year, implementing a delay of 2 hours between processing each year. This allows time for any actions that may time out to finish processing in the background.