Welcome to our blog where will be sharing tip, tricks and detailed walk-throughs covering all areas of Dynamics 365 but primarily focused on the Field Service and Project Service Apps, Scheduling and integration using Microsoft Flow and the Common Data Service (CDS). We hope you find the blog posts useful and please feel free to comment if you would like us to elaborate on any particular area. 

  • Tash

Schedule Types - create a new entity relationship

Updated: May 13, 2018

As standard, Dynamics 365 enables scheduling off Project and Work Orders.

Tab Settings - Schedule Types

The following outlines the steps to make another entity available for scheduling.

1. Navigate to Resource Scheduling > Administration

Resource Scheduling - Administration

2. Select Enable Resource Scheduling for Entities.

Enable Resource Scheduling for Entities

3. Setup Wizard will appear to enable an entity relationship.

Setup Wizard

In this example, we are going to enable Opportunity entity for scheduling. From the wizard screen you can select the entity enabled for scheduling and through the wizard create the relationship to booking and requirement. If you create this relationship through the wizard, the lookup will have the prefix new_. I do not like creating fields or relationships with this standard prefix; I always create the relationships first through the Dynamics 365 configuration tool. The model needs to be built up as follows.


4. Once these 'to many relationships' are created off opportunity to Resource Requirement and Bookable Resource Booking, the Setup Wizard can be completed for enabling Opportunity for scheduling.

Enable New Entity for Resource Scheduling

5. On selection of Publish Customization the Booking Setup form will be displayed.

Booking Setup Metadata

A - Booking Status Field Logical Name

This field is important as it controls the status a booking will go through. This means the booking status can change between Work Order, Project and Opportunity. If this field is left blank, the default booking status will be used for the entity.

As standard, Work Order and Project come with the following status:

Work orders Scheduled > Traveling > In Progress> On Break> In Progress > Complete. Or some derivative of that.

Projects Proposed > Committed > Complete

In this example, I want to set opportunity up with the following status.

Opportunity: Scheduled > In Progress > Complete

To enforce this Opportunity Booking Status, an Opportunity Status option set field needs to be created against Booking Status entity. This field's logical name can then be referenced in Booking Status Field Logical Name.

Booking Status Field Logical Name

B - Default Booking Duration. When a booking is created, if you are not driving the booking duration off fields from the base entity, the booking duration can be defaulted. Perhaps you are scheduling sales calls and estimate all of them as 15 min calls.

C - Default Booking Committed Status

H - Default Booking Canceled Status

These control default status off the Bookable Resource Booking entity when a booking is committed or canceled. In our opportunity example, Committed = Scheduled and Cancelled = Cancelled. These values do not need to be populated and if there is another rule in the system determining the booking status they will be ignored.

D - Default Requirement Active Status

E - Default Requirement Canceled Status

J - Default Requirement Completed Status

F - Resource Availability Retrieval Limit. This controls for this entity the maximum number of resources to retrieve and show in the schedule assistant. Let's say you have a large resource pool and you are manually scheduling these bookings, you could impose a limit so that only 3 resources are displayed for selection. This is a good feature if someone is ever scheduling on the phone with a customer and does not want to be bombarded with too many options.

G - Cancel Booking When Moving. When moving a booking on the schedule board, the booking record can be either updated and moved or the booking deleted and a new record created.

I - Disable Requirement Auto Creation. This is an important control, as this will determine if on creation of the entity the requirements are automatically created.

L-Default Scheduling Method. This will control if by default the entity is available for RSO (Resource Scheduling Optimisation) or not. NOTE: even if Resource Scheduling Optimization is turned on, the individual booking requirements can be controlled as to whether the individual booking is available for optimisation.

63 views0 comments