Dynamics NAV Mexican Sales and CFDI Part 2

Now the real problem

Codeunit 10145 (in case that you use the Microsoft imposed PAC).

In function LOCAL CreateXMLDocument (changes in yellow).

WITH TempDocumentHeader DO BEGIN
   AddAttribute(XMLDoc,XMLCurrNode,’version’,CompanyInfo.”CFDI Version No“);

   AddAttribute(XMLDoc,XMLCurrNode,’formaDePago’,GetPmtTermCode(“Payment Terms Code”));
   IF “Currency Code” <> ” THEN BEGIN
     AddAttribute(XMLDoc,XMLCurrNode,’TipoCambio’,FormatAmount(1 / “Currency Factor”));
     AddAttribute(XMLDoc,XMLCurrNode,’Moneda’,”Currency Code”);
   AddAttribute(XMLDoc,XMLCurrNode,’total’,FormatAmount(“Amount Including VAT”));
   IF IsCredit THEN
   AddAttribute(XMLDoc,XMLCurrNode,’metodoDePago’,”Payment Method Code”);
   IF CompanyInfo.”Bank Account No.” <> ” THEN
     AddAttribute(XMLDoc,XMLCurrNode,’NumCtaPago’,GetBankAccountLastFourChars(CompanyInfo.”Bank Account No.”));

  // Emisor

  // Receptor
   XMLCurrNode := XMLCurrNode.ParentNode;
   XMLCurrNode := XMLCurrNode.ParentNode;
   XMLCurrNode := XMLNewChild;
   AddAttribute(XMLDoc,XMLCurrNode,’rfc’,Customer.”RFC No.”);
   AddAttribute(XMLDoc,XMLCurrNode,’nombre’,”Bill-to/Pay-To Name”);
   AddAttribute(XMLDoc,XMLCurrNode,’UsoCFDI’,TempDocumentHeader.”CFDI Use”);
   // Receptor->Domicilio
   XMLCurrNode := XMLNewChild;
   AddAttribute(XMLDoc,XMLCurrNode,’calle’,”Bill-to/Pay-To Address”);
   AddAttribute(XMLDoc,XMLCurrNode,’colonia’,”Bill-to/Pay-To County”);
   AddAttribute(XMLDoc,XMLCurrNode,’localidad’,”Bill-to/Pay-To City”);
   AddAttribute(XMLDoc,XMLCurrNode,’pais’,Customer.”Country/Region Code”);
   AddAttribute(XMLDoc,XMLCurrNode,’codigoPostal’,”Bill-to/Pay-To Post Code”);

  // Conceptos
   XMLCurrNode := XMLCurrNode.ParentNode;
   XMLCurrNode := XMLCurrNode.ParentNode;
   XMLCurrNode := XMLNewChild;

  // Conceptos->Concepto
   TempDocumentLine.SETRANGE(“Document No.”,”No.”);
   TempDocumentLine.SETFILTER(Type,'<>%1′,TempDocumentLine.Type::” “);
   IF TempDocumentLine.FINDSET THEN
       XMLCurrNode := XMLNewChild;

//New SAT Requirement Start
       AddAttribute(XMLDoc,XMLCurrNode,’ClaveProdServ’,TempDocumentLine.”SAT Product/Service Code”);
//New SAT Requirement End

//New SAT Requirement
AddAttribute(XMLDoc,XMLCurrNode,’ClaveUnidad’,TempDocumentLine.”Unit of Measure Code”);
//New SAT Requirement
       AddAttribute(XMLDoc,XMLCurrNode,’unidad’,TempDocumentLine.”Unit of Measure Code”);
       AddAttribute(XMLDoc,XMLCurrNode,’valorUnitario’,FormatAmount(TempDocumentLine.”Unit Price/Direct Unit Cost”));
         XMLDoc,XMLCurrNode,’importe’,FormatAmount(TempDocumentLine.Quantity * TempDocumentLine.”Unit Price/Direct Unit Cost”));
      //New SAT Requirement Start
       XMLCurrNode := XMLNewChild;
         XMLCurrNode := XMLNewChild;
           XMLCurrNode := XMLNewChild;
           AddAttribute(XMLDoc,XMLCurrNode,’Importe’,FormatAmount((TempDocumentLine.Quantity * TempDocumentLine.”Unit Price/Direct Unit Cost”)*1.16));
           AddAttribute(XMLDoc,XMLCurrNode,’TasaOCuota’,FormatAmount(TempDocumentLine.”VAT %”));
           AddAttribute(XMLDoc,XMLCurrNode,’Impuesto’,FormatAmount(TempDocumentLine.”VAT %”));

           AddAttribute(XMLDoc,XMLCurrNode,’Base’,FormatAmount(TempDocumentLine.Quantity * TempDocumentLine.”Unit Price/Direct Unit Cost”));
           XMLCurrNode := XMLCurrNode.ParentNode;
         XMLCurrNode := XMLCurrNode.ParentNode;
       XMLCurrNode := XMLCurrNode.ParentNode;

       //New SAT Requirement end
       XMLCurrNode := XMLCurrNode.ParentNode;
     UNTIL TempDocumentLine.NEXT = 0;

  // Impuestos
   XMLCurrNode := XMLCurrNode.ParentNode;
   XMLCurrNode := XMLNewChild;
   IF IsCredit THEN

  // Impuestos->Traslados/Retenciones
   IF IsCredit THEN
   XMLCurrNode := XMLNewChild;

  IF TempDocumentLine.FINDSET THEN
       IF IsCredit THEN
       XMLCurrNode := XMLNewChild;
       IF NOT IsCredit THEN
         AddAttribute(XMLDoc,XMLCurrNode,’tasa’,FormatAmount(TempDocumentLine.”VAT %”));
         FormatAmount(TempDocumentLine.”Amount Including VAT” – TempDocumentLine.Amount));
       XMLCurrNode := XMLCurrNode.ParentNode;
     UNTIL TempDocumentLine.NEXT = 0;

