Good afternoon,
We are using the User Profile Fields. For our particular domain, one of the fields that we are using is called Expertise. This field allows for having a list of string values separated by commas where the values are predefined and chosen from a checkbox list when editing Ex.: John Smith, Expertise field can be: Hiring Practices, Sales Management, Sales Coaching Tips.
When it is displayed in the User Profile Fields, each of those values (expertise) link to the Member Directory search.
What we were expecting is that the link will redirect with the correct URL that will allow for the automatic search. The problem is that when the expertise is multiple words, the generated seems not to be correctly leading to unexpected results. We understand that the reason is that some of the extension functions that the User Profile Fields use to generate and the HTML with the link embedded is failing to generate the proper URL. Let me explain better what I mean.
Check this first picture:
In the picture above, if you click in Customer Success (check the brown square area) within the field Expertise, we are expecting something like this (see picture below): 
Notice, the green square area. The URL shows Customer Sucess without the double quotes as expected and as result, the Customer Customer checkbox within the Expertise field is checked. However, instead of getting that, what we are actually getting is this:
Notice that URL shows Customer Sucess WITH the double quotes which is not expected, and as result, the Customer Customer checkbox within the Expertise field is not checked.
In some instances like when clicking to another more complex Expertise value such as Sales & Marketing Technology Stack within in the User Profile Fields widget, it will lead to no results at all.
Now, although we know that you have corrected this "multiple word search issue" in the People Search widget, it seems that you might need to apply the correction also within the User Profile Field specifically for the Expertise field.
I hope this context is clear enough. If you need more information, let me know.
Thanks in advance.
