Describe the issue
The Calculate Depreciation report exposes different protected variable names between the W1 application and the IT localization.
In the W1 version of the report, the protected variable is named:
PostingDescription
However, in the IT localization, the corresponding variable is named:
PostingDescriptionTxt.
This inconsistency creates issues for report extensions that rely on protected variables. An extension developed against W1 cannot be compiled or reused against the IT localization without code changes.
For protected variables that are intended to be consumed by extensions, the naming should be consistent across the base application and localizations.
Expected behavior
The Calculate Depreciation report should expose the same protected variable name in both W1 and IT localization layers.
For example, the IT localization should use PostingDescription, matching the W1 implementation, or provide a backward-compatible approach that ensures extension compatibility across versions.
Steps to reproduce
- Create a report extension for Calculate Depreciation.
- Access the protected variable
PostingDescription.
- Publish the extension against a W1 environment.
- Publish the same extension against an IT localization environment.
- Observe that the variable name differs (
PostingDescription vs PostingDescriptionTxt), causing compatibility issues.
Additional context
This appears to be an inconsistency between the W1 application and the IT localization implementation of the same report.
Having different names for equivalent protected variables makes it harder to create reusable extensions that work across localized versions of Business Central.
Describe the issue
The Calculate Depreciation report exposes different protected variable names between the W1 application and the IT localization.
In the W1 version of the report, the protected variable is named:
PostingDescriptionHowever, in the IT localization, the corresponding variable is named:
PostingDescriptionTxt.This inconsistency creates issues for report extensions that rely on protected variables. An extension developed against W1 cannot be compiled or reused against the IT localization without code changes.
For protected variables that are intended to be consumed by extensions, the naming should be consistent across the base application and localizations.
Expected behavior
The Calculate Depreciation report should expose the same protected variable name in both W1 and IT localization layers.
For example, the IT localization should use
PostingDescription, matching the W1 implementation, or provide a backward-compatible approach that ensures extension compatibility across versions.Steps to reproduce
PostingDescription.PostingDescriptionvsPostingDescriptionTxt), causing compatibility issues.Additional context
This appears to be an inconsistency between the W1 application and the IT localization implementation of the same report.
Having different names for equivalent protected variables makes it harder to create reusable extensions that work across localized versions of Business Central.