Upgrade to CDS for Apps - time for each step?

[bbtestA0]

I've been trying to upgrade my CDS for 2 days. Step 1 - create test database have been "active" for 36 hours (I've not received an error message yet so I suppose it still working). We only have a few entities and apps (5), no flows. 

Where or how can I check if my process is working?

[JimDaly-MSFT]

---

@ShaneOss wrote:

@JimDaly-MSFT  Wow! We are also in the same situation. Step 1 completed but assumed that MS had sent notifications as designed. Are there plans to fix for customers that have completed Step 1 but not yet finalised their upgrades? I.e. to resend the notification with the necessary info: https://docs.microsoft.com/en-us/common-data-service/upgradecds/upgrade-verify-apps-flows

---

I requested this be added, but couldn't get it. We had to choose between providing this and fixing other blocking bugs.  Yes, it is a big inconvenience for people who started their upgrades early, but we have lots of other things that need to be fixed and this wasn't considered to block people from upgrading. Please advise if you feel otherwise.

The workaround is that you can look at the list of affected apps and flows at the end of step one. It should list the owner of the app so that you can contact them directly. Also, you should be able to review apps using the admin portal: https://docs.microsoft.com/en-us/power-platform/admin/admin-manage-apps 

Finally, support has a tool that they can run to get a list of affected apps and flows if you send them your information.

[ShaneOss]

Thanks @JimDaly-MSFT  for the info.

I've logged a ticket regarding the issue. Having a list of affected apps/flows would be great! Will follow up via the support ticket. There were no apps or flows listed at the end of step 1, nothing under Resource Copies.

[Caroline]

@ShaneOss it's not so much that they haven't gotten to it yet, more that they haven't been able to find a solution. It was suggested that I tried a manual transfer as my back up plan, as I don't want to risk loosing everything.

@JimDaly-MSFT I saved the app to my desktop, created a new environment, and have uploaded the app into that. I'm currently uploading the entities into the new environment too. It's good to know that the date has been extended though. 

[JimDaly-MSFT]

---

@ShaneOss wrote:

Thanks @JimDaly-MSFT  for the info.

I've logged a ticket regarding the issue. Having a list of affected apps/flows would be great! Will follow up via the support ticket. There were no apps or flows listed at the end of step 1, nothing under Resource Copies.

---

If you see no affected apps or flows at the end of Step 1, could it be that no one is using the database?

[ShaneOss]

---

@JimDaly-MSFT wrote:

---

@ShaneOss wrote:

Thanks @JimDaly-MSFT  for the info.

I've logged a ticket regarding the issue. Having a list of affected apps/flows would be great! Will follow up via the support ticket. There were no apps or flows listed at the end of step 1, nothing under Resource Copies.

---

If you see no affected apps or flows at the end of Step 1, could it be that no one is using the database?

---

@JimDaly-MSFT  I don't think so. We have 64 PowerApps and 25 Flows in that DB (environments/Default-19537222-55d7-4581-84fb-c2da6e835c74). 🙂

[JimDaly-MSFT]

---

@JimDaly-MSFT I saved the app to my desktop, created a new environment, and have uploaded the app into that. I'm currently uploading the entities into the new environment too. It's good to know that the date has been extended though. 

---

When you get a new environment, the database will be CDS 2.0, which has different entities that CDS 1.0 had. If your app has relatively simple needs and you can manually re-create and move the data, it may be easier to do that than the upgrade.

[Caroline]

@JimDaly-MSFT yep, that's all good. It is a relatively simple app, and so far, it doesn't look like I have to recreate too much. Thanks for the advice 

[JimDaly-MSFT]

---

---

@JimDaly-MSFT  I don't think so. We have 64 PowerApps and 25 Flows in that DB. 🙂

---

And you are telling me that all those apps and flows use data in the CDS database? If that is true, then they should be listed at the bottom of Step 1 as affected apps and flows..

Forgive me, but I've been responding to some people who have been concerned about the apps and flows on their environment, but we only find that the Apps and Flows in their environment don't use CDS as the data source. They are connected to all kinds of other data sources, but not CDS.

While each environment has a CDS database, not every App or Flow uses it.

If your apps and flows depend on CDS and they aren't being listed at the bottom of Step 1, then I need to investigate that as a bug.

[ShaneOss]

@JimDaly-MSFT  They were created by other users within the organisation. I'm not sure if they acutally are referencing CDS as a data source. In our test tenant when we performed the upgrade I saw the apps and flows listed at the end of Step 1. Thought that would be the same would be the case for our PROD tenant.

So your saying Apps/Flows listed under "Resources" within the default environment CDS database may not be using it? I can supply a list.

[JimDaly-MSFT]

---

@ShaneOss wrote:

@JimDaly-MSFT  They were created by other users within the organisation. I'm not sure if they acutally are referencing CDS as a data source. In our test tenant when we performed the upgrade I saw the apps and flows listed at the end of Step 1. Thought that would be the same would be the case for our PROD tenant.

So your saying Apps/Flows listed under "Resources" within the default environment CDS database may not be using it? I can supply a list.

---

Apps and flows can use a wide range of connectors, the previous version CDS database connector was just one. I wouldn't be surprised that your test tenant would have apps and flows created by people for learning or evaluation purposes. But in your production environment, those same apps and flows using the previous version of CDS might not be present.  That is something we hope you can discover, because it might save you a lot of work.