Fix effective permission filtering

[darjoo]

What & why

Filtering the Effective Permissions page could make the By Permission Set pane show wildcard permissions instead of the selected object's specific permission. This made the UI inconsistent even though effective authorization was calculated correctly.

Populate the permission buffer using the exact object ID first and fall back to wildcard object ID 0 only when no exact record exists. Exact records with blank permissions remain explicit exclusions and therefore also take precedence over wildcard grants.

Linked work

N/A - this internal fix is tracked by the Azure DevOps work item below.

AB#615963

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required - be specific: scenarios, commands, screenshots for UI changes)

• Built and installed the changed System Application, Base Application, and Tests-Permissions packages against Business Central 29.0.52770.0.
• Ran PopulatePermissionBufferPrefersSpecificObjectOverWildcard; it passed and confirmed an exact direct grant is displayed instead of an indirect wildcard grant.
• Ran PopulatePermissionBufferPrefersSpecificEmptyOverWildcard; it passed and confirmed an exact exclusion is displayed instead of a wildcard grant.

Risk & compatibility

Low risk. The change affects only the permission-set breakdown buffer used by the Effective Permissions UI; merged effective authorization remains unchanged. No schema, upgrade, telemetry, or feature-flag impact.

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

The temporary Record variable in the new test PopulatePermissionBufferPrefersSpecificObjectOverWildcard is named PermissionBuffer instead of TempPermissionBuffer. The file already follows the Temp-prefix convention elsewhere (e.g. TempPermissionSetBuffer), so this new declaration and its five usages in the method (var declaration and the calls to PopulatePermissionBuffer, SetRange, FindFirst, and the Assert.AreEqual comparisons) should be renamed to make clear it is an in-memory buffer, not a database write.

Knowledge:

• microsoft/knowledge/style/temporary-variable-temp-prefix.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.14.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

The temporary Record variable in the new test PopulatePermissionBufferPrefersSpecificEmptyOverWildcard is named PermissionBuffer instead of TempPermissionBuffer. The file already follows the Temp-prefix convention elsewhere (e.g. TempPermissionSetBuffer), so this new declaration and its five usages in the method should be renamed to make clear it is an in-memory buffer, not a database write.

Knowledge:

• microsoft/knowledge/style/temporary-variable-temp-prefix.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.14.4}