PnP Modern Search V4 - Query Template Path:{\Site.URL}/<LibraryName> not working #1769
Comments
|
@FranckyC |
|
Yes I noticed that, you can use the Path:{site.absoluteUrl} token as a workaround for now. It should work. |
FranckyC
added a commit
that referenced
this issue
Feb 1, 2022
…If the token property is not found in the current context (client side resolution) then the value is let untouched for server side processing as a query variable + restricted manual character escape to curly braces only.
FranckyC
added a commit
that referenced
this issue
Feb 1, 2022
…If the token property is not found in the current context (client side resolution) then the value is let untouched for server side processing as a query variable + restricted manual character escape to curly braces only. (#1784)
|
@wobba @jameelrrs should be fixed in #1784. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
v4.5.3
Discussed in #1767
Originally posted by jameelrrs January 28, 2022
Hi,
To start with, PnP Modern Search WebPart is a great Solution. Amazing and appreciate the work done by the community.
What was working:
Using a dynamic token in the PnP - Search Results query template to point my results to a specific library, since we have multiple sites as below:
Path:{\Site.URL}/<LibraryName>Issue:
This was working fine until we planned to move to V4. However the same query doesn't work in version V4. Somehow, it adds " in the beginning or ending of the queryModifier and adding LIbraryName after it doesn't give results.
Is there something missing. Please suggest... Thanks in advance.
The text was updated successfully, but these errors were encountered: