web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Service | Customer Service, Contact Center, Fie... / Script Error with Work...
Service | Customer Service, Contact Center, Fie...
Answered

Script Error with Workorder form after field service version upgrade

(0) ShareShare
ReportReport
Posted on by ACECORP 1,589

We recently upgraded field services to the latest version.

Upon doing that, every user (including administrators) gets a script error when opening the work order form.

FSWOScriptError.png

We disabled our own custom scripts to see if there is some kind of conflict, but even with all our custom scripts disabled, and only the three Microsoft native scripts enabled, the error still occurs.

We are using the 1.0.0.0 version of the Work Order form because that is where all our custom fields and logic exists.

Screen-Shot-2020_2D00_07_2D00_02-at-2.40.33-PM.png

You can see in the screen shot below that we disabled the only script we had that is custom.

WoForm.png

Having done that, can anyone suggest why we might be getting errors with the Microsoft native scripts on an OOB form?

The script error details are not helpful and only show the following:

Library.Load@https://cpptest.crm.dynamics.com/{637293112980018647}/WebResources/msdyn_/WorkOrder/WorkOrder.Library.js?ver=1243022576:34:21
@https://cpptest.crm.dynamics.com/form/ClientApiWrapper.aspx?ver=1243022576 line 160 > eval:1:20
RunHandlerInternal@https://cpptest.crm.dynamics.com/form/ClientApiWrapper.aspx?ver=1243022576:160:1
RunHandlers@https://cpptest.crm.dynamics.com/form/ClientApiWrapper.aspx?ver=1243022576:118:19
OnScriptTagLoaded@https://cpptest.crm.dynamics.com/form/ClientApiWrapper.aspx?ver=1243022576:275:1
AppendScriptTag/scriptTag.onload/

I have the same question (0)
  • Verified answer
    kunihih Profile Picture
    kunihih Microsoft Employee on at

    It appears that the WorkOrder.Library.js web resource has been modified by the customer and this is blocking the newest changes made to this web resource via the update from surfacing. This in its turn may be the cause of this error.

    Go to Settings - Customizations - Customize the System - Web Resources.

    Search for WorkOrder.Library.js and select Solution Layers

    You will see a Active layer of customizations above the OOB updates to this web resource.

    Click "..." and then "Remove Active Customizations" to remove the changes made by the customer to this file.

    This should allow the OOB web resource changes to surface and this may alleviate the error.

    That said I recommend that you speak to the customer to see if changes to this file were intentional before removing the customizations. Also consider raising a ticket with Microsoft so that they can help with a more thorough investigation.

  • ACECORP Profile Picture
    ACECORP 1,589 on at

    To my knowledge, OOB JavaScript files were never modified or customized. We created new/different javascript files to hold customizations. However, I will check into this on Monday to see if somehow this OOB JavaScript file was inadvertently customized.

  • ACECORP Profile Picture
    ACECORP 1,589 on at

    I see it. There is an "Active" entry and the "Remove Active Customizations" is present. I will back up the current JavaScript file in case of an issue, and then I will remove the Active Customizations as suggested. I will report back with the results once I have them.

    Screen-Shot-2020_2D00_07_2D00_06-at-10.07.46-AM.png

  • ACECORP Profile Picture
    ACECORP 1,589 on at

    That was successful. Thank you very much! Now I just need to figure out what was present in that script that we "lost" and figure out how to "restore the functionality" via another script, but that should be the easy part. Thank you again for your help.

  • ACECORP Profile Picture
    ACECORP 1,589 on at

    Completed the analysis. Nothing was lost, the FS Update appears to have created several redundant entries in the script, basically re-writing some things that were written differently but did not remove or replace the original OOB code.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
FSRon Profile Picture

FSRon 61

#2
James White Profile Picture

James White 21

#3
AT-28040446-0 Profile Picture

AT-28040446-0 20

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans