Nav2018 changed textconstant comment behavoir

janpieter
janpieter Member Posts: 298
edited 2017-12-03 in NAV Three Tier
In a textconstant you could use special 'Comment' language translations. These were stored as language '@ @ @'. Before 2018 when you provided no other languages using this textconstant, this would result in the value in the 'comment' language. In 2018 it will return an empty string if you don't provide any translations.

Not so happy about this change. It was a perfect way to store 'hard' text with no need for translation. For anyone using this system the same as I did, be aware your code will run differently. Now you will have to at least put this in the 'ENU' section.
In a world without Borders or Fences, who needs Windows and Gates?

Comments

  • Slawek_Guzek
    Slawek_Guzek Member Posts: 1,692
    edited 2017-12-03
    For hardcoded texts I have always been using a one-liner functions returning the text, and further down in the code referenced the function. Worked well long before the 'Comment' language capability was added.

    Thank you for warning us. It is not nice to face code breaking changes between versions.
    Slawek Guzek - www.yitron.co.uk
    Business Central, MS SQL Server, Wherescape RED;

Categories