Book Image

Dynamics 365 Business Central Development Quick Start Guide

By : Stefano Demiliani, Duilio Tacconi
Book Image

Dynamics 365 Business Central Development Quick Start Guide

By: Stefano Demiliani, Duilio Tacconi

Overview of this book

Microsoft Dynamics 365 Business Central is the new SaaS ERP proposition from Microsoft. This latest version has many exciting features guaranteed to make your life easier. This book is an ideal guide to Dynamics 365 Business Central and will help you get started with implementing and designing solutions for real-world scenarios. This book will take you through the fundamental topics for implementing solutions based on Dynamics 365 Business Central (on-premise and SaaS). We'll see the core topics of the new development model (based on extensions) and we'll see how to create applications with the new Microsoft ERP proposition. The book begins by explaining the basics of Dynamics 365 Business Central and the Microsoft ERP proposition. We will then cover topics such as extensions, the new modern development model of Visual studio code, sandboxes, Docker, and many others. By the end of the book, you will have learned how to debug and compile extensions and to deploy them to the cloud and on-premise.You will also have learned how to create serverless business processes for Microsoft Dynamics 365 Business Central.
Table of Contents (13 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Handling translations with XLIFF files


Dynamics 365 Business Central is multi-language enabled, which means that you can display the user interface in different languages and you need to support that feature when developing extensions.

With classic NAV development in C/SIDE, you manage the multi-language captions by using the CaptionML property: https://docs.microsoft.com/en-us/dynamics-nav/captionml-property.

As you've probably seen, in our previous extension, we haven't managed the translation of the captions that we have in our code. You can't find lines with the CaptionML set, for example the following:

field(2; Description; Text[50])
        {
            DataClassification = CustomerContent;
            CaptionML = ENU = 'Description', ITA = 'Descrizione';
        }

But instead, you'll find the following:

field(2; Description; Text[50])
        {
            DataClassification = CustomerContent;
            Caption = 'Description';
        }

So, how we do handle multi-language support for...