Dynamics CRM - Sharepoint Upload Event

Dynamics 365 provide out-of-box integration with SharePoint which we used to manage our documents.

It hosts SharePoint document library in CRM page to upload or mange document.

But sadly Dynamics CRM/365 do not provide any event when document is uploaded in CRM.

Some time we to trigger an action like approval process, notification, email or task once document is uploaded.

So, in this blog I will try to counter this issue with help of Microsoft Flow.

So, let’s begin………

1. Login in O365 portal with admin permission.

https://www.office.com/?auth=2&home=1

2. Open SharePoint.

3. Open Flow

4. Open Dynamics 365

5. Create a new Team Site in SharePoint 

Select Public as privacy setting.

Copy Site address in notepad for use.

Click on next than finish.

6.  Go to Dynamics 365 and setting->Document management.

7.  Click on Document Management Settings

8. For demo purpose I am only taking Contact entity for SharePoint integration.

9. Paste your site URL that we created previously.

10. Click on next and leave Select folder structure as uncheck than Next and Finish.

11. Go to Microsoft Flow and click on “Create from template” to create new flow.

12. Search for “Get a push notification when a new file is added in SharePoint” template and click on it.

13. Click on “Edit in advanced mode"

14. Paste site URL that you create earlier. And select “Contact” in library name and leave folder as blank.

15.  Delete push notification step, we do not need this.

16. Click on “New step” and select “Add a condition”. If we do not add this condition it will create two tasks.

17. Click on “If yes” and select “Add an action"

18. Select Dynamics 365 from connector.

19. Currently there is no template to execute an action or workflow. So, I am creating a high Priority “Task” for testing and can trigger workflow or action based on our requirement.

20. Select “Dynamics 365 – create a new record” action.

21. Select your organization than “Task” in entity.

22. Provide required information and save it. Now all setup is done now time for testing. We can create multiple Flow for different entities.

23. Go to any contact record and navigate to document. Upload a new document.

24. Once document is uploaded wait for few second and go to Microsoft flow to check history of your flow.

25. Open last history.

26. If result, is successful go to Dynamics 365 to check Task is create or not.

Bingo!! Task created.

Try to use this and share your feedback.

Dynamics CRM: SandboxAppDomainHelper.Execute

With upgrade of Dynamics CRM after 2016 some time we faced different kind to strange issue.

Recently I had faced issue in one of our running plugins.

Error: -

Parameter name: SandboxAppDomainHelper.Execute: The plug-in type could not be found in the plug-in assembly: MyAssemblyName

Dynamics CRM Version: -

After debugging and doing different R&D we find there is no issue in our plugin code.

Issue was occurred due to Microsoft update. If you find this kind of error fellow below steps. Hope this will also works for you.

Resolution Steps: -

1.        Update below reference in “MyPluginName” assembly with version 9.0

·         Microsoft.Crm.Sdk.Proxy

·         Microsoft.Xrm.Sdk

2.       Update assembly using plugin registration tool.

3.       Update below reference in “MyPluginName” assembly with version 8.2.0.0

·         Microsoft.Crm.Sdk.Proxy

·         Microsoft.Xrm.Sdk

4.       Update assembly using plugin registration tool.

5.       Disable and again enable below step

I had used Nuget “Microsoft.CrmSdk.CoreAssemblies” package.

Share your comment and follow blog to be updated.

Happy CRM!!

Dynamics CRM: Note Control Customization

In Dynamics CRM 2013 onward Microsoft introduce note control with more options.

Note control have “Posts’, “Assistance”, “Activities” , “Notes”, “One Note” etc.

This is a great Control to see all information in single control.

But this control does not support any customization. Some time we need to customize this control for our users.

I will try to explain how we can customize note control. However, this customization is Unsupported customization and not recommended by Microsoft.

Requirement: - I had the requirement where I need to show “Activities” and “Notes” on contact form and only “Notes” on Account Form.

