web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Arabic Language Pack for Business Central

(4) ShareShare
ReportReport
Posted on by 355

I am trying to create an Arabic language pack (translation extension) for the Base Application.

Steps I followed:

  1. Created a new AL project.

  2. Added "features": ["TranslationFile"] in app.json.

  3. Added dependencies for System Application and Base Application with matching version (27.0.0.0).

  4. Added workspace settings:

al.generateXlf = true
al.generateXlfForDependencies = true
  1. Ran:

    • AL: Download Symbols

    • AL: Package

However, the generated file inside Translations is still empty:

<?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
  <file datatype="xml" source-language="en-US" target-language="en-US" original="ALProjectarbic">
    <body>
      <group id="body" />
    </body>
  </file>
</xliff>
I have the same question (0)
  • Suggested answer
    Pallavi Phade Profile Picture
    5,420 Super User 2026 Season 1 on at
     
    Can you check this below linkedin post it might solve your problem 
     
     
     
    Warm Regards
    Pallavi Phade 
    www.linkedin.com/in/pallaviphade131116
  • Suggested answer
    OussamaSabbouh Profile Picture
    12,965 Super User 2026 Season 1 on at
    Hello,
     
    Your XLF is empty because your project has no translatable content, so nothing gets generated — generateXlfForDependencies does not auto-extract Base App captions into your file. When translating the Base Application, you don’t generate strings from your app; instead, you must manually add a translated BaseApp XLF file into your Translations folder, set the correct target-language (e.g., ar-SA), ensure the <file original="..."> is not your app name, and use the original <trans-unit id> values from Base Application. In short: download or obtain the BaseApp XLF → translate it → place it in your translation extension → publish. The empty file you’re seeing is expected behavior.
     
    Regards,
    Oussama Sabbouh
  • LA-02071030-0 Profile Picture
    355 on at
     
    How i get BaseApp XLF file @Oussama Sabbouh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,005 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,148 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 557 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans