Upgrade your previous version Common Data Service database, apps, and flows
You can now upgrade previous version Common Data Service (CDS) databases to the latest CDS for Apps. This upgrade process also helps you upgrade any apps or flows that currently use the previous version CDS database so that they will work with CDS for Apps.
Now is the time to start upgrading your databases and the apps and flows that use them. Please target completing all your upgrades by March 1, 2019. The previous version CDS will be discontinued on March 15, 2019.
We are aware of some databases which have unusual circumstances who will require some extra help, and will will be reaching out to them next week.
We have also provided a way to skip the upgrade and just get a new CDS for Apps database for your environment. If you are interested in this option, see Skip upgrade and just get a new CDS for Apps database below.
Which CDS is this for?
To avoid confusion, this table contrasts these similarly named databases:
|Full Name||Short version||Also known as||Description|
|Common Data Service||CDS||
||Released in 2016 with PowerApps.|
|Common Data Service for Apps||CDS for Apps||CDS 2.0||Released in 2018 with substantial enhancements over the previous version.
More information: New features in the Common
Data Service for Apps! (Spring Update).
This upgrade will upgrade your CDS database, including any apps or flows that use it to a CDS for Apps database.
For most people, if you started using PowerApps after March of 2018, you should already have a CDS for Apps database, so this upgrade is not for you.
Note: People who started using a Microsoft Dynamics 365 for Talent environment before October 1, 2018 will need to upgrade.
Upgrade your database, apps, and flows
When you view your environments using the admin portal (https://admin.powerapps.com/environments), you will see an Upgrade now link for any environments still using the previous version of CDS.
When you view the environment, you will also see a banner and an Upgrade now button.
Either the link or the button will take you to a page that will guide you through a three-step process.
The three-step process helps minimize the down time required when the final step completes the upgrade. It also helps coordinate apps and flows created by different people. While this process has three simple steps, the complexity of the upgrade process will depend on how you have used the previous version CDS for apps database and the number of apps and flows that are using it. If you intend to upgrade, please start right away.
You can learn all about the process in the Upgrade to Common Data Service for Apps documentation.
Skip upgrade and just get a new CDS for Apps database
While you have a previous version CDS database in your environment, you cannot add new CDS for Apps database in that environment.
Perhaps you never created any apps or flows using the previous version CDS database? Or perhaps you just evaluated it and don’t have any apps or flows connected to it that you currently use?
If you are eager to get a new CDS for Apps database in your environment and you don’t care about upgrading any existing data, apps, or flows you can just delete your previous version CDS database and add a new CDS for Apps database. You can be done in just a few minutes using PowerShell. For information on this option, see Delete your previous version Common Data Service database.
If you aren’t comfortable using PowerShell, you can contact PowerApps support and request this be done for you.
The previous version of CDS will not be supported for much longer. We plan to discontinue the previous version of CDS on March 15, 2019
In the coming weeks will send email notifications to all tenant and environment admins where there are environments still using the previous version CDS database. We will also monitor our telemetry for the upgrade process to ensure everyone who wishes to upgrade can be successful.
Important: If people take no action, we will expect that they are not interested in upgrading and their databases will be deleted 30 days after the service is discontinued.