In Local function CreateOriginalStr (changes in yellow).

WITH TempDocumentHeader DO BEGIN
   BlobManagement.Write(‘||’ + CompanyInfo.”CFDI Version No” + ‘|’);
   BlobManagement.Write(DateTimeFirstReqSent + ‘|’);
   IF IsCredit THEN
     BlobManagement.Write(FORMAT(‘E’) + ‘|’)
     BlobManagement.Write(FORMAT(‘I’) + ‘|’);
   BlobManagement.Write(GetPmtTermCode(“Payment Terms Code”) + ‘|’);

     GetCustomer(“Bill-to/Pay-To No.”);

  BlobManagement.Write(FormatAmount(SubTotal) + ‘|’);
   IF “Currency Code” <> ” THEN BEGIN
     BlobManagement.Write(FormatAmount(1 / “Currency Factor”) + ‘|’);
     BlobManagement.Write(“Currency Code” + ‘|’);
   BlobManagement.Write(FormatAmount(“Amount Including VAT”) + ‘|’);
   BlobManagement.Write(“Payment Method Code” + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.City) + ‘|’);  // LugarExpedicion

  IF CompanyInfo.”Bank Account No.” <> ” THEN
     BlobManagement.Write(RemoveInvalidChars(GetBankAccountLastFourChars(CompanyInfo.”Bank Account No.”)) + ‘|’);    // NumCtaPago

  BlobManagement.Write(CompanyInfo.”RFC No.” + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.Name) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.Address) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.County) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.City) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.City) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.County) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.”Country/Region Code”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.”Post Code”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.Address) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.County) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.City) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.County) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.”Country/Region Code”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.”Post Code”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(CompanyInfo.”Tax Scheme”) + ‘|’);

  BlobManagement.Write(Customer.”RFC No.” + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(“Bill-to/Pay-To Name”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(TempDocumentHeader.”CFDI Use”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(“Bill-to/Pay-To Address”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(“Bill-to/Pay-To County”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(“Bill-to/Pay-To City”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(Customer.”Country/Region Code”) + ‘|’);
   BlobManagement.Write(RemoveInvalidChars(“Bill-to/Pay-To Post Code”) + ‘|’);

  TempDocumentLine.SETRANGE(“Document No.”,”No.”);
   TempDocumentLine.SETFILTER(Type,'<>%1′,TempDocumentLine.Type::” “);
   IF TempDocumentLine.FINDSET THEN
       BlobManagement.Write(TempDocumentLine.”SAT Product/Service Code” + ‘|’);//New SAT Requirement
       BlobManagement.Write(FORMAT(TempDocumentLine.Quantity,0,9) + ‘|’);
       BlobManagement.Write(TempDocumentLine.”Unit of Measure Code” + ‘|’);
       BlobManagement.Write(TempDocumentLine.”No.” + ‘|’);
       BlobManagement.Write(RemoveInvalidChars(TempDocumentLine.Description) + ‘|’);
       BlobManagement.Write(FormatAmount(TempDocumentLine.”Unit Price/Direct Unit Cost”) + ‘|’);
       BlobManagement.Write(FormatAmount(TempDocumentLine.Quantity * TempDocumentLine.”Unit Price/Direct Unit Cost”) + ‘|’);
     UNTIL TempDocumentLine.NEXT = 0;

  IF TempDocumentLine.FINDSET THEN
       BlobManagement.Write(‘IVA’ + ‘|’);
       IF NOT IsCredit THEN
         BlobManagement.Write(FormatAmount(TempDocumentLine.”VAT %”) + ‘|’);
       BlobManagement.Write(FormatAmount(TempDocumentLine.”Amount Including VAT” – TempDocumentLine.Amount) + ‘|’);
     UNTIL TempDocumentLine.NEXT = 0;

  BlobManagement.Write(FormatAmount(RetainAmt) + ‘||’);


OK, what I need to install Dynamics NAV–Part 2

Lets start with the second part.

In the latest post I´ve talked about the memory for the middle tier but we need to check some things about the service.

Each NAV server needs 500 MB of memory to run plus 5 MB per user (active session) even if the sessions are idle and for every page the user opens, you need to allocate more memory.

The server instance has some special parameters to run and give service to the clients.

Data Cache Size – This parameter determines how much memory is used caching data. For a single tenant deployment 9 could be ok.


In NAV 2016 and higher the SQL – NAV interface use ADO.NET instead of ODBC so the resource consumption is lower than prior versions with ODBC.

The cache is a “store in memory” function so when a user read a record, if a second user wants to read the same record, gets it from cache because the cache is shared between the users of the same instance.

NAV use the cache when the system use the following functions


  • FIND

And there are two types of cache

Global Cache – for all users connected to a Microsoft Dynamics NAV instance.

Private cache – per user, per company, in a transactional scope. Data in a private cache for a given table and company are flushed when a transaction ends.

The cache that is used is determined by the lock state of a table. If a table is not locked than the global cache is queried for data; otherwise, the private cache is queried.

For a call to any of the FIND functions, 1024 rows are cached. You can set the size of the cache by using the Data Cache Size setting in the Microsoft Dynamics NAV Server configuration file. The default size is 9, which approximates a cache size of 500 MB. If you increase this number by one, then the cache size doubles. So, you need to consider how many records can bring back a simple SETRANGE function.

So, from here you can do the math and check how much memory do your Dynamics NAV server needs for one instance and add more memory for development and test instances (if they run in the same server).

OK, what I need to install Dynamics NAV–Part 1

Before the Dynamics NAV installation, we need to check some things related to the infrastructure, users, locations, etc.

Active Directory

Dynamics NAV use AD, SQL and more things like IIS so we need to figure how we can deploy the system, servers and other software. Also, we need to check if the electrical power is consistent or you have many blackouts; same for the internet connection.

Let’s check some scenarios starting with the simplest deployment

Microsoft says that we need an Active Directory. The Active Directory is a very important server because manages all the security and users. For this server you can purchase a low level server with maybe 4-8 GB of RAM, one Xeon processor and a small hard disk (don’t forget the Windows Updates, they need storage space).

This server is queried every time a user tries to access a network share, computer, printer or when you run an application (this is the basic explanation). Nobody recommends to install another service or application in an AD Server so you can buy a cheap server.

Don forget a very basic rule, if you put all the eggs in the same basket, you can lose all your eggs.

So, what can we do? Use to AD Server distributing the FSMO roles in two servers at least. In a Windows environment are five roles

  • Schema Master
  • Domain Naming Master
  • RID Master
  • PDC Emulator
  • Infrastructure Master

You can get more info about these roles in https://support.microsoft.com/en-us/help/223346/fsmo-placement-and-optimization-on-active-directory-domain-controllers

SQL Server

Another server that we need is the Database Server, this server has the SQL Server installation and the database files. We need to check some things for this server:

  • How many Dynamics NAV users are we going to have?
  • How many transactions?

For this server we can start from a dual Xeon based server with 16 GB of RAM for less than 25 users to whatever you can pay.

We need to check the best performance setup for the SQL server, are we going to use SSD or not?

For a SQL server it’s very important to choose the fastest RAID level, the RAID 0 is the fastest because multiple drives are reading and writing data but we don’t have fault tolerance. The fault tolerance can be achieved with RAID 1 which is a “mirroring” RAID. For Dynamics NAV the best approach is to use RAID 10 which combine speed and mirroring and its ideal for highly used database. The problem with the RAID 10 is that you need four drives at least but the SATA and SAS drives prices are getting lower and SSD too.

In SQL Server you need to take into account how many processors and cores you have. Why? Because you can split your log file in partitions and is better to have a log partition in a dedicated disk, as an example, if you have 8 cores, you can split your log file in 8 disk drives (in RAID 10 will be 16) for a better performance.

Also you need to check the SQL Recovery Model, simple, full or bulk logged. https://msdn.microsoft.com/en-us/library/ms189275.aspx

Each model has advantages and disadvantages but the real decision maker point is: do you have personnel with the technical knowledge for use full or bulk logged model? If you don’t have an experienced and dedicated person to do this job, choose the simple model and make daily basis full backups at least.

If you choose the simple model, you can forget the log file partition because the model automatically reclaims log space to keep space requirements small, essentially eliminating the need to manage the transaction log space.

When you are configuring the SQL server, you need to modify some settings in the server’s settings.

Max Server Memory

The buffer pool does not immediately acquire the amount of memory specified in min server memory. The buffer pool starts with only the memory required to initialize. As the Database Engine workload increases, it keeps acquiring the memory required to support the workload. The buffer pool does not free any of the acquired memory until it reaches the amount specified in min server memory. Once min server memory is reached, the buffer pool then uses the standard algorithm to acquire and free memory as needed. The only difference is that the buffer pool never drops its memory allocation below the level specified in min server memory, and never acquires more memory than the level specified in max server memory, this can severely reduce SQL Server performance, with one of our customers, their infrastructure admins top the Max Server Memory to 28 when the server has a 64 total with more than 50 free, all user start to complain until the max memory was free again.

Auto – Create Statistics

This parameter needs to be enabled to allow SQL to tune itself for a better performance.

Auto – Update Statistics

This parameter needs to be enabled to allow SQL to tune itself for a better performance. Also, many C/AL functions relies in these statistics.


Leave it enabled.

Max Degree of parallelism

NAV queries are OLTP type so it’s very important to set the MAXDOP in 1 for normal use, if you run maintenance jobs, you can change this parameter to 0, run maintenance and return to 1 when its finished.

As a better performance setting, the best setup can be OS and SQL Server in a disk, the database mdf file in another and the ldf in a third disk (all in RAID 10).

Dynamics NAV Server

Here we have the middle tier. Since Dynamics NAV 2013 to 2017, we have the three tier scenario, DB, NAV and client.

According to Microsoft, we need 2 GB of RAM for the server to give access to 5 users, a very small memory amount, the DB needs to be very small.

In a document posted by Microsoft “https://mbs.microsoft.com/Files/partner/NAV/SalesMarketing/MarketingCollateral/MicrosoftDynamicsNAV2013R2SingleTenantOnPremiseSizingGuidelines.pdf “, we have the next statement


So, the NAV Server needs less memory and we can purchase a little server. The document is a great analysis about the transactions and the process time and effort but they don’t check Web Client or Tablet/Phone app besides they don’t install IIS in the testing server.

In this moment we need to start to think about the client access methods, RoleTailored Client, Web client or Tablet/Phone client. Each one has its owns requirements in memory and can affect the server. In the littlest scenario, you install the IIS in the same NAV Server to publish NAV for all of clients and the Help Server too.

Dynamics NAV–Windows Server Compatibility

Hello all

I upgraded my laptop from Windows Server 2012 R2 to Windows Server 2016.

The upgrade process was a full hard disk wipeout and start from scratch.


for the SQL


Installed Dynamics NAV Versions

  • Microsoft Dynamics NAV 2017
  • Microsoft Dynamics NAV 2016
  • Microsoft Dynamics NAV 2015
  • Microsoft Dynamics NAV 2013 R2
  • Microsoft Dynamics NAV 2013
  • Microsoft Dynamics NAV 2009 R2


So, if you want to migrate your servers to the last OS you can do it without problems


Dynamics NAV e-Purchasing in Mexico

Here in Mexico, we have a government very interested in track all the operations between companies, that´s why we have electronic accounting and electronic invoicing.

With Dynamics NAV we have some problems, the “out-of-the-box” system lacks of some functionality to achieve the goal.

In this post, I’m gonna show the e-purchase functionality designed for the purchase area.

In Mexico we have the CFDI (Internet Digital Fiscal Bill), it’s a xml file with the Sales/purchase transaction information. We have several versions but in this year, the government add information related to the purchased items or services.

With this new data, we can add a special table called “SAT ProdServ Item Relation” and put in that table what we want to post in NAV when an xml file is processed.


What we need to do with this? We develop a new codeunit to process the xml files, we grab the files from a folder, read the file and fill a “cloned purchase order”


As you can see in the image, we make an Imported xml list with some functions:

Import Purch xml – This button grabs the xml files from a folder in your computer.

New Invoice from xml – Because we have all the info in the xml file, we can create a purchase invoice from the file.

Search & Match – Clicking in this button allows NAV to look for an existing Posted Purchase Invoice trying to match the xml to the posted invoices by RFC (Mexican Federal taxpayer registration), invoice amount (with a user-defined variation) and/or invoice date (also with a user-defined variation). If the system found a document, the posted invoice number is added to the list (green formatted line).

If you open the line, you can find the xml imported information that allow us to create a new vendor if we can’t find the RFC in the system.


With the new fields required by the last xml version (3.3) and the “SAT ProdServ Item Relation” we can fill the lines automatically.


Also, we added Job related information to add the purchase to a job and Dimension Control


AS you can see, with this development, we added support to Dynamics NAV to achieve a more automated process for purchase control without “touch” the NAV standard functionality or objects.

Extending possibilities

We added support for Standard Vendor Purchase Codes use with this objects; if you create a purchase standard code for the Vendor, we can use that (for G/L account) to make a Dimension distribution of the expense (as an example, cost center control).

Also we added a validation tool to check if the CFDI is valid using a Web Service of the government sending the required information (which we have in the import process of the xml file). If we have an approved answer for the service we can create the purchase, if we have a rejection from the service, the xml cannot create nor be assigned to a document in the system.

Dynamics NAV 2017 Events

Dynamics NAV 2017 extensions

Well, I’m gonna try to explain some things about extensions and events in Dynamics NAV

First of all, forget your previous assumptions on how do you need to develop anything in NAV, forget to change tables, pages, codeunits. The new development paradigm resides in “create everything new and attach those new things to events”.

Yes, you need to use (purchase) objects.

What we are going to achieve with this new approach? A more stable Dynamics NAV, less problems with developments, an easy upgrade path and maybe, just maybe, some repeatability in the code deployments (this always depends on customer´s ability to understand a standard process).

There is no better way to learn than with a real example.

This is the scenario, in Mexico (with all its stupid’s laws) you need to withhold taxes from certain types of vendors usually called professional services, lease or freights.

This withholding has different types and percentages, for example, if the vendor is a person who gives you a receipt of fees for his work you need to make the next operations

Amount (+) 1000
VAT 16% (+) 160
VAT Withholding 2/3 of VAT (-) 10.67 106.67
Income Tax Withholding (-) 10% 100
Total Amount 953.33

Besides the calculation, you need to store the withholdings in a specific G/L account

Remember you cannot modify the standard tables, pages or codeunits on NAV!!!

My approach is:

Create a table called Withholding Groups


Create a “alternate” G/L Account table and in the new table, add some fields to the G/L Account


It’s very important to keep G/L Account and the new G/L Account copy synchronized

To achieve this first create a new codeunit (I called eAccSubscribers).

Create a new function called OnGLAccInsert (I used this kind of names to allow a very easy understanding).


Once created, click in the Properties button in the menú


Local must be No

Event – select Subscriber

EventPublisherObject – I use table 15, btw you can type “t 15” and NAV complete the field when you change to the next field

Event Function – choose OnAfterInsertEvent from the list


As you see, you have triggers or events for some actions or processes in NAV

In the next window asking for confirmation click ok.

Now let’s write some code, the subscriber has 2 parameters added by NAV, a Rec and a Boolean, the rec is related to the G/L account table so I´ve added a new variable to my G/L Account table called eAccGL.

The code is

eAccGL.”No.” := Rec.”No.”;


What are we do to this moment? When a new G/L Account is inserted in the NAV Table 15, the code takes the t15.”No.” value and inserts the same data in the new table.

Now, you need to create another subscriber to complete the G/L Account information so we create a new function called OnGLAccModify with the next properties


Nav adds these parameters


We can use a TRANSFERFIELDS but I don’t need all G/L Account fields, just some, so I need to write every field one by one


and so on.

You can create an On Delete function.

Now save the codeunit and create a new G/L Account, then run the copied table and you´ll see the added account.

Now, you need to setup the G/L accounts and the withholding groups before start the tricky part, insert new lines before post execution code.

In previous versions you can create a codeunit to check if the G/L account needs to be withholded, and create the new lines in purchase line table and finally, you have some choices, create a button in the menu to call the create lines function (Page modification), add this behavior in the Release button (Codeunit Modification) or modify codeunit 90 (again codeunit modification).

Now we can create the same codeunit to check G/L Account, create lines, etc), but in this version we create a subscriber called CheckIFWHGLAccOnPost, the eventpublisherobject is the codeunit 90 and the event is OnBeforePostPurchaseDoc


Add some code to make all calculations and line insertions like this


Finally, test the function

Create Purchase Invoice and select the account with withholding


Post and check the lines