Dynamics Community Forum Thread Details

Field Service: Work Order Sharing / Unsharing workflow

There is a Field Service workflow which handles the sharing and unsharing of work order records with who is ever booked on the work order.

I have scenerio where schedulers will 2 bookings to a work order.

Bookable Resource of type = User
Bookable Resource of type = Account

I need the 'Bookable Resource of type = User' to see the Account booking on the mobile. This works when the scheduler books the Account booking first before the User (The Account booking will be shared with the User who gets booked second), but if the User gets booked first and then the Account gets booked second then the Account booking doesnt get shared to the User.

Is this a bug in the workflow or is this by design? Our security model is built so that Field Resources need user owned permissions of the booking, so we are not looking into changing the business unti levels.

Based on the scenario that you outlined it is not a "bug" but the order of operations that you are performing and how the plug in works. So if you assume that the plug-in is called each time there is a "Share" that is performed this will allow for the inspection of the state that the Work Order is in (recall that you are sharing the Work Order).

In the first case the WO --Booking--> Account, this triggers the Sharing and (for the fact that the Account has the ResourceBooking against the WO, will make the WO (of which the ResourceBooking is a record and that caused the sharing) to now share what the WO has with the Account.

Then if you add the ResourceBooking for the User, the same thing happens as outlined above, but for the User.

Since the Account ResourceBooking was in place when the Share triggered, the User now see the Account ResourceBooking as it is a member record (of the WO as the Parent).

In the non-working case you have the User ResrouceBooking triggering the Share - when NO Account relationship is in place. So the system is NOT going back and "re-sharing" in a cascade style, all the prior item as it would create a very large spider web of changes/sharing.

So the order is what is key.

If you did want to just make this work, you would have to write you own Plug in (C#) to walk JUST the Accounts + Users and share again the ResourceBooking (only) to make it efficient.

Quick Links