Most of us know that you can use the CHANGECOMPANY function in NAV to change the target company for a query in NAV to allow us to perform C.R.U.D. operations against a table in another NAV Company. While that can be pretty handy for reading data, it has several difficiencies when we want to perform an INSERT, MODIFY or DELETE. The biggest difference is that any Triggers that get triggered actually get run against the Company where the code is being executed from and not against the target company. With the advent of the NAV Web Services we have a new alternative.

Well It Depends on What Time Zone You Are In.

I Recently Encountered A Problem Where A Web Service Returned A Different Date Value For The Today Variable When Ran As A Web Service.

When Microsoft added a Web Services interface to Dynamics NAV with the 2009 release, it took a huge step forward in allowing other applications to be integrated with NAV. Additional improvements have been added with the SP1 and R2 releases. But the question that continues to come up with end users is "What can I do with the NAV Web Services or more specifically, what can they do for me?". I am going to give you my top 10 list but please understand that this just scratches the surface of the capabilities allowed by the NAV Web Services.

I am starting a list of Windows Server and Active Directory commands that are useful for troubleshooting NAV Web Services, etc.  I will keep adding to this list as I discover new ones.

The NAV Web Services provide a customizable API for external programs to use to get data from or write data to NAV using all of the available business logic and in an industry standard format. NAV Web Services can also be used to trigger functionality within NAV to be run.

Have you ever wished that NAV could integrate with (talk to) another system or data source to retrieve or update information. Well there are a number of ways built-in to NAV for doing just that.