Solution: - I have create a html web resource to accomplish my requirement. In HTML we are getting note control help of getElementById method of DOM Javascript. After getting note control based on our requirement we remove unwanted elements from our control like “POST” and “ASSISTANT” from contact form.

Import below solution in your organization. CRM version 9.0. This solution contains HTML web resource need to use. If you faced any issue while importing, unpack this solution and create a new HTML web resource in your organization and paste html code from sav_wsblankhtml file.

Download Solution

Once web resource is created, add this on contact or other entity form as required below note control.

After adding web resource pass parameter to hide required components. And uncheck visibility. Change value as per requirement.

POSTS=true&ASSISTANT=true&ACTIVITIES=false&NOTES=false&ONENOTE=true

Open “Activities Tab” property and select tab which need to default and visible always.

Now Publish your customization. And refresh(ctrl+r) your entity record.

Result: -

Contact record:

Account record:

Share your comments and follow blog to be updated.

Happy CRM!!

Dynamics CRM: Delete Components From Managed Solution

Currently I have faced a scenario where I need to remove few unused components from my managed solution in Production Instance.

My first approach was remove unused components from my solution in Dev instance and export as managed solution than re-import in Production. But this approach not worked for me.

So, my second approach was delete unused components from my solution in Dev instance and export as managed solution than re-import in Production. But this approach also not worked for me.

Finally, I found one approach that works and fulfill my requirement. Here I am sharing my final approach, and this also work in supported way.

I will try to explain this with a simple example where no dependencies components are present.

• I have created one solution named Solution1 in Dev instance and create a two new entities Entity1 and Entity2 in that solution and publish all customization.

• Export Solution1 as Managed Solution from Dev and import in Production Instance. This will create Entity1 and Entity2 and my Production Instance.

• Now create new solution named Solution2 in Dev Instance and add Entity1. Here we have not added Entity2 in this solution because we need to delete Entity2 from all Instance as result.

Note: - If number of components are larger, than use Xrmtoolbox “Manage Solution” Plugin to create clone to solution. And remove unused component from newly created solution.

• Export Solution2 as Managed Solution from Dev and import in Production Instance. This will not create any entity but hold Entity1 as another managed solution layer.

• Delete managed solution Solution1 from your Production instance. This will delete solution and its component but Entity1 will remain in your Production Instance due to Solution2.

• Now Delete Entity2 from Dev instance and publish all customization.

• Export Solution1 as Managed Solution from Dev and import in Production Instance. This will not create any entity but hold publisher, solution name all other components as it was required in this approach. 

Expected Result: -

• Delete managed solution Solution2 from Production and Dev instance to clean instance.

 With this approach, I was able to remove my all unused component from my solution. Also, solution name is same and no need to data backup and reimport. But solution Installed On date is changed which was not important in my use case.

Dynamics CRM : ViewRoleConfiguration

Recently in Dynamics 365 I got a requirement to show system views based on user security role. 

I try find any out-of-box way to achieve this but unfortunately there is no Out-of-box way to achieve this.

I had developed customize way to configure System views visibility based on security role. 

After completing my solution, I think this might be requirement for other CRM users also.

This tool is working only on classic CRM and also install a solution in your environment.

So, I have created XRMToolBox plugin for this configuration. Now anyone can download this plugin either from XRMToolBox or from given link ( Download Plugin) and configure.

Configuration: -

• Open XRMToolBox and connect to your Organization.
• Search “view-role configuration” if already installed else go to XRMToolBox “Plugin Store” and install this plugin. Or save downloaded plugin in your Plugin folder.

• Open View-Role Configuration plugin. If you are using this plugin first time you need to click on “Import Solution” button first.

Download Solution

• This step will install a new solution named “ViewRoleConfiguration” in your organization. This solution is developed on Dynamics 365(9.0) version.

