Skip to main content


Set Multi-OptionSet values with a custom workflow activity

Recent posts

Updating custom workflow activites with additional input parameters

While developing new or extending existing custom workflow activies you might experience a problem that new or updated  input parameters will not show up on the workflow designer UI.

In the Plugin Registrations tool you successfully updated the assembly, but still it does not show up on the UI.

A simple trick solves the issue:

In the Plugin Registration Tool select the workflow activity that you want to update and press the save button in the properties section.

Booking Status: Field Service Status can’t be changed. Record is already used on Resource Bookings

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 change to Open – Completed.…

Dynamics 365 App Designer - Web Interface is going to be / already deprecated?

In version 1710 ( 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 ( 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:

TypeError: Cannot read property 'Metadata' of undefined at Object.GetOrderType - resolved

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 (
at Object.FormApplies (
at Object.OnLoad (

Issue with SLA fields with lower case schema names

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 namesMicrosoft confirmed in our support case that this is a bug and it was fixed in this version:Microsoft Dynamics 365 Version 1612 ( (DB online

Auto Number Workflow: Lessons learned with decimal separators

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:
“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 ended in this per…