Skip to main content

Posts

Cannot find the administrative settings with Unified Interface apps in my Dynamics 365 trial

Recent posts

Set Multi-OptionSet values with a custom workflow activity

As the relatively new multi-optionset field type arrived with v.9 of Dynamics 365 the need to set values via workflow is quite a common requirement. So I searched within the community to find some ideas on how to solve and create such a workflow activity and so I stumbled upon Demian Raschkovan’s Workflow Tools with can be found on his github repository: https://github.com/demianrasko/Dynamics-365-Workflow-Tools/blob/master/msdyncrmWorkflowTools/msdyncrmWorkflowTools/Class/MapMultiSelectOptionSet.cs

It gave me some basic ideas to reach my requirements which are: Should be generic for any type of entity Ability to specify the attribute name of the required multi-optionset for that entity Provide a list of multi-optionset values (comma-separated) Keep existing values (True/Yes => add provided values / False/No => replace all values with the provided values Remove specific value(s) from an existing set of values
My code sample (without other dependencies):
using Microsoft.Xrm.Sdk; using Micr…

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

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 (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/msdyn_…

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 (8.2.2.2518) (DB 8.2.2.2464) online