Adding NAV ODATA web service to ASP.NET Project as a service reference

(0) Share

Report

Posted on by Lynmat

Hello,

Am trying to Add NAV ODATA web service to my .NET application. The end point is able to return data on postman and when I try to access it from a browser.

However, when I try adding the endpoint as a service reference to my solution project. I get the error below.

3630.test.png

Any help to go about this will be appreciated

I have the same question (0)

All responses (5)

Answers (0)

Lars Lohndorf-Larsen on at

Like (1)

Report

Hello, I think that there are different ways to add services from VS (assuming that this is what you use), can you add screenshots of how and where you do this?

Was this reply helpful? Yes No
Lynmat 5 on at

Like (0)

Report

I right clicked on my application ->Add -> Service Reference.

Then I pasted the OData end point from NAV which when I click GO, it will find the service I want. The issue is when I proceed it doesn't retrieve the contents of the service. There is an error something to do with naming conventions of the field names from NAV.

Here it is

But the above fields are absent in any of my tables. Am wondering how to fix this.

Was this reply helpful? Yes No
Lars Lohndorf-Larsen on at

Like (0)

Report

Hello, please try a few more steps. From "Service Reference", click on "Advanced", then "Add Web Reference", and then copy the URL into the URL field there:

Also, rather than putting in a general URL (metadata), I cannot remember if you may need to specify either this URL:

http://MYPCk:13047/BC130/WS/CRONUS%20International%20Ltd./Services

Or from there a specific service like this:

http://MyPC:13047/BC130/WS/CRONUS%20International%20Ltd./Page/Chart_of_Accounts

And notice that here I am using SOAP URL, not OData.

Then follow the steps here as much as you can:

https://docs.microsoft.com/en-us/archive/blogs/nav_developer/nav-2009-sample-c-project-to-consume-a-nav-web-service

I am sure that things have changed since then, so I don't think it applies 100%.

And consider if you do need to use OData or SOAP (or just anything that works), but I think integration differes depending on which method.

Was this reply helpful? Yes No
Lynmat 5 on at

Like (0)

Report

I can comfortably use soap URL, the issue is ODATA Url which returns the service I want but it fails to scaffold.

Now this is the issue. If am able to remove these fields from NAV , and then I wil be able to fix the below problem

I think NAV does not allow this naming convention for the fields. These fields do not exist in my Services though they must be inheriting from fields 'Branch_Code', 'Bank_Code' and 'Citizenship' since these fields exist. I want to do away with the latter fields but i dont know how

Was this reply helpful? Yes No
Lars Lohndorf-Larsen on at

Like (0)

Report

How about if you create a new page and then have very simple names for each field. I think that even space in field names get converted into _,

In the example below I have field "Search Name", but I changed the Name to SearchName, which is what reflects in the OData:

Would that work?

Was this reply helpful? Yes No