Registering a plugin in CRM may result in an error. In my case, I was registering a new assembly and got an error that the assembly has a total of  plugin/workflow activity types.
Developing plugins in the Dynamics 365 Online System is different of how you develop them on-premise. The framework-restriction will be covered in this article.
Today a customer told me, that some mails are not in the queue, but are available in the exchange mailbox. Therefore I started searching. As the whole Server-Side-Sync-Job is just a blackbox, I started to check the plugins and found an error. This caused an exception and therefore blocked the import of the email. I …
Fetching E-Mails from crm, there are multiple attributes. If you like to know, who has sent the mail, you need the attribute sender. This attributes contains the e-mail-address. But CRM also connects the sender with an account or contact, if the e-mail-address field is filled in with the mail address. In my post Connecting e-mails …
Plugins are a common way to add functionality, especially in an on premise system, as there is missing the possibility for using the flows. I created such a plugin, which uses some of the localization methods, deployed the plugin to my development system and got the following error.
Microsoft.Crm.Sdk.Messages.RetrieveLocLabelsResponse cannot be cast to [B]Microsoft.Crm.Sdk.Messages.RetrieveLocLabelsResponse.
Based on my previous post, CRM is sending appointments automatically to the attendees. But what if you don’t want CRM to send this appointments? The system itself has no option, to disable this behavior, but there is a workaround. This is not just configurable in CRM but also on Exchange.
There are some default “business process flows” in CRM. After a new installation or upgrade of Dynamics CRM and installation of the current version of FieldService, you will find some default business process flows. If you want to hide or delete this, just keep reading.
After some time, you will have multiple solutions in your CRM environment. In my case, there were multiple unmanaged solutions, as I have transferred many customizations between my test- and productive environment. Via the solution menu in the settings, you can delete unused solutions, but only one after each other. This consumes much time and …