logo
search
Power Query Problems

Fix Power Query Merge Fails for Dynamics Business Central OData Tables

Aamir Naveed AkramAamir Naveed Akram Sep 28, 2026 869 views

Question details

Users experience connection closures when attempting to merge multiple tables connected via Dynamics Business Central OData feeds in Power Query.

Fix Power Query Merge Fails for Dynamics Business Central OData Tables
Product
Microsoft Excel
Device & OS
not provided
Scenario
Merging multiple data tables sourced from a Dynamics Business Central OData feed.
Observed behavior
Individual tables load successfully, but merging them causes the remote host to forcibly close the connection, likely due to authentication or permission errors.
Before you start

Ensure you have your organizational username and password handy, and verify that your account has the necessary permissions to read all required tables in Dynamics Business Central.

Solution 1Recommended

Verify and Re-enter Data-Source Credentials

Clear existing permissions and re-enter your organizational credentials to ensure the OData feed authenticates properly during the merge operation.

When merging tables in Power Query, the engine evaluates the combined data requests. If the stored credentials are not properly scoped or authenticated for the combined query, the remote host may forcibly close the connection.

1
Clear existing data source permissions

Open Excel and go to the Data tab. Click on 'Get Data', select 'Data Source Settings', and choose 'Global permissions'. Find the OData feed URL for Dynamics Business Central, and click 'Clear Permissions'.

2
Refresh queries and sign in

Return to the Power Query Editor and click 'Refresh Preview'. When prompted to authenticate, select 'Organizational account' from the sidebar.

3
Enter organizational credentials

Click 'Sign in' and enter the correct organizational username and password associated with your Dynamics Business Central account. Click 'Connect'.

4
Test individual queries

Test each table's query separately in the Power Query Editor to ensure they all load without error. Once confirmed, attempt the merge operation again.

Verify and Re-enter Data-Source Credentials
Account Permissions: Make sure you are signing in with an account that has explicit read permissions for all the tables involved in the merge. Missing permissions on even one table will cause the merge to fail.
Free Microsoft Office alternative

Try WPS Office for Seamless Data Management

While advanced Power Query connections can sometimes encounter complex authentication issues in Excel, WPS Office offers a lightweight, highly compatible alternative for everyday spreadsheet management, data analysis, and document tasks without the hefty price tag.

Fully compatible with Microsoft Excel (.xlsx) formatsLightweight application that runs smoothly on most devicesFamiliar user interface requires no steep learning curveBuilt-in data analysis tools for quick and efficient insights
microsoft office alternative - wps office

Frequently Asked Questions

Why does the OData connection close during a Power Query merge?

This usually happens when the combined data request exceeds the authentication scope or times out. Re-authenticating and checking permissions for all merged tables often resolves the issue.

How do I check if my account has permission for Dynamics Business Central tables?

You must contact your system administrator to verify that your organizational account has the required read access for the specific tables you are trying to merge via the OData feed.

Can I share my workbook publicly to get help with this error?

No, it is highly recommended not to share organizational files publicly. If you need to share your workbook for support, remove all sensitive data or use private messaging with official support staff.