-
These days I keep busy upgrading Advania solutions to Dynamics NAV 2013. All the older solutions that have communicated with web services have DOM objects and manually created XML files. We had to add and remove namespace to be able to use XML ports but in the end this worked flawlessly. In NAV 2013...
-
A few days ago I published objects for NAV 2013 and details on how to use a twain scanner with the hardware hub. I know that many happy Dynamics NAV users are still using older versions so I wanted to make this solution available for NAV 2009, both in the Role Tailored Client and in the [...]
-
We have some cases where the Dynamics NAV client is running in a remote desktop and the local machine has a bar code scanner connected. One way is to have the bar code scanner configured as a keyboard. This requires the focus on the correct input field in NAV to work. The other way is to [...]
-
I have now created a document scanning solution that uses the Hardware Hub. This means that you can place the scanner on any computer and the NAV Windows Client on any or the same computer. All you need is the Hardware Hub Twain Client on the computer that is connected to the scanner. The software is...
-
In August last year I posted a way to use dotnet interop and webrequest to replace the automation objects. I saw that we had a limitation that we have gotten used to. When using the WinHTTP automation we where able to look at the status and if the status was not the integer 200 we [...]
-
I am using web services in a company that does not have the license to use the Mobile Document Dispatcher. In Codeunit 1 and trigger CompanyClose there are functions to stop listeners. This is causing problems in the web service so I changed the code to and the error is history.
-
I have now completed my first all-dotnet codeunit. The codeunit uses a dll file that I created from the web service WDSL. This makes the programming a lot easier. This solution has a BLOB fields that stores both incoming and … Continue reading →
Posted to
Gunnar's Blog
by
thegunzo
on
2012-11-26
Filed under:
Filed under: Dynamics NAV, Solutions, Role Tailored Client, Web Services, NAV 2009 R2, XML, Soap Services, C/Side Code, Dotnet interoperability, BLOB, Add-in, NAV 2013
-
I have been working with the dotnet interop and consuming soap web services. I wrote about a dotnet interop based way to communicate with soap web services in a previous blog but now I want to demonstrate another way that … Continue reading →
-
I am currently working on a solution that requires a Dynamics NAV client to communicate with Dynamics NAV web service. This I have done before with the classic client and have used automation objects for the job. Now I wanted … Continue reading →
-
Sometimes a little more flexibility is needed than a single XML Port in a web service function. Then it is possible to send multiple files to a single web service. I am working on an enhancement for the inter-company posting … Continue reading →
-
XE.COM claims to be the world’s favorite currency site. They have XML data feed options that can be used to download the latest currency exchange rates into Dynamics NAV. I wrote a batch to import the current currency exchange rate from their data feed. … Continue reading →
-
I am building a web service for one of my clients and another company is using this web service for an aspx web site. I realized that I needed to test my web service before I can deliver it to … Continue reading →
-
Most of my clients require a running NAV Application Server. The NAS that is included in NAV 2009 R2 requires a license that is included in most licenses today. However, there are cases where more than one NAS is needed. … Continue reading →
-
In so many cases when writing code for Dynamics NAV you want to display a dialog to notify the user or open a progress dialog. Today, we always need to consider that the code might be running from a web service … Continue reading →
-
In NAV 7 the NAV Application Server will no longer be supported. The Job Queue has been redesigned to support the new CREATESESSION feature that will create a new session on the service tier to execute a given task. In … Continue reading →