On-Prem SharePoint 2019 managed property not showing in people search query
I created an Employee Directory using the "People Search Query" I have managed properties for various fields and they all are imported and crawled and appear in the User Profiles. but I have 3 Managed properties that will not return data in a People Search Query, The data appears in the user profile but not in the search query, I configured the managed properties the same and have triple checked all the settings yet I still cannot search the managed property nor can it be added to my display template for the directory. The managed properties does have the "Include in Full-text Index" checked. any Suggestions as to what could be happening, thanks in advance.
Modern Experience: Highlighted Content - filter for two "and" connected managed properties
Modern Experience sites provide the "Highlighted Content" web part for dynamically filtering content. Filtering works like this: Title contains: project AND Created by is: John Doe AND Managed Property PercentageComplete contains: 100 If you select different filters, they are connected by "AND". But: If you select a filter twice it gets connected with "OR". That makes sense in this example: Title contains: project OR Title contains: order AND Created by is: John Doe AND Managed Property PercentageComplete contains: 100 But if you need to filter on two Managed Properties you struggle with this limitations: Title contains: project AND Created by is: John Doe AND Managed Property PercentageComplete contains: 100 OR Managed Property AssignedTo contains: [ME] Microsoft describes behavior here: https://support.content.office.net/de-de/media/15b638d5-fc1c-434d-8e5e-aa1809b819f7.jpg Has anyone an idea how to get around this?
Group Site Collections Columns not Crawled
Hi everyone, I added some custom columns in a group site collection but I can't find these columns as crawled properties in the search schema. All columns have content and the content is searchable. If I do the same with a classic teamsite colums are there as usual and I can map the properties in the search schema. Anyone with the same behavior?
