What is Microsoft Dataverse?

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 may not reflect the new term in the future.


Cheers,

Rocker


Comments

Post a Comment

Popular posts from this blog

Power Automate: Create and attach Dataverse note or activity with an entity record through MS flow

Image
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
Read more

How to send Dataverse email through PowerAutomate

Image
In one of my project requirements, I have to send some recursive email notifications to the account owner. I have chosen Scheduled flow to do this operation, Everything was fine till I created the email. Now, I wonder how to send this email. In traditional Dynamics workflow, we have a "send email" option but there is no such option I can see in flows. What to do now?😓 No worries, After some research, I found "Perform a Bound Action" by which we can send an email. In "Perform a bound action", We have to choose the table as "Email messages", Action name "Send Email" and just mention created email message id in Row Id. Finally, My flow looked like this  That's all, Now the email will be sent from Dataverse. Please subscribe blog for regular updates. Cheers, Rocker
Read more

How to avoid "for each" in Power Automate when there is only one record in Dataverse List rows

Image
There are some situations when we retrieve only a single row. To retrieve an entity record from Dataverse we generally use "List Rows" feature and this always returns an entity collection. Hence we always need to go in "for each" loop. As shown in the below example, I am creating an email on the creation of an account entity record in Dataverse. I have retrieved a queue to set it in "from" activity party of the email. I know that there is only one queue record but I am helpless if I directly select "Dynamic content", It automatically creates a "for each" loop. See in below screenshots: If I go for expression rather than "Dynamic content" then I can avoid "for each" loop, Please refer below screenshot: Below line, I have written in expression: outputs('List_rows_Queue')?['body/value'][0].queueid Here "List_rows_Queue" is the above step, [0] is the first row and "queueid" is a field
Read more