Gunnar's Blog

Up to now we in Advania have been using the method described here on my blog to connect to most of the Soap web services that we needed to integrate with. The problem with this method is that we have to manage a lot of DLLs.  This has caused some issues and problems. Another thing is that we are moving to AL .  And in AL we can’t just throw in a custom DLL to do all the work. In C/AL We can do this with standard dotnet objects DOMDoc := DOMDoc.XmlDocument; DOMProcessingInstruction := DOMDoc.CreateProcessingInstruction('xml','version="1.0" encoding="utf-8"'); DOMDoc.AppendChild(DOMProcessingInstruction…

Microsoft supports Side-by-Side development for C/AL and AL .  To start using the Side-by-Side development make sure you have the latest version of AdvaniaGIT add-in for Visual Studio Code  and update the PowerShell scripts by using the “Advania: Go!” command. When the Business Central environment is built use the “Advania: Build C/AL Symbol References for AL” to enable the Side-by-Side development for this environment.  This function will reconfigure the service and execute the Generate Symbol References command for the environment.  From here on everything you change in C/AL on this environment…

Until now I have had my G/L Source Names extension in English only. Now the upcoming release of Microsoft Dynamics 365 Business Central I need to supply more languages.  What does a man do when he does not speak the language? I gave a shout out yesterday on Twitter asking for help with translation.  Tobias Fenster reminded me that we have a service to help us with that.  I had already tried to work with this service and now it was time to test the service on my G/L Source Names extension. In my previous posts I had created the Xliff translation files from my old ML properties.  I manually…

And what is an interface Codeunit? A Codeunit that you can execute with CODEUNIT.RUN to perform a given task is, from my point of view, an interface Codeunit. An interface Codeunit has a parameter that we put in the This parameter is always a table object. We have multiple examples of this already in the application.  Codeunits 12 and 80 are some.  There the parameter is a mixed set of data and settings.  Some of the table fields are business data being pushed into the business logic.  Other fields are settings used to control the business logic. Table 36, Sales Header, is used as…

In the last blog post we completed the translation to our native language.  Since then I have learned that I also need to include translation files for EN-US, EN-GP and EN-CA. With the latest update of AdvaniaGIT tools that was an easy task.  Just asked to create Xlf file for these languages and skipped the part where we import C/AL translation. I have also been pointed to a new tool that can work with Xlf files.  Multilingual Editor: https://marketplace.visualstudio.com/items?itemName=MultilingualAppToolkit.MultilingualAppToolkitv40 Now I call out to all who are ready to help me with the…

We are on a path to upgrade G/L Source Names from version 1 to version 2.  This requires conversion from C/AL to AL, data upgrade and number of changes to the AL code. A complete check list of what you need to have in your AL extension is published by Microsoft here . Our task for today is to translate the AL project into our native language. To make this all as easy as I could I added new functionality to the AdvaniaGIT module and VS Code extension .  Make sure to update to the latest release. To translate an AL project we need to follow the steps described by Microsoft here . To…

When upgrading an extension from C/AL to AL (version 1 to version 2) we need to think about the data upgrade process. In C/AL we needed to add two function to an extension Codeunit to handle the installation and upgrade.  This I did with Codeunit 70009200 .  One function to be execute once for each install. PROCEDURE OnNavAppUpgradePerDatabase@1(); VAR AccessControl@70009200 : Record 2000000053; BEGIN WITH AccessControl DO BEGIN SETFILTER("Role ID",'%1|%2','SUPER','SECURITY'); IF FINDSET THEN REPEAT AddUserAccess("User Security ID",PermissionSetToUserGLSourceNames); AddUserAccess…

So, where is step 1?  Step 1 was converting C/AL code to AL code.  This we did with AdvaniaGIT and was demonstrated here . First thing first!  I received the following email from Microsoft. Hello, The decision has been made by our SLT, that the use of a Prefix or Suffix is now a mandatory requirement. If you are already using this in your app(s), great. If not, you will want to do so. We are coming across too many collisions between apps in our internal tests during builds and have seen some in live tenants as well. It makes the most sense to make this a requirement now. If you think about…

When using DotNet data type in NAV C/AL we normally lookup a sub type to use.  When we do the result can be something like Newtonsoft.Json.Linq.JObject.'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' Then, what will happen when moving this code from NAV 2016 to NAV 2017 and NAV 2018.  The Newtonsoft.Json version is not the same and we will get a compile error! Just remove the version information from the sub type information. Newtonsoft.Json.Linq.JObject.'Newtonsoft.Json' And NAV will find the matching Newtonsoft.Json library you have installed and use it…

I just uploaded a SQL bacpac to AzureSQL.  This I have done a number of times.  Connected my service to the SQL database and tried to start the service. This time I got an error.  Looking in Event Viewer I can see. The following SQL error was unexpected: Change tracking is already enabled for database '2018-IS365'. ALTER DATABASE statement failed. SQL statement: IF NOT EXISTS (SELECT * FROM sys.change_tracking_databases WHERE database_id=DB_ID('2018-IS365')) ALTER DATABASE [2018-IS365] SET CHANGE_TRACKING = ON (CHANGE_RETENTION = 10 MINUTES, AUTO_CLEANUP = ON) I looked into the SQL database…