Calculating exact Day, Time, No of Month in a Day, Number of days in a Year, Day of the Week and many more has always been a challenging point while writing code in NAV. Though you can manage to achieve this but anyhow you end up with many lines of code. But just twisting your code a little bit with some DotNet variable will bring you a broad smile in your face with just a single line of codes. For an example have a look into the below screenshot.
Tag Archives: DotNet
Append String – Use DotNet Variable
As a Developer there many scenario comes up where we need to append a text value. This kind of needs do comes up when we need to maintain a certain string length. As a common NAV Developer we use to write the below piece of code.
Remove Namespace – Web Service Response (DotNet Variable)
This Post is about How to Import directly an XML which is coming as Web-Service from different platform like .NET. Whenever we get a response from a .NET Service we usually get Namespaces coming as enclosed in it. Now being a NAV developer it’s something which becomes a barrier to us while getting it directly Imported from NAV XML Ports. So here we are to how get rid from this.
String Comparison – Use DotNet Variable
I guess many Developers might have had faced this Issue, Whenever we used to compare a Text variable in CAL Coding something like –
Resize Image using DotNet
We have a function to export items and their images to an Excel file using an RDLC report. However, the user was always forced to export in smaller parts, because the dataset was growing too big.
After some checking, it seems that their images were all very large around 7 mega pixels…
The function call was ambiguous. No matching method was found.
One of the problems with using DotNet in C/AL is that sometimes the C/AL compiled does not have enough information for select between different methods in the DotNet object.
As you might have gathered from my last posts, I am using DotNet more and more. It saves a lot of code writing and it is fast.
DotNet: Dispose happening too soon?
A while ago, I ran into a problem while using DotNet variables.
Whenever I executed the code in our development environment, the code executed without problems, however, on the client side, we received errors when reading the information out of the DotNet objects.