NavXtender Language Support

You are here:
NavXtender natively support’s English (ENC/ENU), French Canada (FRC) and Spanish (ESP) at this time. In order for NavXtender to attach a link to a record for a different language, you (or your NAV Partner / Developer) will have to make some changes in the NavXtender Codeunit to add the translations. Step 1: add translations to NavXtender config.
  1. Navigate to the installation directory of NavXtender
  2. Open the file NavXtender.exe.config in a text editor
  3. Look for the property ‘CardPrefixCSV
  4. Add a translation in your language for the words ‘New’, ‘Edit’, and ‘View’. Ensure they are separated by comma’s, and no spaces between words.
Step 2: add translations to NavXtender web service codeunit.
  1. Open NAV Development Environment
  2. Open the Object Designer via: Tools > Object Designer (Shift+F12)
  3. Go to Codeunit section
  4. Open (Design) the NavXtender Codeunit: 50011 NavXtenderAddLink
  5. Open Global Variables via: View > C/AL Globals
  6. Go to Test Constants
  7. Select a variable for the Page you want to configure, and open Properties (Shift+F4)
  8. Go into the ConstValueML values
  9. Add an ‘FRB‘ Property and add the translation in the Value (example used is for FRB (French Belgium), simply replace with desired language)
The value to add will depend on the page, this must match the Page Caption text for the relevant Page/Card. You can do this manually if you know the translations/locale, however the text must exactly match the page title in order for NavXtender to be able to correctly detect the page. You may want to verify or copy the values from Pages with the following method. (This will need to be done for each page you wish to enable record link storage). To find the exact text:
  1. Go to the Page section
  2. Open (Design) the Page/Card you wish to support. In this example I chose the “Currency Card”
  3. Open the Properties (Shift+F4)
  4. View the CaptionML Propery
  5. Expand the values to find the value you need.
A recommended approach would be to add this do this for one page, ensure it works, then continue on to others. Trouble shooting:
  • If NavXtender is failing to detect a droppable page (can’t drop and/or button won’t show), then double check the CardPrefixCSV in Step 1 includes language that matches the page title.
  • If the translation is correct, links should work correctly. If a link fails with that ‘Record links not supported for this page’ message, double check the translation for that page to ensure it is correct as seen in Step 2.
  • If you have a multi-language environment (users of different languages on the same service), the codeunit language will be based off the service language only. A work around involving multiple services is available, where you create a service for each language pointed to the same DB, and point the users of NavXtender to the relevant service.
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Need help?

Leave A Comment

Go to Top