export package BUG?

[beans]

Unable to export an app ( CDS 1.0 old version) using the Export Package. Getting "Something went wrong. Please try again later."  Was able to do this before. Is EXPORT package stopped under the OLD CDS?

[v-xida-msft]

Hi @beans,

Which license does your PowerApps belongs to?

I have made a test on my side, and don't have the issue that you mentioned. The screenshot as below:

Please take a try to clear cache of your browser, and then try it again to check if the issue is solved.

In addition, if you want to use the the Export app functionality within PowerApps, you need to have a PowerApps Plan 2 trial or PowerApps Plan 2 paid license. More details about exporting or importing your apps across environments with packaging, please check the following blog:

https://powerapps.microsoft.com/en-us/blog/powerapps-packaging/

Please check if your PowerApps has a PowerApps Plan 2 trial or PowerApps Plan 2 paid license, if you have, please also check if the license has been expired.

Best regards,

Kris

[beans]

Hello Kris, 

We still have that issue with some of our apps. Not with all.  Another person on my team has it too We all have P2 licenses.  I had no issues exporting package from CDS for Apps ( CDS2.0) environment,  Did one yesterday.  So this is a CDS 1.0 issue for us.  I guess I will open a ticket for this to get this addressed

[barlowse]

We have a similar issue. The error we get is "Could not find API 'shared_runtimeservice'. " We have opened a ticket with MS Support - but no resolution yet. Export on CDS 1.0 works and creates a zip file, but the import into CDS 2.0 is what fails.

Just curious if you got a resolution? 

[Anonymous · Accepted solution]

@barlowse @beans Are still having this issues? @Anonymous

[barlowse]

All good. Thanks.

[beans]

We have moved past this;  All good for now

[paulewert]

Unfortunately, that doesn't help the rest of us. How did you get past this?

[Fosse]

Hello,

In my case, I was able to get past this problem by individually selecting which dependencies to include when exporting. When I tried to include them all, the exporting failed, but when I selected only one, it succeeded.

In my case, Problems-table was the only one I needed. User table in the picture was some old table connection, that the app was connected to, which I was not using. The table without a name is probably some deleted connection.

I guess you could try also to get past this problem by deleting the unnecessary connection directly from the app, but in my case, that did not help.