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.
Today I tried to import the database of our productive environment into our test-environment, to check a few things and test some features, without interrupting the productive environment. Using the Deployment Manager I run the wizard of importing an organization, but at the step of mapping the users, I was getting the following error message: …
Everybody was already thinking of a feature, which is missing in CRM. But how can you tell Microsoft, to add this feature?
Creating and tracking appointments to Dynamics CRM is one of the base functions to keep all information per account and contact at one place. Therefore all appointments with a customer should be created or tracked to CRM. But be careful with this approach. As soon as you create an appointment in CRM, this appointment will …
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.
If you get an Unhandled Exception in your mailbox profile alerts, but no real information, where it comes from, then this post will help you.
I created a new custom entity and added a subgrid of this new entity to my account entity. Clicking the Plus in the right, upper corner the system opens a new line with a magnifying glass (like it shows in the screen below) instead of the quick create flowing from the top.
Today I tried to import the field service solution to my vanilla organization on an on premise system. I started the PackageDeployer and followed the instructions and then, the import started and the circle was running. After some time I thought, that the import might have failed, because there was no progress.
I tried to export the whole default solution with all customizations of our testing environment. After 5 Minutes, the export stops with an error message, but no details. Digging in the logs I found an error, which is telling me, that the process was running into a timeout:
>MSCRM Error Report:
Error: Request timed out.
Error Message: Request timed out.
Error Details: Request timed out.
Source File: Not available
Line Number: Not available
Request URL: https://crm/CRM/_grid/cmds/dlg_exportsolution.aspx?appSolutionId=%7bFD140AAF-4DF4-11DD-BD17-0019B9312238%7d&command=exportsolution&ismanaged=0&optionxml=%3csettings%3e%3cexportAutoNumber%3efalse%3c%2fexportAutoNumber%3e%3cexportCalendar%3efalse%3c%2fexportCalendar%3e%3cexportCustomization%3efalse%3c%2fexportCustomization%3e%3cexportEmailTracking%3efalse%3c%2fexportEmailTracking%3e%3cexportGeneral%3efalse%3c%2fexportGeneral%3e%3cexportMarketing%3efalse%3c%2fexportMarketing%3e%3cexportOutlookSynchronization%3efalse%3c%2fexportOutlookSynchronization%3e%3cexportRelationshipRole%3efalse%3c%2fexportRelationshipRole%3e%3cexportSales%3efalse%3c%2fexportSales%3e%3cexportExternalApplications%3efalse%3c%2fexportExternalApplications%3e%3cexportIsvConfig%3efalse%3c%2fexportIsvConfig%3e%3c%2fsettings%3e
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 …