Let’s directly jump into trying that out! So I want to create a Crew out of 3 Resources: one User, one Contact and one Equipment.
Go to Field Service (App)=>Resources(Area)
Let’s create three Resources which you want to be Crew members: a Contact, a User and an Equipment
“+ New” on top of Resource list =>
set Resource Type to Crew; provide a Name to the Crew:
5. in your Resource of Resource Type “Crew” go to “Related”=>Resource’s Children
6. click on “+ New Bookable Resource Group” 7. for the field Child Resource choose the first crew member and also fill in the Name field 8. for From Date and To Date choose the timeframe in which you want this Resource to be member of the crew
9. hit Save&Close and repeat step 6 to 9 for all your 3 crew members
10. now open your Schedule Board. You should see this:
11. you might want to do a right click on your Crew resource and chose “View Crew Resources in Split View
this provides you with an even better perspective:
12. now lets drag and drop one of the Resource Requirements from your Open Requirements list onto the Crew Resource
After the system has finished its job (might take a couple of seconds) you will see this:
If I now move the main tile representing the Booking of the Crew by drag and drop, all Bookings for all the crew members get postponed automatically as well.
In Dynamics 365 Field Service you are able to create these types of Resources:
Resource Type: Equipment
Facility Equipment lookup appears and becomes mandatory after this Resource Type has been chosen.
Organizational Unit lookup becomes read only after this Resource Type has been chosen . Gets pulled from ‘Facility/Equipment’.’Organizational Unit’ or, if this is empty, than from ‘Project Parameters’.’Default Organizational Unit’.
Enabled for Field Service Mobile two option set disappears
in previous versions it was called Company Asset
makes sense to be used in a Resource Crew
for example: Truck, Excavator, Beamer, Hololens
Start Location & End Location cannot be set to Resource Address
Resource Type: Crew
Also see here for further details on how to set up a Crew.
After I have created a copy of an existing form I faced issues that some of the scripting provided by Microsoft didn’t work anymore. As long as I don’t get further insights into this I would recommend to be careful when taking this road. Better maybe to customize the existing form instead of creating a copy of it for customizations. This, by the way, is also a way that has proved to be more stable when it comes to upgrading your org with latest MS solution versions. We faced lots of scripting errors on forms that we previously have copied. It turned out that MS replaced the JS libraries for the original forms but not for your form copies during the last larger upgrade cycle.
Reachable in menu via Settings=> Business Management.
If you’re opening the form from Unified Interface you’ll see the lookup field Organizational Unit on the form.
But if you’re opening it from the former UI you’ll get another lookup field Site instead:
So is Organizational Unit the “newer” replacement for Site (at least when it comes to Field Service?
If you are creating a Bookable Resource with Resource Type Equipment than the Organizational Unit gets automatically populated from Facility/Equipment.’Organizational Unit’ into ‘Bookable Resource’.’Organizational Unit’.
There is a Work Hours ribbon button in Unified Interface:
In the new Unified Interface your surely stumbled already over this new Subgrid layout called “List View”:
This layout will change to the “old” Grid View as soon as you allow the section to have more horizontal space. This can be done by formatting the Form (or simply make your browser window wider).
This mechanism is called “Reflow”.
But did you know that you can also determine whether you want to display the Subgrid List View or the “old” Grid View by deactivating Reflow for a certain Subgrid?
Just open the parent Form in edit mode, double click on the Subgrid => Controls =>Add Control… => choose the “Read Only Grid”.
Than you can edit the property “Reflow behavior” to fix the Grid layout to the one or the other View type.
Another very nice feature is that you can customize the content displayed in the “List View” by creating a Card Form and referencing it in the Control properties (see above).
You would than be able to get something like this:
For that, create a new Form of the Type “Card” and adjust it as to your needs:
Up to now I couldn’t find out how to get the “Color Strip” working. I tried this without success. There is an Idea out there that indicates that it doesn’t work (yet?). So if you know more please let me know.
You can also add more than three columns into the Card’s body and additional fields into the Header and the Footer of the Card Form. To control whether the footer is expanded by default or not go to System Settings => “General” => “Set the default card state for Interactive Dashboards” => “Display cards in expanded state”. Sadly this setting can be done only once system wide.
But still, I’m really exited by the great capability to customize the List View.
If you’re going to enable another (custom or OOB) entity for scheduling there is a great blog series from Sara Lagerquist (see links below) which has some good tips. Based on these tips I’m listing up some of the most valuable insights when it comes to extend URS functionality when you Enable Resource Scheduling for Entities.
don’t create new relationships from within the “Enable Scheduling” setup wizard as they won’t contain your custom prefix in their technical relationship names
think about doing a more sophisticated field mapping by Workflow instead of only using the static field mapping from the wizard
also take into account to leverage the standard field mappings for the newly created relationships to pass on additional parameters which are not exposed as fields in the wizard
don’t forget to maybe auto create Resource Requirements by another Workflow
also you maybe want to auto-populate Resource Requirement Skills / Characteristics for your new Resource Requirements
for only a limited number of Characteristics you might want to create several new Lookup fields on your newly schedulable entity to the Characteristic entity
for a larger number of Characteristics you could use Microsoft Flow to populate them into your Requirement Characteristic entity. Source for this Characteristics list to be picked up by Flow could be a new sub-entity from your newly schedulable entity (NewSchedulableEntity 1:n NewSchedulableEntity.Characteristics). If you want to make Service Tasks schedulable you could alternatively use the Service Task Type and place a new Subgrid “Service Task Type Caracteristics” there.
Say you add the Contact subgrid into your Account form on Field Service Mobile because you’re expecting your Field Agents to also capture new Contacts and they are first searching for the Account first instead of adding the Contacts directly from Home=>Contacts.
Now if you tab on “+” at the top of the Contacts subgrid on the Account form the “New” form for Contacts opens.
And now the difference here is: if you leave the setting from below in its standard configuration as it comes out of the box, your address fields will stay empty so that for the new Contact you have to fill everything in manually.
But if you change the setting “Use Entity & Attribute Map” to “true”, the address fields on a new Contact form are automatically populated from the same fields on the Account form were you had started your journey.
Here is a nice article by Thomas Dayman that gives a short overview of how to embed a Survey Questionnaire created with the new Microsoft Forms Pro into the Field Service Mobile app. The approach is to create an Offline HTML file where Thomas provides a sample code snippet for, and embed that via iFrame into a Form in Woodford.
Compared to Resco’s new Inspections the Forms Pro integration doesn’t support offline scenarios. Resco Inspections comes with additional licence cost whereas for Forms Pro it is still not clear how the licencing will look like.