Dynamics Community Forum Thread Details

Error in Generate Work Order for multiple Booking Dates

Since the last update there has been a chance to Generate Work Orders manually to multiple booking dates in Agreement Booking Dates view. Today when i have a chance to test function out there was an error:

Script Error

One of the scripts for this record has caused an error. For more details, download the log file.

TypeError: i.getControl is not a function
at t.CreateGenerateWODialog (testtesttest.crm4.dynamics.com/.../FieldService.AgreementBookingDate.js:13:64842)
at Sp.executeFunction (testtesttest.crm4.dynamics.com/.../app.js
at Sp.execute (testtesttest.crm4.dynamics.com/.../app.js
at _.forEach.e (testtesttest.crm4.dynamics.com/.../app.js
at Array.forEach (<anonymous>)
at Promise.all.then.e (https://testtesttest.crm4.dynamics.com/uclient/scripts/app.js?v=1.3.2493-191119-195952:3408:2966)

If no matter how many records i select before clicking Generate Work Order button but if i open single record in a Form and the click Generate Work Order button it works fine.

Any thoughts how to fix this? Thanks!

Hi Cavtg,

We have reviewed the reported scenario on our trial environment and able to replicate the same issue while using “Generate Work Order Button” on multiple Agreement Booking Date. The workflow “Field Service - Generate Work Order for Agreement Booking Date” workflow is getting failed in the case of multiple Agreement Booking Dates. And on our trial environment has “Field Service Trial 8.8.7.*” installed on it.

Please refer below screenshot,

But when we tried the same scenario on our licensed instance (i.e. on our production instance), then it has generated Work Orders for multiple Agreement Booking Dates. And our Licensed Instance has “Field Service 8.8.6.*” installed on it. Hence the functionality of “Generate Work Order Button” is working correctly on the multiple Agreement Booking Dates in “Field Service v8.8.6.*” (which is not a trial).

So we recommend you to try this scenario on the licensed instance and if you still face the same issue on licensed instance then you will need to open a Microsoft Support Case for the same.

Hope this helps.

Thanks!

Quick Links