Suppress AL0432 obsolete warnings for AllObj."Object Name" field

[SBalslev]

Summary

Suppresses AL0432 compiler warnings introduced by platform PR 246852, which marks AllObj."Object Name" as ObsoleteState = Pending.

Applied #pragma warning disable/restore AL0432\ around all references in 4 codeunits:

• PermissionImpl.Codeunit.al
• RetenPolAllowedTblImpl.Codeunit.al
• WebServiceManagementImpl.Codeunit.al
• TestSuiteMgt.Codeunit.al

Related

• Work item: AB#485120
• Platform PR: 246852
• Companion NAV repo PR: pending (depends on this PR being merged first)

[github-actions]

AL Documentation Audit

Documentation gaps were detected in the following apps:

• Permission-Sets: 0% documentation coverage
• Retention-Policy: 0% documentation coverage
• Test-Runner: 4% documentation coverage
• Web-Service-Management: 94% documentation coverage

To generate documentation, run /al-docs init or /al-docs update using GitHub Copilot CLI or Claude Code.
This review is for awareness to help keep documentation in sync with code changes. It is okay to dismiss this request.

[github-actions]

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.

---

🔄 How to trigger a new status check:

1. 📤 Push a new commit to the PR branch, or
2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Upgrade} \quad \color{gray}{\texttt{\small Iteration\ 1}}$

AL0432 suppression hides obsolete API usage

Four separate #pragma warning disable AL0432 / restore AL0432 pairs are added around calls to RetentionPolicyLog.LogInfo, LogError, and LogWarning. Suppressing this warning silently indicates these API overloads are pending obsolescence, but no migration path or timeline comment is provided, making it easy to miss when the API is eventually removed.

Recommendation:

• Add an inline comment for each suppression block referencing the replacement API and the target version by which migration must occur. Prioritise migrating to the non-obsolete overload.

#pragma warning disable AL0432 // TODO: Migrate to RetentionPolicyLog.LogInfo(LogCategory(), ..., Format(TableId)) before BC vXX
    RetentionPolicyLog.LogInfo(...);
#pragma warning restore AL0432

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why}