Forum Discussion
Modern Team Sites - Highlighted Content filter not work
John_Sanders wrote:Thanks for the feedback David. I have heard from a few folks that we should support standard operators, like [me]. We don't currently support that, you need to use the display name. I've added this to our backlog. Your second example in managed properties works for me if I filter by your example ContentClass = STS_Site, with source = All Sites. Is it working for you now, or still failing?
Hi John_Sanders,
I see if I use query variables like {User} the variable is expanded when examining the returned JSON, but no results are coming back. Any good explanation to this? I see the web part sends a couple of custom props as well, and are they blocking the execution of good old query variables even though they seem to get expanded?
Hi Mikael Svenson and John_Sanders I found one variable that did work with the EditorOWSUser managed property; {User.Email} will show the correct results.
I miss the oportinity to filter by {today} - anyone know when I can expect this to work?
- John_Sanders
Microsoft
Ulrikke Akerbæk can you give us the full scenario?
In HC today you can filter by "Recented changed" or "Recently added", and then set "Since" to "Today". Sounds like that's either too hideen, or not meeting your needs.
Love to hear how we can improve.
Thanks.
Another common scenario would be to list future events, meaning things happening today or in the future. Hence the "since" option is not useful, we would also need a before.
Or, having the advanced option would solve all edge cases as us old skool KQL peeps can craft whatever we want :D
That said, we also hope you are looking to fix the () bug around contenttypeid, which currently blocks the usage of the web part for almost any scenario. cc Elsa Naumann
- Yep, agreeing with you both - was just testing this now to no avail.
Agree, when picking a date field to filter on it will only accept dates, not valid query variables or KQL keywords like today, yesterday etc.
The highlighted content web part needs some adjustments for sure.
- John_Sanders
Mikael Svenson - I've added this to our backlog for managed properties. Thanks for pointing it out.
We've discussed the idea of adding an "Advanced" tab in the future that allows you to enter your own KQL, which could be how we enable this (as opposed to supporting some things in the "simple" UX, but not others.
Would love to know your thoguths on this approach, vs adding standard operators supported in KQL (e.g."today") to the date fields.
