Shop Floor Insight
Advanced Inventory Count
NavXtender Language Support
Last Updated On
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.
- Navigate to the installation directory of NavXtender
- Open the file NavXtender.exe.config in a text editor
- Look for the property ‘CardPrefixCSV‘
- 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.
- Open NAV Development Environment
- Open the Object Designer via: Tools > Object Designer (Shift+F12)
- Go to Codeunit section
- Open (Design) the NavXtender Codeunit: 50011 NavXtenderAddLink
- Open Global Variables via: View > C/AL Globals
- Go to Test Constants
- Select a variable for the Page you want to configure, and open Properties (Shift+F4)
- Go into the ConstValueML values
- Add an ‘FRB‘ Property and add the translation in the Value (example used is for FRB (French Belgium), simply replace with desired language)
- Go to the Page section
- Open (Design) the Page/Card you wish to support. In this example I chose the “Currency Card”
- Open the Properties (Shift+F4)
- View the CaptionML Propery
- Expand the values to find the value you need.
- 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