[Bug]: Different protected variable name between w1 and IT in report Calculate Depreciation

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

1. Create a report extension for Calculate Depreciation.
2. Access the protected variable PostingDescription.
3. Publish the extension against a W1 environment.
4. Publish the same extension against an IT localization environment.
5. 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.

Start at the W1 and IT implementations of the Calculate Depreciation report and compare the protected variable declarations, especially PostingDescription and PostingDescriptionTxt. Done means the localized report exposes a consistent protected variable name or a documented backward-compatible approach, while preserving report-extension compatibility.