microsoft/knowledge/privacy/register-integration-in-privacy-notice-registrations.md seems to be outdated
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open microsoft/knowledge/privacy/register-integration-in-privacy-notice-registrations.md and review the registration example against the issue’s stated event publisher and helper usage. Update the document and its matching code example so they use the Privacy Notice Registrations event and the higher-level helper, then verify the outdated guidance is gone.
Written by the indexing model from the issue text.
Description
Knowledger in microsoft/knowledge/privacy/register-integration-in-privacy-notice-registrations.md and matching good code example seem to be outdated. There is no published event in codeunit "Privacy Notice Registrations", the event is in "Privacy Notice".
This leads to advices like this:
Major — Privacy Notice registered on the wrong codeunit
The event subscriber that registers the GitHub Copilot integration subscribes to Codeunit::"Privacy Notice" instead of Codeunit::"Privacy Notice Registrations":
// ❌ current — wrong publisher
[EventSubscriber(ObjectType::Codeunit, Codeunit::"Privacy Notice", OnRegisterPrivacyNotices, '', false, false)]
local procedure RegisterGHCopilotPrivacyNotice(var TempPrivacyNotice: Record "Privacy Notice" temporary)
The OnRegisterPrivacyNotices event is published by Codeunit "Privacy Notice Registrations", not by Codeunit "Privacy Notice". Subscribing to the wrong codeunit means this procedure never fires, so the SMAGHCopilot integration is never added to the tenant's Privacy Notices registry. As a result, GetPrivacyNoticeApprovalState('SMAGHCopilot') at line 38 will always return a non-Agreed state, and every call to ImportUsageData will fail with PrivacyNoticeNotAgreedErr — even after an administrator tries to approve it on the Privacy Notices Status page, because the notice was never registered to begin with.
Additionally, the BCQuality reference implementation uses the higher-level PrivacyNotice.CreatePrivacyNoticeForIntegration(...) helper rather than manually initialising the temporary record.
Fix:
[EventSubscriber(ObjectType::Codeunit, Codeunit::"Privacy Notice Registrations", OnRegisterPrivacyNotices, '', false, false)]
local procedure RegisterGHCopilotPrivacyNotice(var TempPrivacyNotice: Record "Privacy Notice" temporary)
var
PrivacyNotice: Codeunit "Privacy Notice";
begin
PrivacyNotice.CreatePrivacyNoticeForIntegration(
GHCopilotIntegrationIdTok, 'GitHub Copilot Metrics');
end;
BCQuality reference: microsoft/knowledge/privacy/register-integration-in-privacy-notice-registrations.md
which in its turn confuses the agent that tries to fix it.
- Dominant language
- AL
- Stars
- 213
- Forks
- 121
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 33
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/BCQuality
-
Difficulty 1/5 1-3 hours Newbie friendliness 91/100
-
Invalid Assertion Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in microsoft/BCQuality
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100