learn-build-service-prod[bot]
commented
1 year ago Learn Build status updates of commit ecef981:
:bulb: Validation status: suggestions
| File | Status | Preview URL | Details |
|---|---|---|---|
| dynamics-nav-app/admin-responding-to-requests-about-personal-data.md | :bulb:Suggestion | Details |
dynamics-nav-app/admin-responding-to-requests-about-personal-data.md
- Line 17, Column 476: [Suggestion: link-broken - See documentation]
Link '/dynamics-nav/classifying-data' points to a page that doesn't exist. Check the path or URL and update the link. - Line 41, Column 1: [Suggestion: link-broken - See documentation]
Link '/dynamics-nav/classifying-data' points to a page that doesn't exist. Check the path or URL and update the link.
For more details, please refer to the build report.
Note: Links can become broken if there are changes on the target sites. If you think the validation result is a false alarm, please use SiteHelp with option 'Content authoring and publishing -> False alarm on broken link validation' to report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
A Pull Request has been made from the Learn Platform's Metadata Management System to update allowlist-driven metadata. Please review and merge this Pull Request within 5 days.
If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update. This includes bypassing the Repository's Branch Policy, including if Review Required is enabled. Fixing#713729 Retag ms.prod excel to ms.service excel - MicrosoftDocs/nav-content
Why we make metadata updates The Learn Content Architecture team manages business-facing reporting taxonomies that enable analytics for OKR reporting and content portfolio management. These taxonomies are referred to as ms.* allowlists. Allowlist values populate metadata attributes.
We regularly review allowlists to ensure they are accurate, useful, and align to curr ent business needs. Updates to allowlists and allowlist-driven metadata make reports cleaner, easier to use, and more consistent.
We regularly review allowlists to ensure they are accurate, useful, and align to current business needs. Updates to allowlists and allowlist-driven metadata make reports cleaner, easier to use, and more consistent. Since metadata attributes are included in the YAML header, certain types of allowlist changes require making content updates.
How does this affect me? Once changes to allowlist-driven metadata are merged, standard dashboards and reports will reflect new values. You'll need to use new filter values in those dashboards and reports. If you have custom dashboards or Kusto queries, you might need to update those as well.
Frequently Asked Questions Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.
How can I revert a Pull Request that has been merged and created an unexpected issue?? Whether a PR has been merged manually or automatically, you can revert it if an issue arises. See Reverting a pull request - GitHub Docs.