Dynamics 365 Rocker's Blog

There was a requirement where a note(annotation) will be created once an account is created in Dataverse. I have created a Microsoft flow to achieve this functionality. Below is the screenshot of the flow: It was not a difficult flow but I was getting below error in last step i.e, "Create a note and attach PDF" Resource not found for the segment. The reason for this error was assigning "Account id" in regarding: To resolve the above error, I have set "accounts(Account)" in regarding and it worked. You can also use "/accounts(Account)". Conclusion : Whenever you are creating a #Dataverse note or activity through #MSflow then use "entityname(entityid)" or "/entityname(entityid)" in regarding and don't forget to add suffix "S" in entityname. Cheers, Rocker

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...