Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 110 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Calling Dynamics NAV Page Web services from .NET Core (Read SubPage Data)
averied
Member Posts: 1
Wonder if anyone has experienced with connecting to NAV Web services from a .NET Core app.
The main issue I'm having is when calling Services like the SalesHeader Page SOAP WS. When I call the Read method, the Sales Lines are returned as null (I guess any SubPage data will return as null).
I'm not sure if this is happening since NAV 2018 or even before, as I can see some blogs describing a succesful connection, but not confirming if the Read Operation succesfully returns the SubPage data
Testing with Postman, I can see the response is correct, as Sales Lines are there in the response. The problem seems to be with the proxies generated by .NET tools.
I've tried adding a service reference from visual studio to http://NAVSERVER:7047/DynamicsNAV110/WS/CRONUS España S.A./Page/SalesOrder
i've tried using the Microsoft WCF Web Service Reference Provider
Odata Tools are just a nightmare, in my experience it's better to make manual requests, but the thing about ODATA is you won't get Page and Subpage in a single call, like you can with SOAP
The only generated proxy that works is the old .net 2.0 based "Add web reference" from Visual Studio, but this is not available for .NET Core.
So it's sad that we can't have a 100% functional solution at the moment. Other operations like Create are working correctly. The problem is reading Subpage data. Right now we are stuck with manual requests. Would be nice to have working Visual Studio generated proxies.
Please I'd be thankful if you have any insight about .NET Core and NAV integrations, as .NET Core is trending right now, and I guess soon we will need external apps to interact with NAV.
The main issue I'm having is when calling Services like the SalesHeader Page SOAP WS. When I call the Read method, the Sales Lines are returned as null (I guess any SubPage data will return as null).
I'm not sure if this is happening since NAV 2018 or even before, as I can see some blogs describing a succesful connection, but not confirming if the Read Operation succesfully returns the SubPage data
Testing with Postman, I can see the response is correct, as Sales Lines are there in the response. The problem seems to be with the proxies generated by .NET tools.
I've tried adding a service reference from visual studio to http://NAVSERVER:7047/DynamicsNAV110/WS/CRONUS España S.A./Page/SalesOrder
i've tried using the Microsoft WCF Web Service Reference Provider
Odata Tools are just a nightmare, in my experience it's better to make manual requests, but the thing about ODATA is you won't get Page and Subpage in a single call, like you can with SOAP
The only generated proxy that works is the old .net 2.0 based "Add web reference" from Visual Studio, but this is not available for .NET Core.
So it's sad that we can't have a 100% functional solution at the moment. Other operations like Create are working correctly. The problem is reading Subpage data. Right now we are stuck with manual requests. Would be nice to have working Visual Studio generated proxies.
Please I'd be thankful if you have any insight about .NET Core and NAV integrations, as .NET Core is trending right now, and I guess soon we will need external apps to interact with NAV.
0