Forum Discussion
Modern Pages - Highlighted content not filtering search results for pages in other site collections
MicrosoftFrom reading your comment "The near duplicate trimming in SP search is just not a good thing- and seems to ignore Title all together for modern pages at least. Create multiple articles as modern pages, give them unique titles but write the same content in all, and only one will roll up." I think you're saying that searching directing on the site trims all the other pages with different titles and identical content inside (and it also removed them in HC)?
So you're asking for a new "Expert Settings" area (potentially), where users that know what they're doing could off-check "Near duplicate trimming"? Since I'm guessing normal folks wouldn't even think to off-check that as an option. Is that right?
John_Sanders I noticed the web part now has a property in the backing JSON named advancedQueryText which seems to be the query template. Are there plans to expose this in the web part property panel? If so, it would be an awesome pre-xmas gift :)
Wrote about my investigations at http://www.techmikael.com/2017/11/modifying-query-template-for.html
- Awesome news and like the direction this is going. Validation is a hard nut, and I'm guessing it's not too important as we've never had that in any web part using KQL before.
In my mind you could have a collapsed Advanced web part setting, where you have to check off to use advanced, and then you are sort of at the point of the CSWP - your own KQL, or the UI - no mix and match. If you check to use advanced, the other controls should also be disabled - which I believe is possible with the current SPFx settings.
That way you could link to https://docs.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference and https://technet.microsoft.com/en-us/library/jj683123(v=office.16).aspx and be all set - more or less ;) - John_Sanders
Some nice sleuthing there Mikael Svenson. We are working on a way that you can enter more advanced query terms in the property pane.
1) the UX is behind a flight at the moment as it's not yet ship ready (e.g. is it too confusing for non power users, need to craft an updated/linked help article, should we attempt to do validation in the long run, etc.).
2) It also immediately brings up the desire to do custom data mapping of custom property X to position Y in the card layouts (since you can now query and retrieve property custom property X).
We're working on it...
