XRM was CDS then and Dataverse now

I waited for sometime before writing this post. Since renames and rebranding happened multiple times in the past. And sadly some got reverted due to some unavoidable situation (Dataflex).

Coming to the point, “Common Data Service” is hereafter going to be called as ”Dataverse”, to be precise - ”Microsoft Dataverse”. Along with that MS Teams turned into a Developer platform with its own database which was earlier called as Project Oakdale (code name) - hereafter “Dataverse for Teams”. We even had a meetup session in our NYC Power Platform group on this topic.

We all know CDS is nothing but our very own Dynamics CRM under the hood. I prefer to use XRM (“anything” Relationship Management) - which is why the platform is more than just CRM (Customer Relationship Management), a perfect candidate with all fabulous features viz Rigid security concepts, SDK, REST API, Normalized Database, and what not as a complete package.

How many of you know, CDS 1.0 was tried on Dynamics Axapta (FinOps now) and for some reason, later CDS 2.0 born on top of Dynamics CRM. That’s how we got this Power Platform today after lot of adventures.

I’m pretty excited to see the future roadmap and product lifecycle. Fingers crossed.

Apart from that, some terminology changes also announced along with this. I pasted the content I posted in my LinkedIn below for context.

“The name changing will continue until morale improves.” - James Phillips, President (BizApps at Microsoft).

Common Data Service has been renamed to Microsoft Dataverse

Some terminology in Microsoft Dataverse has been updated. For example, entity is now table and field is now column