First of all, as you might have read from my earlier blog, I hastily promised that I will no longer post NAV2018 CU teardowns any more, but it seems that Business Central and NAV2018 are walking their own paths now, so I will continue writing these until further notice.
CU14 is a minor update from MS. it includes small changes to functionality, basically concentrating on the things you can read from MS blog. Mostly these are small VAT handling fixes and typo fixes.
NAV 2018 CU14 does not include any new features. I could find no new objects or new functionality hidden with the update.
There is not much changed or addd functionality.
As usual, this CU includes new Integration events, but the quantity seems to be decreasing. There is only a few of them this time, which suggests that NAV 2018 is getting "mature" in regards of published events. This is good news!
I found a feature that I had totally missed earlier. It seems that somewhere during the NAV2018 journey MS added a nice new feature from North American localization called Freight. It manisfests itself with a new field in Sales and Receivables Setup called "Freight G/L Acc.No". User can add a G/L number here, but what then?In NA version Sales Order header has a field where you can insert freight amount, and the functionality adds a G/L line into the order somewhere during the handling of the order.The only place where InsertFreightLine is used was in Codeunit 5343 CRM Sales Order to Sales Order. Perhaps this feature can only be used with CRM orders then.
Bummer! I would have liked to see this in standard NAV.Maybe I have to download NA version and give the Sales Order page a closer look...
Earlier introduced Codeunit 10 Type Helper has been added a function called FormatDateWithCurrentCulture. This is a function that uses a mscorlib .NET dll call for System.DateTime. As the function call suggests, the result is a locally formatted datetime as a text string. This is something we all can now use to tackle regional formatting challenges in NAV. This function is now used in excel transfers, and greatly enhances localised functionality.This issue was reported to MS by our financial consultants Marjo Kellomäki and Jyrki Rantalainen. This issue had actually been existing for a very very long time. I remember that starting at least from NAV 4.2FI we have had standard instructions to change regional settings in a very special way on all workstations that use excel integration. Especially thousand separator has been an issue. Standard Windows thousand separator in Finland is ascii 127 (or 255) which is "blank character". In order to fix excel transfers in old versions this separator had to be changed to space, ascii 32.