{"id":30442,"date":"2022-01-25T15:53:55","date_gmt":"2022-01-25T10:23:55","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=30442"},"modified":"2023-01-13T12:58:30","modified_gmt":"2023-01-13T07:28:30","slug":"execute-js-within-rules-on-the-field-service-mobile-for-dynamics-365-field-service","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2022\/01\/execute-js-within-rules-on-the-field-service-mobile-for-dynamics-365-field-service\/","title":{"rendered":"Execute JS within rules on the Field Service Mobile for Dynamics 365 Field Service"},"content":{"rendered":"

Introduction:<\/strong><\/h2>\n

Field Service technicians use Field Service Mobile application which provides brief information related to the Work Order, Booking and Service location. And, Woodford application allows us to help customize the Field Service Mobile application based on the business requirements for each organization.<\/p>\n

Woodford customization application provide various ways to automate process so that technician can easily complete their tasks at the service location. For example, custom buttons on the forms\/views, using JavaScript on the forms\/views, On load\/On Change\/On Save rules etc. With latest Woodford solution version 14.2.0, we are now able to execute the JavaScript function within Rules on the form by \u201cExecute JS<\/strong>\u201d feature.<\/p>\n

Previously we were required to develop the JavaScript to execute the functionalities for On Change\/On Load etc. event using \u201cMobileCRM.UI.EntityForm.onChange<\/strong>\u201d functions, which further includes the code for the logic to achieve specific requirement. However, using ExecuteJS<\/strong> function we can eliminate the code for \u201cMobileCRM.UI.EntityForm.onChange<\/strong>\u201d and reuse the simple JavaScript functions within On load\/On change rules directly.<\/p>\n

We can add the Rules on the forms in order to automatically populate default values, hide show fields, update record values etc. But previously it was difficult to add complicated logic within Rules on the forms. Now as we have an option to execute the JS function from Rules we are not supposed to add additional Iframe on the Form in order execute JavaScript functionality.<\/p>\n

Now, let\u2019s consider an example where user wants to schedule an appointment for particular Account from the Field Service Mobile application by single change on the Account form. To achieve this requirement using the Execute JS feature within the Rules on the Form, follow the steps given below:<\/p>\n

1<\/strong>. On Booking, add \u201cSchedule Appointment?<\/strong>\u201d, \u201cNext Appointment Date<\/strong>\u201d, \u201cNext Appointment End Date<\/strong>” custom fields which will be used to create a new Appointment record.<\/p>\n

2<\/strong>. Open Woodford mobile project and navigate to the Bookable Resource Booking entity form and add these fields on the same so that technician can have access to the functionality within Field Service Mobile as shown in the below screenshot:<\/p>\n

\"Field<\/p>\n

3<\/strong>. On change of Schedule Appointment field value as Yes, we need to trigger a JavaScript function, which will create an Appointment record. So, will create the Iframe, JavaScript Library with below code to create an appointment and add these files in the Offline HTML.<\/p>\n

function ScheduleAppointment() {\r\ntry {\r\n\r\nMobileCRM.UI.EntityForm.requestObject(\r\n\r\nfunction (entityForm) {\r\n\r\nvar BookingEn = entityForm.entity;\r\n\r\nif (BookingEn == null || BookingEn.properties == null)\r\n\r\nreturn;\r\n\r\nvar AppointmentRequired = BookingEn.properties.new_scheduleappointment;\r\n\r\nvar WorkOrderRef = BookingEn.properties.msdyn_workorder;\r\n\r\nif (!AppointmentRequired) return;\r\n\r\n\/\/create appointment record with Service Account\r\n\r\nvar appointmentRec = new MobileCRM.DynamicEntity.createNew(\"appointment\");\r\n\r\nappointmentRec.properties.subject = \"Appointment For \" + WorkOrderRef.primaryName;\r\n\r\nappointmentRec.properties.regardingobjectid = new\u00a0 MobileCRM.Reference(BookingEn.entityName, BookingEn.id);\r\n\r\nappointmentRec.properties.scheduledstart = BookingEn.properties.new_nextappointmentdate;\r\n\r\nappointmentRec.properties.scheduledend = BookingEn.properties.new_nextappointmentenddate;\r\n\r\nappointmentRec.save(\r\n\r\nfunction (err) {\r\n\r\nif (err)\r\n\r\nMobileCRM.bridge.alert(err);\r\n\r\nelse {\r\n\r\nMobileCRM.bridge.alert(\"Appointment Scheduled Successfully...\");\r\n\r\n}\r\n\r\n}\r\n\r\n);\r\n\r\n},\r\n\r\n);\r\n\r\n}\r\n\r\ncatch (err) {\r\n\r\nMobileCRM.bridge.alert(err);\r\n\r\n}\r\n\r\n}\r\n<\/pre>\n
\"Field<\/p>\n
4<\/strong>. Now add the Iframe on the Booking form using \u201cAdd Iframe<\/strong>\u201d button within mobile app project as shown in the below screenshot:<\/p>\n
\"Field<\/p>\n
5<\/strong>. Now this functionality can be triggered on change of \u201cSchedule appointment<\/strong>\u201d field on the Booking record by adding the resco rules with ExecuteJS<\/strong> function by mentioning the tab and function Name from the script.<\/p>\n
Please refer below screenshot for the same.<\/p>\n
\"Field<\/p>\n
6<\/strong>. Next, save the changes and publish the customizations of the mobile project.<\/p>\n
7<\/strong>. Technician can now open the Field Service Mobile app, navigate to the Booking Record, fill the Next Appointment Date<\/strong>, Next Appointment End Date <\/strong>and change the Schedule Appointment as Yes. This will create the appointment record with below listed details.<\/p>\n