I'm trying to filter a content search web part by using the current user's office value {User.Office} imported from AD.
I followed Ben N.'s example here: https://en.share-gate.com/blog/filtering-content-with-sharepoint-user-properties-search
In this example, there are two managed props used:
- Target - List column managed property
- {User.Office} - User profile managed property
My Query:
(path:"http://SharePoint/Site/Pages"
ContentTypeId:0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D001C98329396731B49A7CD1E5`5FDC5EB5B* OR ContentTypeId:0x01010A005BE79603E138A9439396512A9967A3BA*)DisplayHomeOWS=Yes TargetOWSCHCM:{User.Office}
Problem:
when I did a proof of concept with "Target" as a single choice value, everything resolves and I'm able to get the results based on my office location. However, when I changed the "Target" column to a multi-select choice field (Users can have more than one office location), it doesn't seem to resolve anything anymore.
Can anyone confirm that multi-select choice fields are being indexed in the search crawl? If so, can anyone let me know if I'm missing something?
I've run several full crawls after each managed property was added/mapped. Still not positive results.
Thanks in advance!