Strange NAV2018 Extension publishing error

Today I took an (v1) extension, that had worked perfectly on NAV2017 and tried to publish it to a NAV2018 instance, resulting in a cascade of errors:

[23462397] You have specified an unknown variable.SDefine the variable under 'Global C/AL symbols'.

I have specified an unknown variable, then SDefine the variable? Strange?

It turned out, that the offending variable was called “S¢gning” (Old danish code, with messed up character conversion), so the character ¢ after the S messes up the error description. The object compiles and work fine in NAV2018 FINSQL, so it seems that Microsoft have changed the way a V1 Extension is compiled at publish time that has a stricter character requirements. Changing into the correct Danish ø does not help.

Update: This was an interesting experience in wrong combinations of regional settings on servers vs. the quirkiness of the .TXT format. After going through the entire workflow and fixing setting I’m back in business 🙂

(Article added here for helping people when googling errors like this).

First wave of GDPR support in NAV

Yesterday Microsoft released a new batch of Cumulative updates for all supported versions (2015-2018) of Microsoft Dynamics NAV.

As part of this CU, the support for GDPR is surfacing:

The NAV platform will have new classification properties on tables and fields. This will help you organize and mark all the places in your database where you have sensitive information that should be covered by your company GDPR compliance.

I suspect we\ll see much more GDPR support in upcoming UCs.

NAV2013R2 and older are out of support and will not receive any GDPR updates. I’m looking into a way for these versions to get the features, reach out to me on twitter if you need this.