-
Notifications
You must be signed in to change notification settings - Fork 353
Filters with RefinableYesNo Managed Properties #4121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Bug confirmed |
This relates to #3998. As it's actually a data issue and not web part issue I'm note sure I want to fix it here. I did reach out to the service team but haven't heard anything back, but will ping them. |
I only last week figured out those RefinableYesNoxx MPs existing. Should it work properly with RefinableString? (I can't remember ever trying with Yes/No columns.) |
@sympmarc string should work.. and check what the actual string value is. |
@sympmarc can you check your findings again using v.4.16? I get the true/false texts in the Refiner, but they works as expected for me. |
@kasperbolarsen - Which do you want me to test? The RefinableYesNo MP or RefinableString? |
RefinableYesNo |
Yes, it seems to work in 4.16. Was it fixed in #3998 ? It still says True/False, but the filtering seems to work. Given it's a Yes/No, it feels like it should use those strings instead. |
I am working on localized values for the supported languages
…On Thu, Feb 27, 2025, 18:36 Marc D Anderson ***@***.***> wrote:
Yes, it seems to work in 4.16. Was it fixed in #3998
<#3998> ?
It still says True/False, but the filtering seems to work. Given it's a
Yes/No, it feels like it should use those strings instead.
—
Reply to this email directly, view it on GitHub
<#4121 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE5DXIRRQX534VX63FRURZ32R5EJ5AVCNFSM6AAAAABSKK52CWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBYGY2TINJWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: sympmarc]*sympmarc* left a comment
(microsoft-search/pnp-modern-search#4121)
<#4121 (comment)>
Yes, it seems to work in 4.16. Was it fixed in #3998
<#3998> ?
It still says True/False, but the filtering seems to work. Given it's a
Yes/No, it feels like it should use those strings instead.
—
Reply to this email directly, view it on GitHub
<#4121 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE5DXIRRQX534VX63FRURZ32R5EJ5AVCNFSM6AAAAABSKK52CWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBYGY2TINJWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…add translation method in LocalizationHelper #4121
…add translation method in LocalizationHelper #4121
Version used
Ex: 4.14.0
Describe the bug
When using a RefinableYes/No managed property as a filter, there are two issues:
To Reproduce
Detailed steps to reproduce the behavior:
ows_IsPolicy
andOWS_Q_BOOL_ISPOLICY
options)Expected behavior
Filtering should work
Screenshots
Filter

Results

Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: