Skip to content

Enforce permissions when reviewing orphaned extension data - #9844

Open
jhejlsberg wants to merge 1 commit into
releases/28.xfrom
features/633514/orphaned-extension-data-permissions
Open

Enforce permissions when reviewing orphaned extension data#9844
jhejlsberg wants to merge 1 commit into
releases/28.xfrom
features/633514/orphaned-extension-data-permissions

Conversation

@jhejlsberg

@jhejlsberg jhejlsberg commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

What & why

Backports PR #9569 to 28.x.

Ensure marking orphaned extension data as reviewed consistently calls CheckPermissions() from both the notification and page actions.

Linked work

Fixes AB#633514

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.

No tests added; both entry points now share the same implementation.

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

  • Installed and uninstalled an extension; verified the orphaned-data notification appeared.
  • Marked data as reviewed from both the notification and the Delete Orphaned Extension Data page; verified the reviewed status was updated.
  • Reinstalled and uninstalled the extension; verified the reviewed status was reset.

Risk & compatibility

Permission enforcement is stricter on OpenPage.

<!--
Thanks for contributing to BCApps!

A few things before you hit "Create pull request":
- Your PR must link to an approved issue. New here? See CONTRIBUTING.md.
- You must have built and run your change yourself. CI is a safety net,
not a substitute.
- If you used AI or an agent to write this PR, you are still the author.
Read the diff,
  build it, and try it before requesting review.

Contributing guide:
https://github.com/microsoft/BCApps/blob/main/CONTRIBUTING.md
Local dev environment:
https://github.com/microsoft/BCApps/blob/main/LOCAL_DEV_ENV.md
-->

## What & why

<!-- A few sentences: what does this change do, and what problem does it
solve? -->

Ensure marking orphaned extension data as reviewed consistently calls
CheckPermissions() from both the notification and page actions.

## Linked work

<!-- Required: link an approved GitHub issue using "Fixes #<number>".
Microsoft contributors: also link the ADO work item with "AB#<number>"
if you have one. -->

Fixes
[AB#633514](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/633514)

## How I validated this

- [x] I read the full diff and it contains only changes I intended.
- [x] I built the affected app(s) locally with no new analyzer warnings.
- [x] 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.

No tests added; both entry points now share the same implementation.

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

<!-- Example:
- Ran the new "Post and Send" action on a sales invoice in a fresh
container; document posted and email queued (see screenshot).
- New unit tests in MyFeatureTest.Codeunit.al pass locally; full module
test suite green.
- No tests added because change is comment-only / refactor with existing
coverage. -->

- Installed and uninstalled an extension; verified the orphaned-data
notification appeared.
- Marked data as reviewed from both the notification and the Delete
Orphaned Extension Data page; verified the reviewed status was updated.
- Reinstalled and uninstalled the extension; verified the reviewed
status was reset.

## Risk & compatibility

<!-- Anything reviewers should watch for: breaking changes, upgrade/data
impact, permissions,
telemetry, feature flags, follow-up work. Write "None" if there's
nothing to call out. -->

Permission enforcement is stricter on OpenPage.
@jhejlsberg
jhejlsberg requested review from a team July 30, 2026 09:19
@jhejlsberg
jhejlsberg marked this pull request as draft July 30, 2026 09:20
@github-actions github-actions Bot added the Integration GitHub request for Integration area label Jul 30, 2026
@github-actions github-actions Bot added this to the Version 28.4 milestone Jul 30, 2026
@jhejlsberg
jhejlsberg marked this pull request as ready for review July 30, 2026 12:15
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

⚠️ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AL: System Application Integration GitHub request for Integration area

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants