Introduction: This blog consists of information on how you can find the triggering parameter of the Workflow. Scenario: There are many workflows on update of a record and which workflow is triggering for which fields and on which fields the workflow is dependent on. It may be handy to identify which fields are being used to trigger workflows. You would open each workflow and check or you could click field in every entity and Check Dependencies. But there is much easier way for it. Solution: We can make use of Advance Find on the Process Entity. There are some fields like 1) Trigger On Update Attribute List 2)Trigger On Create 3) Trigger On Delete 4) Is Child Process This fields can be useful in many ways. Trigger On Update Attribute List has a field list separated by comma. This are the fields on which the workflow triggers.

Introduction: Managing and understanding security roles in CRM can be tough. One of the Tools on Xrm.Tools is a Security Role Explorer, which tries to help make it easier. Steps to Compare roles in CRM: Go to xrm.tools site on browser. Click on Explore Roles Now button on the left most corner. You need to enter CRM organization credentials. Select Compare Roles buttons. Compare Roles – Allows you to compare two roles and look at what is Unique to each role, Different or the Same. This is great for example when you are trying to decide if you should consolidate some roles. View User Roles – It allows you to provide a user e-mail, it looks up all their roles and presents you a composite view of what their roles provide them. This is great when you have users that have multiple roles, and you want to see what their combined access is. View Entity Roles – You simply need to provide the logical name of the entity. Once provided it will show you all the roles and the access each role provides for that entity. This view is great when you simply want to know which roles have access to a specific entity, and you don’t have time to open 20+ roles up to find out! We will compare roles in this blog. Thus, enter the roles you want to compare. The result will be displayed and you can analyse the security roles and depending on the analysis you can create new roles or add access to the existing roles. You can compare the previous OOB role with the new OOB roles too.

Introduction: This blog consists of information on adding notes section in to your form and the difficulties faced while adding the notes section. When to use notes on entity forms: Notes are quick, easy and create a time-stamp. You can use when temporary and not critical information need to be shared with others. Prerequisites: 1. Notes should be enabled on the entity. Open the entity in the solution and check the notes box. 2. If notes are not present on the form, add on the form. If the notes section is already present on the form, the notes button will be disable on the form. Note the below points before adding the notes section: Dynamics CRM allows only one Notes/Activities/Posts per entity and which is enabled by default. If you try to add one more notes, you will get the error message. It will be visible only for the Main forms, so if you are deleting the Notes/Activities/Posts from Main form, it will be visible on another main form. If you want to make use of Notes/Activities/Posts to be added on some other form. You can’t use a notes control for an entity that is not enabled for Notes, so unfortunately you cannot have just activities, or activity feed posts. Disadvantages: Notes are not searchable. Notes cannot be included in Reports or advanced finds. Notes do not roll-up. Users must re-create the same note several times for different records. Information may be lost.

Introduction: In this blog, we will have a look on new updates on Business Process flow. Previous Release Updates: Business Process Type Run process as a task flow (Mobile) Run process as a business flow (Other clients) New Designer New Toolbar introduced with edit buttons, connector, new snapshot button to take screenshots of your business process flow design which can be used in technical documentations Security Note:  Your process will not show up in this tab until you Activate the process.  If you Deactivate it after updating security roles, the process will remain in the available in this tab so you will NOT need to go back and update your security roles again.  It’ll only be removed from the security role tab once you delete the process. Action Workflows Stages can execute workflows with a trigger of Stage Entry, or Stage Exit. Example: You can have the completion of a specific Business Process on an opportunity kick off a workflow that creates a Case, and activates a Business Process on that newly created Case. Stage Active Duration Out of Box feature, to see duration details in BPF- Total time for the BPF being in active state Additional Status Reasons available – Abandon, Finish Maximum number of processes, stages, and steps To ensure acceptable performance and the usability of the user interface, there are some limitations you need to be aware of when you plan to use business process flows: There can be no more than 10 activated business process flow processes per entity. Each process can contain no more than 30 stages. Multi-entity processes can contain no more than five entities. New Release Dynamics 365 July 2017 Update: Business Process Flow entities are now available on Site Maps, Views, Charts: Now the BPF are available in the form of entities and personalized views can be created and we do not need to write any code for getting the BPF in particular stage. Sales BPF will be visible in Sales area and Service BPF will be available in Service area. Site Maps Views Charts Action Steps: Calling an on-demand workflow or a process action from within the Business Process. Action will appear on the UI in the form of a button Business Process Flow in Unified Interface: Different stages of Business Process Flow When you click on pin the stage, the stage is pinned on the right side of the screen and we can see for how much duration the stage was in active stage as shown below The activity duration of the stages is visible even on the Business Process Flow Hope you like the new feature of Business Process flows with some new required functionalities.

