Setting dataflow refresh settings results in "XrmODataClient_InternalError"

(2) Share

Report

Posted on by PA-28041025-0

Hey there,

I've been running into the following error when trying to set the refresh settings of dataflows.

Unhandled HTTP Request Exception. Status Code: 400. Reason: . Response Text: "XrmODataClient_InternalError".

I have several dataflows that connect to an on-prem SQL Server via a gateway. These dataflows query different tables. When trying to edit any refresh settings of these flows and hitting save this exception occurs.

All of these dataflows run successfully when triggering the refresh manually.

I did the following this to try to fix this:

verifying the owner of the dataflow is the logged in user
verifying the user has the necessary rights (systemadministrator and dataflow maker)
re-adding the connections to dataverse and the sql database to refresh credentials
updating the gateway to the current version and trying to debug via the gateway error log (without any useful insight)

The error popup is even behind a loading overlay, which I have to remove via the browser dev tools to even be able to copy the error and mashup script.

My current workaround is to duplicate the dataflow, which magically makes the refresh settings work again.

I hope this helps, if someone is running into the same error.

Categories:

Power Query

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Jon Unzueta 1,827 Super User 2025 Season 2 on at

Like (0)

Report
@PA-28041025-0

It sounds like you've been quite thorough in your troubleshooting! The error you're encountering, "XrmODataClient_InternalError," can be quite frustrating. Here are a few additional steps and considerations that might help resolve this issue:

Additional Troubleshooting Steps:

Check for Special Characters:

Ensure that there are no special characters in the names of your dataflows, tables, or columns. Special characters can sometimes cause issues with dataflow operations.

Validate Data Types:

Verify that the data types in your source tables match the expected data types in Dataverse. Mismatched data types can sometimes lead to errors during refresh .

Review Gateway Configuration:

Double-check the configuration of your on-premises data gateway. Ensure that it is properly set up and that all necessary ports are open. Sometimes, network issues can cause intermittent errors.

Incremental Refresh Settings:

If you are using incremental refresh, ensure that the settings are correctly configured. Incorrect settings can sometimes lead to errors during the refresh process.

Clear Cache:

Clear the cache for your dataflows. Sometimes, cached data can cause issues with refresh settings. You can do this by navigating to the dataflow settings and selecting the option to clear the cache.

Check for Updates:

Ensure that both Power Apps and the on-premises data gateway are updated to the latest versions. Updates often include bug fixes that can resolve issues like the one you're experiencing.

Monitoring and Logs:

Enable Detailed Logs:

Enable detailed logging for your dataflows to capture more information about the error. This can be done in the Power Platform admin center under the monitoring section.

Application Insights:

Consider using Application Insights to monitor and log detailed information about your dataflows. This can provide deeper insights into what might be causing the issue.

Workaround:

Your current workaround of duplicating the dataflow is a good temporary solution. However, it's important to identify the root cause to prevent future issues.

If these steps don't resolve the issue, it might be beneficial to reach out to Microsoft Support for more in-depth assistance. They can provide more specific guidance based on your environment and configuration.

Was this reply helpful? Yes No
FA-02101626-0 2 on at

Like (0)

Report

Up here.

I'm having the same issue from time to time in a bunch of dataflows that I have. It works if I refresh manually but when I try to set up automatic refresh, I get this error.

That happens in flows that used to work the day before.

I was the one who created the flows and I'm a system admin as well.

Someone with an idea?

Was this reply helpful? Yes No