Import and Export of tables failing in some environments

(1) Share

Report

Posted on by SB-24090026-0

In my dev environment (unmanaged) and production environment (managed) today I am unable to import or export tables. I created a new environment and did a restore there from dev and that new environment does not have the error, but dev and prod still do. I have done the imports previously, last week, and had no issues.

When I do an Export Data in those two environments, I get the error
Connection to dataverse failed . Please check the link below on how to fix this issue.

If I do an Import Data from Excel, browse to my file to upload and start upload, it gets the error:

The file could not be uploaded for Pack Item: [UnknownError] Type=Microsoft.PowerApps.CoreFramework.Communication.Http.NonSuccessHttpResponseException, StatusCode=NotFound, Msg=Server returned non-success HTTP response

Looking at network transfers from the Edge DevTools, when I select a file to import I get a 500 Internal Server Error on the CreateProjectEntity URL.

Request URL:

https://projectmanagementservice.us-il301.gateway.prod.island.powerapps.com/api/DataManagement/CreateProjectEntity

Request Method:

POST

Status Code:

500 Internal Server Error

Remote Address:

52.250.230.72:443

Referrer Policy:

origin

With the response:

{
"messageCode": "UnknownError",
"message": "[UnknownError] Type=Microsoft.PowerApps.CoreFramework.Communication.Http.NonSuccessHttpResponseException, StatusCode=NotFound, Msg=Server returned non-success HTTP response"

Categories:

Microsoft Dataverse with Power Apps

I have the same question (3)

All responses (2)

Answers (0)

SB-24090026-0 21 on at

Like (0)

Report

This is the screenshot from where I do the export from:

Generates the error:

Doing an import, this is the screenshot:

I see from other posts that I am not alone in this problem. Critical to get this fixed.

Was this reply helpful? Yes No
Suggested answer

jthewissen 28 on at

Like (0)

Report

Hi,

We experience the same issues on some of our environments.
The workaround for export that works for me, is using the edit with excel functionality to read data into excel, then save this as an CSV file. With a text editor change the semicolon to comma seperation and save the CSV file. This can be used to import.

The workaround that works for me is using the (old) advanced Settings view and start an import job there. There the upload works for our environments and uses the same steps for mapping columns.

Hopefully this helps you to import data, while the new experience is broken.

Kind Regards,

Jeannot Thewissen

Was this reply helpful? Yes No