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 ...

In version 1710 (9.0.2.2279) of Dynamics 365 Online we get this dialog to create a new app… As you can see it contains the Client options Web and Unified Interface. After an automatic minor update to the newer version 1710 (9.1.0.33) online you only have this dialog available. This version creates a unified interface app by default and you cannot create apps with a web interface anymore. Microsoft is transitioning from the classic web interface to the relatively new unified interface. Is this the version where we cannot create new web interface based apps anymore? Either this is a bug or we face the next wave mentioned in Steve Mordue’s article: https://stevemordue.com/the-transition-to-unified-interface/

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/...

On a customer tenant we had the issue on some orgs that with SLA feature enabled on the entity work order the transferred solution created on the target system fields with lower case schema names: DEV-System with proper schema names: Exported as managed solution and then imported to a Dynamics 8.2.2.x Online system: => now with wrong lower case schema names Microsoft confirmed in our support case that this is a bug and it was fixed in this version: Microsoft Dynamics 365 Version 1612 (8.2.2.2518) (DB 8.2.2.2464) online

I read several blog articles how easy it is to use realtime workflow based auto number solution with a new auto number entity. In one of the recent project I thought I will use this approach instead of a third party solution. It worked fine but I struggled with this issue: As you can see the value has decimal separators. So I was upset and thought about how to solve it. A blog article wrote about how we could change the user and the global format settings to work around this issue. I did not like this approach neither would my customers like it. Finally, I smart tip was found on this blog article written by Prashant Shukla: http://dynamicscrmcoe.com/auto-numbering-real-time-workflows-no-customization-no-add/ Quote: “To remove the comma from the Auto-Number field (whole number), copy it to a calculated field of Single Line of Text.” Only thing after the creation of this new field I had to update the workflow to reference the new calculated field which e...

If you recently updated your CRM environment and CRM users approach you with complains about their personal language settings, not being able to set their desired language - you might have forgotten to install the required update for the MUI language pack(s) as well. if you see this behavior go to Settings –> Administration –> Languages There you go => we forgot to update the language pack to the latest update version

Recently I used this tool for a Dynamics 365 project. I made a few fixes and rebuilt it with support for Dynamics 365 v.8.2.x. https://github.com/acieslik/CRMCustomizationToolForExcel The original code was taken from Microsoft’s discontinued Codeplex platform: https://archive.codeplex.com/?p=crmcustomizationtoolforexcel I thought it would be worth to continue this nice project and tool on Github. Its very intuitive, easy to use, and got some potential to be improved, also for V.9.x features.

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.

Today my browsers were teasing me with this error message when I tried to open our Dynamics 365 web site. I cleared the browser cache and voilà the problem was gone.

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/

The EU’s new General Data Protection Regulation is scheduled to take effect on May 25, 2018. Designed to serve as a uniform set of data protection laws within the EU, it will become law alongside the BDSG in Germany. This means that all affected companies will need to make extensive adjustments to the new legal landscape. Here are the most important impending changes: Expanded executive responsibility Effective application of data protection law based on increased liability and fines “Privacy by design” and “privacy by default” will become basic principles of data protection law Data Protection Impact Assessments Expanded obligation to report data incidents Expanded documentation regulations (including with regard to information security management systems, or ISMS) Expanded citizens’ rights Modified role for data protection officers Since there won’t be any transitional period as they take effect, you need to get your company ready for these new l...

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.

Some customers as well as on my machine I had the problem that the Dynamics 365 for Outlook never showed the entity views in the right Outlook pane. Also the message “Waiting for a page to be retrieved from a CRM server…” appeared in the ribbon bar. I first activated the trace logging of the Outlook Add-in but it did not help to find any pointers. Finally the message of the ribbon bar entered in Google Search allowed me to find the link below: https://support.microsoft.com/en-hk/help/4049314/microsoft-dynamics-365-for-outlook-is-unable-to-render-webpages-after It will help you to resolve this issue.