Small and medium business | Business Central, N...

Connecting NAV 2015 (on-premise) Web service with power automate using http

(5) Share

Report

Posted on by AN-20081518-0

Hello everyone,

I tried to call dynamic NAV 2015 Odata in power automate but not getting response showing internal server error in invoke an http action as I already setup gateway which is working fine with SQL. Did I miss some configuration from dynamic NAV side? Any assistance will be appreciate.

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Sohail Ahmed 11,177 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
To connect Dynamics NAV 2015 on-prem web services with Power Automate using HTTP, here are a few key things to double-check:

✅ Basic Checklist:

Web Services Published in NAV:

Ensure your page/query is published under Web Services in NAV.

Access it from browser using the format:

http://<Server>:<Port>/DynamicsNAV/OData/<ServiceName>

Authentication Mode:

NAV 2015 typically uses Windows Authentication or NavUserPassword.

Power Automate doesn't support Windows Auth directly – you'll need to:

Use a custom connector (for basic auth).

Or expose NAV through an API proxy or gateway that supports it.

NAV Web Service URL Format for HTTP Action:

If you're using HTTP action in Power Automate, make sure:

Method = GET or POST depending on what you call.

URI = Proper OData endpoint.

Headers = Include Accept: application/json if needed.

Gateway Configuration:

Confirm that NAV server URL is added as an allowed data source in the on-premise gateway.

Test the endpoint directly in browser from the machine where gateway is installed.

Service Tier Configuration in NAV:

Verify OData Services are enabled in NAV Server Instance Settings.

Ensure correct Port (default is 7048 for OData).

🔧 Suggested Fix:

If you're getting 500 Internal Server Error, try the following:

Test the NAV OData URL directly in browser → confirm it's reachable.

Use Postman with basic auth to confirm the service responds properly.

Then replicate same headers and URL in Power Automate HTTP action.

🧠 Additional Tips:

For long-term use, consider exposing NAV through an Azure API Management Gateway or use BC/NAV connector via custom connector with basic auth.

Enable logging on NAV server to get detailed error about the request.

✅ Mark below checkbox to make this answer Verified if it helps you.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,423 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello,

Thank you for your question.

When attempting to connect Dynamics NAV 2015 (on-premises) to Power Automate using an HTTP action, and receiving an internal server error, there are several key areas to verify:

Recommended Checks:

OData Service Configuration in NAV

Ensure that OData Services are enabled in the NAV Server configuration.

Verify that the OData Base URL is accessible from the machine where the on-premises data gateway is installed.

Confirm that the web service endpoint is correctly published and accessible via browser or Postman.

Authentication Method

NAV 2015 typically uses Windows or NAVUserPassword authentication. Power Automate HTTP actions may not support Windows authentication directly.

Consider using Basic Authentication with a NAV user configured for web service access.

Gateway Configuration

While your gateway works with SQL, ensure that it is also configured to allow HTTP traffic to the NAV OData endpoint.

Check that the firewall allows inbound traffic on the port used by NAV OData (default is 7048).

SSL and Certificates

If using HTTPS, ensure that the SSL certificate is valid and trusted by the machine running the gateway.

Self-signed certificates may cause issues unless explicitly trusted.

Error Logging

Review the Event Viewer on the NAV server and the Power Automate run history for more detailed error messages.

Enable tracing in NAV to capture more diagnostic information.

Test Outside Power Automate

Use Postman or a browser to test the OData endpoint directly. If it fails there as well, the issue is likely on the NAV side.

If this response helps resolve your issue, please consider marking it as accepted so it may assist others facing similar challenges.

Best regards

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi, In addition, NAV2015 has stopped supporting, please upgrade to the latest version as soon as possible.

https://learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2015?wt.mc_id=DX-MVP-5004336

Thanks.

ZHU

Was this reply helpful? Yes No

Join the conversation

Community site session details

Connecting NAV 2015 (on-premise) Web service with power automate using http

✅ Basic Checklist:

🔧 Suggested Fix:

🧠 Additional Tips:

Recommended Checks:

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Connecting NAV 2015 (on-premise) Web service with power automate using http

✅ Basic Checklist:

🔧 Suggested Fix:

🧠 Additional Tips:

Recommended Checks:

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates