In a recent article I explained how to establish a connection from a Console application to Microsoft Dynamics CRM On-Premise. In this post, I will cover the same steps on how to connect a Console application to Microsoft Dynamics CRM/365 Online using the Microsoft.Xrm.Sdk and Microsoft.Xrm.Tooling.Connector namespaces
Recently I have seen a lot of posts on the CRM Community of how to establish connection to CRM using a Console application. In this post I will review the steps of establish a connection. I will focus on CRM On-Premise using ADFS/Claims/IFD, and will provide additional samples on connecting to Dynamics CRM Online in a separate blog article.
In the recent weeks, I have seen a lot of topics in the Dynamics Community forums asking about what are the capabilities of the Dynamics 365 Team Member License, and what actions can or cannot be performed with this license. I have decided to summarize the details from the licensing guide regarding this licenses to be able to answer some of the questions that arise.
There might be certain projects where you have a custom entity with address fields, and you want have a composite field that will display the address, and be able to use that process across the board in multiple entities. The example below shows how to do that.
With the release of Dynamics 365 (online), version 9.0, there are a lot of changes in our developer resources. One of the biggest changes though, is that the Microsoft Dynamics CRM SDK will no longer be available as a download. The new name of the SDK, as it was known will be the Microsoft Dynamics 365 Customer Engagement Developer Guide.
This is probably a request that has been required many times, but recently, one of our customers had a request to open an OnBase document based on some data that was available in a subgrid. Since OnBase has a web to query the database using a query string in their web application, this seemed to be an easy enough solution.
Recenly we received requests from clients and some questions from Dynamics Community members on how to Clone records. Although there are some available solutions out there, and the various possibilities on how to implement this, we would like to demonstrate here one possibly and not to complicated way on how to implement this. This implementation involved using Ribbon Workbench to create the Clone button and a Command that will execute a JavaScript function, which will call an action and execute Plugin/Action code to copy the record.
When choosing to execute webapi functions, that are various methods that are available. The first option of course is to use the default GET, POST and PATCH required to Retrieve and Update data in CRM using the Web API.
This blog post will demonstrate how to create a simple button using Ribbon Workbench which will execute a JavaScript function on the client. In order to do this make sure that you have Ribbon Workbench installed in your CRM environment, or you can use the Ribbon Workbench that is available with XRMToolbox.
Many times we are asked by our customers to disable Bulk Edit to certain users or groups of users/teams within the system. That requirement is pretty straight forward and can easily be understood. The resolution to this of course is also easy, and can easily be accomplished by changed the Bulk Edit privilege for a particular security role. What happens though when the requirement is to disable bulk edit from a user only on a particular entity. This becomes a little more complicated.