The only reason you might have landed to this page is because your recent ribbon customization is giving you hard time and like me you did not knew about this very help full tool provided by Microsoft with D365 CRM.
If you are working on ribbon customization then the normal issues that you might face other then the logic that should happen after the click event is with either display of the newly added ribbon button, i.e. with Display Rule or Value Rule. It may be because of some small incorrect or missing configuration but that may take some time to identify.
We all know that some very basic things to check are: 1. Display Rule Configuration 2. Value Rule Configuration 3. Missing Command definition (yes, if your button does not have a Comment associated, the button will not be displayed on the ribbon).
But even after validating all this and even more if the issue is still not resolved then MS has provided a very good article on some more possible steps to be performed.
The article uses an in-app tool called the Command Checker to inspect the ribbon component definitions to help us determine why the button is hidden.
To enable the Command Checker, you must append a parameter ‘&ribbondebug=true‘ to your D365 application URL. For example: https://yourorgname.crm.dynamics.com/main.aspx?appid=9ab590fc-d25e-ea11-a81d-000d3ac2b3e6&ribbondebug=true
Once the Command Checker has been enabled, within the application in each of the various ribbon bars (global, form, grid, subgrid), there will be a new special “Command checker” button to open the tool.
More details on how to use the tool are available on the link shared above.
While working with a sub-grid in D365, a question was thrown regarding behavior of Add record (plus) button. Many of you must have observed that for few sub-grids, click action of Add record button opens a new form to create a new record while for others a new line is added in sub-grid where one can add the record name and associate it. You might have figured the reason for this earlier but it was now that a college helped to figure out why it happens for me.
For those who were still looking for the reason of this behavior like me, this is all related to requirement level of the look-up field on child record. If Look-up is configured as business required then a new form is opened else the grid provides an inline row to associate the record. My assumption for this behavior is that if the look-up is business required, then it is assumed that all the existing records are already associated with some parent record thus user should create a new record. Always correct me if i’m wrong 🙂
While working with Business Process Flow in Dynamics 365, one of my colleague faced issue with “Next Stage” button. On clicking “Next Stage” on first stage, user is navigated to second stage but the second stage is not marked as Active. User is required to set it as active manually by clicking “Set Active” button.
Upon checking found that it is a known issue in Dynamics 365. Background workflows related to the entity on which the BPF is configured are causing the issue.
The issue is expected to get resolved by July 2017. For now as a workaround, we are required to deactivate all the workflows related to the entity for which BPF is configured and activate them again. Second workaround is to convert the background workflows to real time workflows.
Very happy new year to all of my blog readers. This is my first post of the year and it could not have started in a better way. I am delighted to announce the new “Multi-Select Picklist control” from XrmForYou.com tools library. Showing a picklist attribute as multi-select is a requirement we get every now […]