Dynamics 365 Rocker's Blog

If you’ve been working with Power Platform or Dynamics 365 for a while, chances are you’ve used Ribbon Workbench to customize buttons in the command bar. It has been a go-to tool for years—but let’s be honest, it often feels complex, time-consuming, and a bit outdated. 👉 The good news? You don’t need it anymore for many common scenarios. Microsoft has significantly improved the platform, and now you can add and customize command bar buttons directly within Power Apps —no external tools required! 🔍 The Old Way: Ribbon Workbench Ribbon Workbench was powerful, but it came with challenges: Requires the creation of a separate solution for ribbon customizations. Publishing changes through the tool can be time-consuming. Manual configuration of commands, actions, and rules Dependency on third-party tooling Harder maintenance and upgrades While it’s still useful in advanced cases, it’s no longer the default choice for everyday command bar customization. ✨ The New Way: Command Designer in P...

I was working on a requirement where Dataverse entity record needs to be export in excel and send as an email attachment. In this scenario, each record must have a separate excel file, and as we know there is no way to create an excel file dynamically through flow. To achieve the above task, I have followed below steps: Step 1:  I created an excel template in one drive and this template has one table and two columns i.e. Name and City: We can increase/decrease columns as per requirement. In this example, my template name is "Sample sheet.xlsx" Step 2: Create a Microsoft flow that triggers on the creation of "Contact" in Dataverse: Then add a new step to get the file template from one drive that was created in Step 1: Next, Add a new step to copy the template with a new name at a new location on onedrive: I have created a new folder with the name "Copies" in onedrive before creating the above step. The next step is to compose rows, In step 1, I have created...

We were using Pre-Image in our workflow and returning an attribute value of this pre-image as an output parameter. Suddenly we were getting the below error: An unexpected error occurred from ISV code. (ErrorType = ClientError) Unexpected exception from plug-in (Execute): MyProject.Workflow.Value: System.Exception: Could not load type 'System.Buffers.Text.Utf8Formatter' from assembly 'MyProject.Workflow' because the method 'TryFormatDecimalG' has no implementation (no RVA).  The code was like this: Entity preImageEntity = crmWorkflowContext.WorkflowExecutionContext.PreEntityImages.Contains("PreBusinessEntity") ? crmWorkflowContext.WorkflowExecutionContext.PreEntityImages["PreBusinessEntity"] : null; StringAttrValue.Set(context,  preImageEntity .Attributes[AttributeName.Get(context)]); To resolve this issue, We have to implicitly cast attribute name "To String" as shown below StringAttrValue.Set (context,  preImageEntity  .Attributes[...

One day, some of the users in my Dynamics 365 CE environment were not able to attach a document against an appointment and other activities. A user who has a basic(user-level) create, global read, business unit edit, and global "append and append to" privileges on activities, trying to attach a document against an activity that is owned by another user/team. But unable to do it and getting an "insufficient privilege" message. We know that there is no privilege in the security role for "Attachment" and many people suggest that attachments are handled by "Note(annotation)" privilege. I have increased the notes privilege to global but no luck. After doing some research, I came to know that the "Activity attachments(Activitymimeattachment)" privilege depends on Activities. When I increased the activity  "Create, Append and append to" privilege to Global(Organization) then attachment also inherited this privilege. Hence users are a...

In simple words, Microsoft Power platform is a place where we can work on the following technologies: PowerApps  Power Automate Power BI  Power Virtual Agents   We can create the following type of components in PowerApps: Model-Driven App : Default app for Microsoft Dataverse or Dynamics 365. We can not connect with other system databases except Microsoft Dataverse. Canvas App : It provides the facility to connect with multiple system databases including Microsoft Dataverse. There are multiple prebuilt connectors available that help us to connect with multiple systems. Power Portal : It is a website for users who do not have an office365 license, Here users can interact with Microsoft Dataverse data. Here we can create flows and do operations in Microsoft Dataverse as well as in other systems. There are multiple prebuilt connectors available that help us to connect a flow with multiple databases. For eg, A task record should be created in Dynamics 365 if we get a tweet on...

Last month Microsoft changed the name of Common Data Service to  Microsoft Dataverse or Dataverse. There are the following changes in terms that we used to call in CDS: CDS Term Dataverse Term Entity Table Attribute/Field Column Optionset /Multiple Optionset Choice Two Option Yes/No Record Row But there is no change in API or web service, CreateEntityRequest is still called as CreateEntityRequest. Have a look at Power App to see the changes: But these changes are not reflected in Dynamics365 Solution. We can find the old term there i.e. "entity and option set" but the same solution in the power app reflects the new term i.e. Table, Choice etc. Solution in Dynamics 365  Solution in PowerApp CDS connector in Power App still has the name "Common Data Service", It may or may not change in the future. Solutions in Dynamics 365 may or ma...