Bring your code 2 life

While using Field Service there might be the situation where you figure out that the Field Service Status does not fit to the booking status, or the Field Service Status was not provided at all. But if you try to change the Field Service Status field on a booking status record that was already assigned to any resource booking in the system you will usually see this error coming up: If the system only has a handful of resource bookings it can be handled easily in a manual manner by temporarily switching the booking status to another status. But consider any automatic workflows or business process that could be behind any of the status changes. You need to make sure that those will not become triggered by a temporary status change! (E.g. service report generation, etc.) Please note:     Be aware that the booking status on the resource booking affects the system status of the assigned work order. E.g. if all bookings have status completed the work order will ...

Field Service added some new forms to entities like opportunity, quote, order, etc. as well as a JavaScript library running on these forms. Now if you had copied a form based on a FS form then with an earlier version of Field Service you would have received this error everytime you try to save or load a record. TypeError: Cannot read property 'Metadata' of undefined at Object. GetOrderType (https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/msdyn_/SalesDocument/SalesDocumentFormLoader.Library.js:1:5679) at Object.FormApplies (https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/msdyn_/SalesDocument/SalesDocumentFormLoader.Library.js:1:4312) at Object.OnLoad (https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/msdyn_/SalesDocument/SalesDocumentFormLoader.Library.js:1:909) at https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/...

Preconditions Supported Operating Systems : This install will work on Operating Systems that support the fall 2016 release of Dynamics 365 Server. The process : 1. Download the Setup FieldService-OnPrem-6_2_1_38-5ea54f2c17.exe 2. Unzip the Setup 3. Start the PackageDeployer.exe 4. Login to your target instance 5. Go through the wizard Login with user of Dyn365 Online that has Dual Use Right License like Plan 1 or Customer Engagement assigned: Final result: Field Service and Resource Scheduling is now available.

My team and I were waiting so long for this tool: https://www.microsoft.com/en-us/download/details.aspx?id=56966 The following version requirements exist for source and target environments: Source: Dynamics CRM 7.1 or later FieldOne Sky 5.1.0107.611 or greater Resco MobileCRM Woodford 9.1.4.0 You must upgrade Woodford to 9.1.4.0 and publish the mobile project to version 9.1 before migrating Target: Dynamics 365 for Customer Engagement Fall 2016 release or later The process: The tool: More documentation is provided in the download ZIP package.

Now has GDPR compliance, more enhancements and some bugfixes : https://blogs.msdn.microsoft.com/crm/2018/04/03/release-notes-for-field-service-and-project-service-automation-update-release-5/

Field Service and Project Service Automation Update Release 6 on Dynamics 365 Version 8.2: Now has GDPR compliance and some bugfixes :   https://blogs.msdn.microsoft.com/crm/2018/04/03/release-notes-for-field-service-and-project-service-automation-update-release-6-on-dynamics-365-version-8-2/

One of our customers approached us with the following issue they had with the Field Service app provided by Microsoft’s Store. The customer has an on-premise CRM installation. Therefore the app is required to access the CRM server via ADFS in the company’s local area network. The simplified architecture looks equal to this one: After some time of investigation I was able to repreduce this issue with the native Resco Mobile CRM app installed via Microsoft Store with Windows 10 as well. Whenever the machine had an internet connection the app worked just fine, but as soon as the app was launched in a local area network only without any internet connection, the app complained with the error box shown above. Second step was to use Fiddler tracing as described here: https://www.resco.net/fiddler-trace/ With an active internet connection I found appropriate Fiddler logs with connection requests. Interestingly, without internet connection I could not find any requests at all. This ga...

1. Open this link: https://mbs.microsoft.com/customersource/Global/365Enterprise/downloads/product-releases/365fieldservicedownloads 2. Login with a valid account 3. Download and unzip binaries 4. Start package deployer to install the solutions.