I have been doing a lot of custom workflow steps lately for MS CRM. I've been using the CRM Developer Extensions which makes it so easy to get started with a plugin or custom workflow. If you add a CRM Workflow Class template, it adds the following lines (I've omitted a few others it adds for clarity):
You are here
Whether you’re a user that just wants to share a view with someone or you’re an administrator/manager that would like to create and distribute personalized views, sharing personal views is a very common thing, so it’s surprising that CRM for Tablets does not support it. Shared views that a user does not own do not display in the mobile app. Even worse, if the user has access to a dashboard that contains personal views, they’ll receive a generic error:
When building a Web API project, you need to keep in mind how requests to your methods will be made. If requests are made client-side, you'll need to take CORS (Cross-Origin Resource Sharing) security into consideration. This can be done a few ways, which I won't get into for the sake of this post, but you can find more information about CORS here.
While working in Dynamics CRM, I needed to add several options to a few different optionsets on the Lead entity. Adding the options isn’t difficult, but can be tedious and repetitive, so I didn’t want to do it manually. I decided to leveraged the CRM SDK and used a LINQPad query to populate the optionset as shown in Figure 1.
After upgrading from CRM 2016 to Dynamics 365, we noticed that the Notes control on a form for one of our custom entities was no longer working properly. It would display, but there was no longer any way to add notes to the record:
When it should be displaying like this:
Sometimes you run into an error message that can mean any one of several things has gone wrong, and there's no real way to know what is the true solution. The error "Managed Metadata Service or Connection is currently not available" in SharePoint is one of those error messages.