It’s good to think of the D365 Resource Scheduler as the resource engine that is used to power the following D365 Apps:
- D365 Customer Service
- D365 Field Service
- D365 Project Service Automation ((known as PSA)
So how does this actual work in practise. At a very basic level D365 Resource Scheduling allows a user to react to ‘Resource Requirements‘ that have been generated from within the 3 Apps mentioned above.
Inside D365 Resource Scheduling we store the following types of data:
- Roles (Resource Categories) /Skills
- Schedule Board
You will see that the ‘schedule board’ is surfaced also directly within the 3 apps – and its from this you can see resources and make bookings. So although you may well be looking at D365 Customer Service – the actual work is being done by D365 Resource Scheduling.
The result is a new record that you will see under the Bookings section of D365 Resource Scheduler, as a ‘Bookable Resource Booking’. This combines data from the D365 App record such as pricing, and combines it with the resource data from the D365 Resource Schedule
Enable a Custom Data Entity for use with Resource Scheduling
There are some straight forward steps you need to go through to enable the use of the D365 Resource Scheduler with any CDS Data Entity. However there are some mandatory fields that entity needs to have:
- Start Date
- End Date
- Work Location
The CDS Data Entity will also need to have some relationships setup on the entity.
Then inside D365 Resource Scheduling you will need to enable resource scheduling for that entity:
As I learn more about this I will start to add more posts and explain what I have learnt.