search

microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
744 stars 245 forks source link

AL0424 "The Multilanguage syntax is being deprecated. Please update to the new syntax" #5789

Closed RoieSantos closed 4 years ago

RoieSantos commented 4 years ago

Describe the bug Encounter this warning upon updating our extensions to BC16.

To Reproduce

  1. Make sure you are using the updated AL Language extension (5.0.254558)
  2. Create a page / pageextension having a property of "PromotedActionCategoriesML"

Screenshot image

Can we ask what is the best action needed to eliminate the warning. Thank you.

Versions:

AL Language: 5.0.254558 Business Central: 16.0.11209.0 (Preview)

nicolassaleron commented 4 years ago

Hi, This is not a bug but is related to the fact that ML properties should be used anymore.

Please have a look here : https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-work-with-translation-files

In your case, you should use PromotedActionCategories property and translate it in a XLIFF file.

qutreson commented 4 years ago

Closing this issue as a good answer and some links to the documentation were provided.

As a side note, this diagnostic is not reported by CodeCop, but by the AL compiler itself

RoieSantos commented 4 years ago

Hi qutreson,

Sorry for my late reply on this, We have try the above solution you sent and still not able to achieve the multi language functionality via translation files. Here are screenshot of our testing

  1. In our app.json we put the features : "TranslationFile" , "GenerateCaptions" and ExcludeGeneratedTranslations

image

  1. We also did copy the auto generated .xlf file to create a new en-AU.xlf file to support EN-AU language image

  2. In the newly created .xlf file we change the target-language to "en-AU" image

  3. In our Pageextension we only put Caption in the properties .. since the CaptionML or PromotedCategoryML is being deprecated. image

  4. We did double check if the translation file has the caption properties of the said pageextension image

Below are the result of the testing. image image

As per our testing only the language English(United States) "en-US" achieved the caption properties.

Please advise If we miss on some setup of we are lacking of something? Appreciate you reply

Thank You

qutreson commented 4 years ago

As per our online documentation (see here), you have to add a <target> element for each entry under the <source>. If you don't specify the target, then the entry is not considered.

RoieSantos commented 4 years ago

Hi qutreson,

Thanks for the info, It is all working now image

Appreciated your help

Thank you