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: 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 Entity1and 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 - Interview Part-3

Q: - Explain Goal management.

Ans: - In Goal management module mainly Goal, Goal Metrics and Rollup queries entities are used.

Goal management is only place where no form design changes from 2011 to dynamics 365. Still dynamics using same form design for goal management.

The goal management in Microsoft Dynamics 365 lets us set sales, marketing, and other business goals for our organization and measure the results against the targets. The goal management will help us to motivate our work force, identify successful programs, do better planning, and grow our business.

Goal. This gives you the actual figures, whether it is revenue or number of tickets sold.

Goal metric. This tells you how your goal figure is being measured (number versus dollar amount). There are some out of the box goal metrics for Revenue, No. of Product Units, and No. of Cases, but goal metrics can be created for anything you wish to measure.

Rollup field. The goal metric has rollup fields which are the definitions of how we want to calculate actual and estimated values of the goal being measured—in our case, estimated versus actual revenue and estimated versus the actual number of tickets sold.

Goal Type: - Dynamics 365 have  two type of goals.

1. Amount/Revenue/Money
2. Count

Case Study: - For more understanding of goal management I am taking below case study.

                        Customer service team setting target for customer service executive to resolved cases per quarter.

1. Click on sales or service from site map area.

2. Select Goal and click on “New” button to create a Goal.

3. New window will open. Now provide Name of your goal.

4. In my case study I am taking case count. So, in Goal metric I am selecting “No. of cases”. This is out-of-box Goal metric.

5. Now set required user in Goal owner.

6. Provide time-period for which you need to set goal.

7. Provide expected value in Target(Integer).

Now your goal almost created, but we need to fill some details in Goal Criteria.

1. Record Set for Rollup if want to use all records select All else for owner select owned by goal owner.

2. If you are using parent-child goal than you can select if parent will participate in rollup calculation or not.

Rollup Query: -

            Rollup query is mainly used you want to select set of records need to participate in rollup calculation based on user filter criteria.  Here I am taking Query for cases which are created by me for actual and all cases for In-progress calculation. 

Goals will automatically be recalculated every 24 hours. A system administrator can alter that time frame to happen more frequently if needed in System Settings. Additionally, clicking the Recalculate button at any time in the command bar will force a recalculation of the selected goal.

You will find some out-of box- chart for Goal. These charts are used to see actual and In-progress value comparison.

I think this blog will give you basic idea about Goal in Dynamics 365. I my next blog I will explain Customer service module.