Introduction: There can be a possibility that we lost our plugin code and dlls are already present in Dynamics CRM and we want to extract the code from Dynamic CRM. We don’t have a code backup and we are supposed to make changes in the code as we have some errors in plugin or we need to reconstruct the code. In such situation, we can follow the below steps to decompile the code. We can make use of XRM Tool Box and some tool to decompile dll. Steps: Steps to be followed are given below: Open XRM Tool Box–>  Assembly Recovery Tool–>  Select the plugin–> Click on Export to disk  Dll will be downloaded in the local drive  Download the code Decompile tool. Link is given below https://www.jetbrains.com/decompiler/ After download Open the Decompile Toolà Open the dll from local drive Your code will be decompiled as shown below Only issue is we must disable the previous plugin and register the plugin assembly and steps again. Now we can make changes in the code. Conclusion: Retrieving the codes from dynamics CRM dlls can be done by following the above easy steps.

Introduction: This blog consists of steps to change the name of the custom app in Dynamics 365. Initially the app name is “Dynamics 365-custom” as shown below. Steps: We can change the name to our organization name as shown below: Navigate to Settings–> Administration–>System Settings In General Tab–> Set options for the default app:Dynamics 365-custom–>Change the default app name The App name is changed to “CloudFronts Apps” and will be visible as below: Conclusion: Like this way, you can change the name of custom application in Dynamics 365.  

Introduction: While using Fetchxml queries to retrieve more than 5000 records, first page will give you 5000 records and paging cookie. Paging cookie will help to retrieve additional records. For additional records, we need to set the paging cookie in the fetch tag. Setting the paging cookie: When the fetch query is executed it brings the paging- cookie with it in the resultant response. The paging cookie is attached to the next Fetch XML The paging cookie consists of the first and last record details. Name and the GUID of the records. When trying to execute fetch XML request. it started throwing “Page Cookie Malformed” exception. This is because there is a special character present in the paging Cookie. You can see in the above cookie that Name has “&” which is the replacement for character “&”. This breaks the fetchXml request.There can be any character present in the record name such as (‘s). Even (‘) breaks the fetch XML. Thus, we need to encode the paging-cookie before it is inserted in fetchXml. pageCokies.replace(/&/g, ‘&’); This will help to solve the issue and we can retrieve more than 5000 records.

This blog consists of steps to add an external link to navigation bar in the application using new sitemap editor in Dynamics 365. Steps to be followed are given below: Create an HTML Web Resource in CRM consisting of below code. <html> <body> <script> //open link in new window window.open(“https://www.google.com”); </script> </body> </html> Open the sitemap editor and add a new subarea and the created web resource into your sitemap Publish your configurations and click on Google Search in the Navigation to check the results: Behaviour: On click on the link, the link opens in the new tab.

Introduction: Have you ever wondered what happens to the user owned records in CRM when the user itself is deleted from CRM? Will the records get deleted? Or Will it be assigned to some other user? What will happen to the existing system jobs? Let us see in the below example. Description: Suppose there is a user named “Somesh Siripuram” and this user has its own account records. The owner of this records is “Somesh Siripuram”. Now the user is being deleted from the admin portal and no longer has access to Office 365 and CRM. Login with system administrator and check for the deleted user. The user will be listed in “Disabled User” view. When you open the user the email address and the user name of the user will be changed and some number appears Now, it’s time to check the deleted user owned records Thus, we can see that records neither gets deleted nor the owner of the records get changed. Manual assigning of records to another user is required. Other effects: Waiting jobs will remain as waiting until it is cancelled. New system jobs (where workflow owner equals to disabled user) will fail. You need to change the owner manually, they are not auto assigned to system  

Introduction: There can be requirements to delete the components from the managed solution. Neither directly deleting the components from managed solution works nor deleting the field from unmanaged solution and migrating as managed solution to target environment works. We can make use of OOB feature of solution management. OOB feature used is Clone the solution. The version of the solution will be upgraded when we clone the solution. Steps: Steps to be followed are given below: Delete the components from your unmanaged solution that are not required or replaced. Make note of Version Number and click on Clone Solution. You can check the Version Number. It is increased by 1 count. Click on Save Version of the unmanaged solution will be changed Export the solution as managed and import on the target environment While importing this solution, make sure that you checked “Stage for Upgrade” When solution import completes, you can see “Apply Solution Upgrade” option. After applying solution upgrade, two difference can be seen in already installed managed solution on target environment. Version changed to 1.1.0.0 The component deleted in unmanaged solution will also be deleted in managed solution Conclusion: Thus, managed components can be deleted using OOB feature.