As part of the April 2020 wave 1 release for Dynamics 365 Field Service you can now have dependent requirements and these can be scheduled in sequence using RSO (Yes this feature is not available for manual or any bookings done using schedule assistant).
You can define relationship between requirements using the successor relationship of a resource requirement
Once you define the the relationship between the requirements and run RSO, RSO is going to schedule the requirements in sequence and the same would reflect on the schedule board too. This is how it’s going to look like on the schedule board:
If you are trying to connect to your Field service instance using the FS mobile app you need to first setup the Field service mobile configuration tool (a.k.a. woodford) , install the Default base mobile template project and then derive a customizations project which would hold your Mobile customizations.
This can be setup following the guide on Microsoft docs:
But even after following the guide if you try connecting to FS mobile, you may end up getting few errors.
Your organization has not created a Bookable Resource for your account and set it to be “Enabled for Field service Mobile”
The issue here is that if you want to access FS mobile app, your user account should have a corresponding Bookable Resource with “Enabled for Field service Mobile” flag checked.
Here I have created a Bookable resource and enabled it for FS mobile:
Once you setup the Bookable resource, try to connect to FS mobile app again, you may get another error message:
Your organization needs to configure Field Service Mobile. There may not be a published mobile project or the mobile project is not configured for a security role assigned to you.
If you remember while setting up the FS Mobile project in woodford, the project was enabled for Field Service related Security roles, you need to make sure the User trying to login to the FS mobile app has at least one of those security roles. Once you give FS related security role to the user you should be able to access FS mobile app.
I have used Preferred Resource for Accounts in Field services a lot many times, which basically means that you can configure if the customer has some preferred resources and it helps the dispatcher to schedule those resources (if available) for a better customer experience.
Recently I came across how to configure if the customer doesn’t want a Resource to be allocated for their work orders.
How we do it is using the same Resource Preferences records but instead of choosing “Preferred ” preference type we use “Restricted”.
As you might know starting Field service V7.5.5.x, the Field service related entities are just available from the UCI app not the standard UI.
During the initial usage of the new interface, I have jotted down few of the benefits I see from usage perspective which I am going to document here in this article:
Behaviour of the app when there’s an issue with Internet
I haven’t seen anybody talking about this as a feature but I as a user felt really good when the UI tells me that there is issue with Network rather than just not showing anything :-), a more app like behaviour.
Streamlined Navigation – Just seeing entities which are relevant to the User
As the app focuses on just one thing so there’s less clutter and less questions raised by Users on what do you mean by this when all they are using is Field services
Will add more findings here as I see more happy faces using UCI 🙂
One of our customers had a requirement where they want a booking to be scheduled only at the start of an hour i.e. a booking can be scheduled at 2PM or 3PM but not at 2:30 PM.
On searching for a solution, we found out a very easy OOB solution which is called Time resolution.
It’s a setting on the schedule board which allows the booking to be created in an interval of minutes (1 to 60). Once we set this to 60, the User would just see 1PM, 2PM etc while dragging and dropping the Resource requirement on the schedule board.
Now this is going to just restrict the booking when dragged and dropped on the schedule board.
We also created booking rules to put some additional checks which work on the schedule board and finally a plugin on create of a booking which takes care if booking is created manually.
I recently installed Field service in a new Trial instance to play with the new UCI interface and the Microsoft Field Service Mobile app.
There’s definitely a learning curve moving from standard UI which has Field services related menu items in the same sitemap but with the new Field service version, Field service related entities can only be accessed from the UCI app. See below screenshot on how to access the APP:
Now, once you click on the app, you can change the area from the bottom in order to configure FS (the Settings area)
I think it’s more confusing if you have used Field service 7.x with standard UI. Once you browse the settings area, you will quickly realize that the Scheduling settings like Scheduling parameters (to enable maps) are missing. The FS settings area looks like this:
In order to access scheduling related configuration settings, there’s another App called (Universal Resource Scheduling) which now sits outside Field services and can be accessed in the following manner:
Once you are in the Universal Resource Scheduling app, you can access the Settings area from the “change Area” dropdown at the bottom and then you will see all Scheduling related configuration settings.
On the Insider home page, search for a program with the name “Opt-in to Upgrade Project and Field Service – Unified Interface.”
Click that program link in the search results and choose to “Join Now” in the page that opens. This will add you as a participant to the program.
On the program page, access the link provided to sign up: “Signup Link to opt-in for the latest Field & Project Service UCI Release (GA)”
The link will open a simple questionnaire and one of the questions is the instance URL; please provide the URL of the instance.
Microsoft will receive the details you provide and, within a few days, will enable the install or upgrade of the latest versions of Field and Project Service on the instance that you provided. Once enabled, you will receive a confirmation email from Microsoft.
Once you receive the email, you can access your Dynamics 365 Admin portal to install or upgrade Field Service and/or Project Service Automation on the enabled instance.
For any questions and discussion on the functionality, please use the Forum on the program page. Use the Microsoft Support process to log any issues/bugs.
If the identified instance has both Field and Project Service installed, please plan to upgrade both solutions before resuming normal use of the instance.
For a smooth install experience, please make sure that the identified instance meets all the prerequisites listed on the Insider Program page.
These releases of Field and Project Service will only be available for install or upgrade on the identified instances. They will not show up for any other orgs, even if they are on the same tenant.
As we know the Microsoft Field service app has offline capability but there are few design decisions that can help you and your customers in long run.
One important aspect is to decide upon the sync filters which drive what data is available for Users while they work in offline mode.
In this post I would be focussing on Sync filter for Customer assets and it becomes even more important if your customer has a lot of Assets in the field.
Deciding upon sync filters should be a continuous improving/ agile process rather than spending time on thinking the best solution for the very first time.
Here was our Sync filter journey for Customer assets:
We started with No sync filter. This is because we weren’t sure how many assets would the customer have/create over the period
Next step was to at least filter out inactive assets
Now when the asset number started growing, we deciding upon just showing the Assemblies which are nothing but Asset containers at each site. This worked for a while but then technicians had no insight when at a site that this assembly had what assets.
We finalised upon showing all Assets (Parent/ Child) in the territories that the User works in. This was great, now the User could see every asset that he/she deals with.
After a while this also starting blowing apart as few Users were catering to multiple territories and by default there’s a hard limit of 10000 records that you can sync for an entity in offline mode.
The business then decided to re do their territories and create new territories for overlapping areas.
The point here is that no one solution will fit all customers and solution for today may become obsolete tomorrow.
One good thing with woodford sync filters is that we can use fetchxml to build them,
Here’s the sync filter fetch xml we finalised upon:
If your customer has D365 FS licenses and you were using Woodford solution to customize the Microsoft FS mobile app or Resco FS app, the woodford trial would eventually expire after a period of 30 days.
However for each D365 FS license you can activate a FS mobile app license as well, how to do it is explained in detail on the following URL: