Automatic Update Policy for Field Service
The Field Service (FS) solution will enable system-driven, automatic updates, in alignment with other Microsoft announcements that have highlighted the improved update process for Dynamics 365.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
When Work Order loading, following Script error popup. Please help me to solve it
This is the error
Let me guess: it is a custom form?
And that appeared after upgrading from FS 7.x to 8.x?
Problem solved. What I have done (in consultation with MS) is to create a duplicate form (WO-Duplicate) and it seems to be working fine now. So what we need to do is to deactivate old form and use this new one.
Great. May I ask you: was it a duplicate of your customized form or a duplicate of the standard form that came out of the box?
So I had the same issue and the problem arises from duplicating the main work order form from a much older version of Field Service.
Yes we got exactly the same issues and feedback from MS Support. On the one hand it was a lot of work to fix that for all our custom forms and on the other for i.e. the Resource form it did not work for us at all what MS and Thomas describes. So we than took the OOB Resoure form and added all our custom fields and custom scripts manually to it.
Learning for the future: try to use the OOB forms and customize them instead of first replicating them before customizing. Anybody disagrees?
I think what happens is that if you customise the OOB form you may potentially lose what the original form from Microsoft was suppose to be if you customise it too much.
I had an experience where someone removed subgrids on the main product form which then broke some Microsoft functionality we wanted to use in the future. I had to load up a trial to find out what was on that form originally.
I personally would like to get Microsoft's opinion on this for "best practice". I can see that both ways could cause issue in future potentially especially now that Field Service is updating on a near regular bases.
Thank you Thomas for the feedback. I also would appreciate a recommendation or direction from Microsoft for that in order to have better decision criteria when trying to balance advantages against disadvantages case by case.
Duplicate customized form
Business Applications communities