-
Notifications
You must be signed in to change notification settings - Fork 328
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
Values of columns are not shown in the search result webpart, but are filterable #2242
Comments
Hi @FHaslwanter, can you ensure the value is correctly saved in the details list column? It may be related to an other issue we have in the 4.7 release. you can also switch to debug layout to see if the value is present in the results. |
Hey @FranckyC, I just looked the value up in the debug mode. The value is present in the results like you can see in the screenshot attached. |
Does this happen to all columns, or only ones starting with a number? And if you reference the property directly and not via slots, does that work? |
Ok.. so seems an issue on our end where the mp starts with a number then. |
#2242 Support props starting with a number in slots
Fixed with 3034, and you can also use the mp directly with |
Version used
Ex: 4.7
Describe the bug
We currently upgraded from version 4.3 to 4.7 and had already some columns with metadata filled in to test PnP Modern Search. The values filled in before the upgrade are still shown in the columns webpart. Values from new columns are not shown, but filterable like seen in the screenshots.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The values of the column "Note" is shown and not only filterable.
Screenshots
"Auswahl" is a old column, which already existed before the upgrade. "Note" is the new column, which is filterable but the values are not shown as can be seen in the screenshot
Desktop (please complete the following information):
Additional context
We currently upgraded from V4.3 to V4.7. In V4.3 it worked perfectly fine.
The text was updated successfully, but these errors were encountered: