Repository navigation
Conversation
Resolve CQWP URLs against the source collection, retain descendants with a bounded Path filter, and explicitly skip unsupported field-filter combinations rather than broadening their scope. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Use the native Highlighted Content title filter so a single literal Title Contains condition is ANDed with the recursive Path scope. Retain explicit skip diagnostics for unsupported operators, fields, multiple filters, and special query values. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Browser comparison showed the native search title predicate omitted a classic substring match and returned different assets. Restore the explicit scoped-field-filter guard instead of reporting an approximate mapping as supported. Retain the verified recursive CQWP scope fix. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
TaoziZ03
approved these changes
Nov 16, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Preserve a non-list Content Query Web Part's configured source-web scope when converting it to Highlighted Content, instead of silently broadening an actual web URL to the entire site collection.
~site/~sitecollectionURLs against the source collection, retaining complete nested-web paths.Pathmanaged-property restriction that includes descendants. Use the Contains operator (Path:"web/"), not WebId selection or Path equality, which exclude descendants.Unsupported combinations and fidelity limits
Scoped CQWP configurations with active field filters remain unsupported: they log a warning and use the existing skip-part exception path. The page migration continues, but the unsupported part is omitted. This is not a content-preserving migration of that part.
Simply combining Path with another managed-property filter is unsafe because Highlighted Content's flat search filters use OR. An attempted native Title Contains mapping preserved the scope conjunction but failed authenticated classic/modern result comparison, so it was withdrawn. The commit history is preserved; the final tree contains only the scope correction and explicit guard.
This PR does not claim complete CQWP result, content-category, substring-predicate, or ordering equivalence. In particular, classic notebook/folder/image results can still differ from the modern content categories.
Validation
net10.0andnetstandard2.0; existing package/analyzer warnings remain.The installed PowerShell module did not contain the local framework changes, so migration validation used the direct-local-library exception rather than claiming public
ConvertTo-PnPPageend-to-end coverage. All original fixtures and earlier outputs were retained.