Do I need to Copy the OData URL and SOAP URL links in Web Services to NAV Administration Soap Services and OData Services?
Like this ?
by the way, im trying to integrate/run the NAV through outlook and after copying the link and pasting in SOAP URL and ODATA URL in NAV Administration and still gives me this error
Do I need to Copy the OData URL and SOAP URL links in Web Services to NAV Administration Soap Services and OData Services?
No! The Web Services Page shows you local URLs. The URL fields in the configuration are needed if you access the web service using a public URL, and that URL differs from the local one. If you don't have a differing public URL for the service you can leave the field blank. It is not needed.
I suggest you use SoapUI, or WebServiceStudio, or some similar tool to verify your web service is working, before consuming it from outlook.
Answers
https://Server:SOAPWebServicePort/ServerInstance/WS/CompanyName/salesDocuments/
above sample "SalesDocuments" is the service name.
below link for the detail :
https://docs.microsoft.com/en-us/dynamics-nav/web-services
You can open web service page to check your service name :
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
Do I need to Copy the OData URL and SOAP URL links in Web Services to NAV Administration Soap Services and OData Services?
Like this ?
by the way, im trying to integrate/run the NAV through outlook and after copying the link and pasting in SOAP URL and ODATA URL in NAV Administration and still gives me this error
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
@RockWithNAV I already copied it but still the same. same result
No! The Web Services Page shows you local URLs. The URL fields in the configuration are needed if you access the web service using a public URL, and that URL differs from the local one. If you don't have a differing public URL for the service you can leave the field blank. It is not needed.
I suggest you use SoapUI, or WebServiceStudio, or some similar tool to verify your web service is working, before consuming it from outlook.