• Once this solution is successfully installed. We are ready to configure our system views based on different security role.
• Click on “Retrieve Data” button. This will retrieve security role list and entities list.

• Select your “Security Role” for which you want to configure view permission.

• Now select entity for which need to configure view permission.

• On Entity selection, it will show all system views whose (querytype is 0). I.e view which shows in view selector.

• Select the view which you want to hide for given security role.

Example: - I am using “My Active Accounts” for demo.

• Now click on “Save Data”. This will create a record in “View Role Configuration” entity. This record will be used to enable security role-based view visibility.

Before View-Role view configuration: -

After View-Role Configuration: -

• We can see that “My Active Accounts” is not visible in Account view selector list. Even this view also not available in advance find view.

• When we want to remove View-role security. Follow the same process and now just de-select view and click on “Save Data”. This will delete the configuration record and view will become available for that security role.
• We can also delete this solution from your organization with the help of given plugin.

Note: - Use two users while testing this plugin. One user by which you connect XRMToolBox. Second user which have that security role on which you are configuring security role-based system views.

Please provide your comment and share your reviews.

Dynamics CRM: Manage Solutions

People says, “Necessity is the mother of invention”. But I think “Laziness also initiator of invention”.  😊

In CRM as a developer we always played with Solution. We create new solution to manages our development and to transfer our work from Dev to Test instance etc. Solution also required for marketplace package movement.

After CRM 2016, Microsoft also added two new option in Solution: -

Clone a patch- To make small change related to parent solution.

Clone Solution- To merge current solution and patch in single updated solution. And remove previous one.

But here I am not discussing about these features because you will find some good materials related to these new features in google.

Use Cases: -

• When I was working for one of my project I have a solution more than 400 components. And I need to create a solution with 300 components of that solution. You could say Clone a patch might work but not in my case because it creates dependency on parent solution and create a blank solution.

• In one of another project I had a managed solution in Production. In development Organization have unmanaged solution which played by lot of team members, as we developer do always.😉 We need an unmanaged solution from that managed solution. But Microsoft do not give any feature for this.

• I need to export list you all solutions. But no option found either in advance find or in solution view.

While tackle with these situation, I was thinking there should be something a single click option to do so.

Now I started developing a XrmToolbox plugin to help me. Today I am deploying my Plugin for all developers and soon it will be available in XRMToolbox also.

Features of this Plugin.

• Retrieve all Solutions
• Make a Copy of Solution
• Delete Solution
• Export Solution to folder
• Export Solution list to excel
• Publish All Customization.

Download XRMToolBox from given URL and install. https://www.xrmtoolbox.com/

Install Managed Solution Plugin in your XRMTollBox using plugin store.

If you are not able to find Manage Solution plugin.

Download Plugin

Install in XRMToolBox by clicking Settings->Path->Storage folder->Plugin folder.

Copy assembly in Plugin folder.

Connect your organization and open plugin Managed Solution.

Click on “Retrieve Solution”. Now you will see list of all solutions and their information.

Select any managed or unmanaged solution to make a copy of it. Select solution and click on “Make a copy” button. Before creating a copy, you need to provide new solution name.

It will create a copy of your solution with all source solution component.

To Delete any solution, select your solution and click on “Delete Solution” button.

To Publish all customization, click on “Publish All Customization” button.

To export all solutions list, click on “Export Grid” button provide your location to store solution excel sheet. Make sure you have MS office preinstall to use this option.

To export any unmanaged solution, select unmanaged solution and click on “Export Solution” and it open a new form. Fill required details in new form and click “Export” button.

It will save your unmanaged solution in your specified location. You can save managed and unmanaged solution same time.

With this plugin I was able to tackle all my use cases in lesser time. 

"I choose a lazy person to do a hard job because a lazy person will find an easy way to do it" 

      Bill Gates.......

Note: - Plugin based on .net framework 4.5.2

Please share your feedback.

Follow my blog so you will not miss my new upcoming blogs.