| bc-version |
domain |
keywords |
technologies |
countries |
application-area |
|
|
style |
| label |
| locked |
| translation |
| token |
| url |
| json |
| xml |
|
|
|
|
Set Locked = true on Labels that must not be translated
Description
A Label is by default surfaced to translators and rewritten per locale. That is wrong for strings that are not natural language: HTTP verbs (GET, PUT), URL fragments, JSON/XML snippets, content-type strings, GUIDs, application keys, and field tokens used by integrations. Translating these breaks the integration the moment a non-English tenant runs the code. The Locked = true parameter on the Label declaration tells the translation pipeline to keep the string verbatim, and signals to reviewers that the value is part of a wire-level contract rather than display text.
Best Practice
Pair Locked = true with the Tok suffix for short tokens (GetMethodTok: Label 'GET', Locked = true;) and with the Txt suffix for telemetry strings that contain format placeholders but should not be localized. The Locked parameter and the Tok / Txt suffix together make the intent unambiguous.
See sample: label-locked-for-non-translatable.good.al.
Anti Pattern
HttpsUrl: Label 'https://example.com'; or ContentTypeTok: Label 'application/json'; declared without Locked = true. The translator localizes them, the integration fails in production for the affected tenant, and the failure is invisible in the developer's English-locale tests.
See sample: label-locked-for-non-translatable.bad.al.