RE: How do I book Multiple Resources to a Single Workorder as a group in Dynamics 365 Field Service Manager
Of cource you can do that. However it was not really intuitive to use since it was still called Field One Sky. But in the end it works pretty nicely.
1. go into Resource, create a new Resource as Resource Group by naming it i.e. "test group", set Resource Type to Group.
2. within this Resource Group Record go to Submenu=>"Resource Groups (Parent)".
3. Add a record there and substitute the already filled "Child Resource" with the person/Resource you want to be member of this Resource Group. Name the intermediate record however you want. Add the time frame for which this Resource shall be member of this Group.
4. Repeat step 3 as many times as you want to have Members in your Group.
Alternatively you can add a Subgrid to the Resource form (maybe in a closed tab) by using the View "Bookable Resource Groups (Parent Resource)" and label it i.e. "Resource Group Members".
Now if you go to the Schedule Board, one strange thing I identified is, you cannot simly extend the filter criteria on the default filter to also display Groups, but what you can do is: click "Options" on the upper left side and choose "Select Resources". There you can choose your Resource Group (and for this showcase also the Group Members).
Now drag and drop a Resource Requirement from the list on the bottom of the Scheduling Board onto the Resource Group. You will recognize it gets scheduled for all the Group Members automatically as well.
Also if one of the Resources changes its Booking Status, all other Booking Statuses of the Group Members (including the Group Booking itself) inherits this new Booking Status.
So my recommendation is: rename some of the fields and add the members subgrid (maybe add a javascript that the member subgrid gets displayed only if Resource type is "Group"). And play around a bit with this feature.
It was also recommended to only use Respource Groups when they have the character of a longer living time. If you're looking for Groups who only work together occassionaly, it might bemore efficient to Schedule every Resource separately than creating Resource Groups.