I'm going to do a multi-post series on the functionality that comes with the Microsoft Dynamics 365 Developer Toolkit. In part 2 we are going to go through the customizations project and understand what functionality comes with it.
We have to configure the Developer Toolkit first. Inside of Visual Studios we have to go to Tools->Options and then set the Path for both the Plug-in Registration and Crm Sdk Bin Directory. After setting these we're ready to create our Customizations project.
The creation of the project is as easy as creating any other project inside of Visual Studio. We'll go new project and then find the Customizations project.
Once we've created the project we'll be guided through a wizard to connect to our CRM organization.
Once we're connected and solution selected we'll be loaded into Visual Studio with our project open. We should also have the new CRM Explorer which is what we'll be using to access the different components of the solution inside of Visual Studio.
Now that we're all setup we're ready to understand what functionality is available to us within the CRM Explorer. Let's explore each of the solution areas in more detail.
The entities section will display all of the entities within your solution. Your able to do a few different things by right clicking on any entity; when we do this we've given 4 options: Refresh, Create Plug-in, Add WorkflowActivity, and Create Class for entity. It should be noted that trying to create either a WorkflowActivity or Plug-in will throw an error until your solution has a CRM Package project time created in it. We'll be going over the CRM Package project a bit more in Part 3 of the series and how it all wraps together.
There isn't really any functionality available for the option sets. It shows you all of the ones in the solution and your able to double click then opening the option set within a browser to be edited.
The web resources section is split into all of the different web resource types. This is a bit easier to navigate all of the web resources within your solution. We're able to double click and open the web resources in a browser for editing as well.
Inside of the processes we're able to create Actions, Business Processes, Dialogs, and Workflows. We're able to double click and edit the processes we're viewing as well.
We're able to Install the profiler for plug-in troubleshooting and do that within the solution. It's actually pretty hard to do it this way as it's very simple to debug plug-in code. If the profiler is something new to you; I'd recommend reading more at: https://msdn.microsoft.com/en-us/library/hh372952.aspx.
We're able to register and edit existing service endpoints within the CRM Explorer. This is fairly handy if this is something you use heavily. For an example of how to do this I'd recommend reading: https://msdn.microsoft.com/en-us/library/jj863635.aspx.
We're able to view all of the security roles associated to the solution as well open them in a browser for editing. We are not able to create or delete within the CRM Explorer.
We're able to view all of the field security profiles associated to the solution as well open them in a browser for editing. We are not able to create or delete within the CRM Explorer.
Overall the CRM Explorer is a great way of looking at a solution within visual studio. Your able to access the different records by opening them in a browser as well dig into your code for plugins/processes/etc. In Part 3 of the series we're going to create a CRM Package project and then come back and create a plugin to show you how it comes together within your new solution and CRM Explorer.
Thanks for tuning in as always!
Hi Jason, Thanks for you blog. Instead of On-Premises i select Office 365, Checkbox "Display list of available organzizations" and "Show Advanced". In Advanced i fill out Online Region, User Name and Password. Afterwards die Dialog shows "Connecting to the Microsoft Dynamics CRM server..." but connection is not established... sandglass. Cancel or exit the dialog is not possible, only exit VS. What could be the problem?