In one of my projects I use Excel a lot for reporting. I create the Excel documents with OpenXML and with the help of the Excel Buffer table. With the click of a button the user creates a beautiful Excel Workbook but when I open the workbook it is displayed in the back of Dynamics NAV client window....
In a previous blog I showed how to get the database name and the database server name for NAV 2009. I used Automation object to read the service configuration file and pull from there the required information. This method is obsolete for NAV 2013 but here is the required code to pick similar and more...
Microsoft Dynamics NAV is still using the old DOS code page for files. If you create a file with the file variable and write text to that file you will get a DOS file. The same thing happens when writing to a BLOB and exporting to a file. The Code example below handles the DOS code [...]
Gunnar Þór Gestsson
Filed under: Filed under: Dynamics NAV, How-To's, NAV 2009 R2, XML, Data Transfer, C/Side Code, Dotnet interoperability, Text File, NAV 2013, Stream, CSV-file
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...
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 [...]
As the Icelandic localization for NAV 2013 is supposed to land here in April it is now time to start moving the solutions to the new platform. One of the things that I have used are the automation variables for SQL server connection. In NAV 2013 I plan to replace all automation variables with dotnet...
In the Classic Client we had the C/AL command BEEP to sound an alert to the user. This function is not supported in the Role Tailored Client. Here we have a solution in .NET. Where Console is a RunOnClient DotNet variable ‘mscorlib, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089′...
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 →
Gunnar Þór Gestsson
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
For some time have been looking for a solution on how to upload a file into BLOB with RTC Client. The built in functions, UPLOAD and UPLOADINTOSTREAM both force an Open Dialog. I already had the file name and wanted … Continue reading →