-
Notifications
You must be signed in to change notification settings - Fork 1k
Exclusion operator cannot be escaped #7828
Copy link
Copy link
Closed
Labels
area:docsCategory: SharePoint developer/development documentation relatedCategory: SharePoint developer/development documentation relatedarea:docs-commentCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devtype:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active work
Description
Metadata
Metadata
Assignees
Labels
area:docsCategory: SharePoint developer/development documentation relatedCategory: SharePoint developer/development documentation relatedarea:docs-commentCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devtype:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active work
Type
Fields
Give feedbackNo fields configured for issues without a type.
We should mention that the exclusion operator will be detected in a string and treated as the exclusion character regardless of quotes, and other measures.
For example if you are searching for 56nb3-45hf5-672345 you cannot find this string by using any of these:
'56nb3-45hf5-672345'
"56nb3-45hf5-672345"
56nb3--45hf5--672345 (or variants of this enclosed in quotes) Doubled the character for this sample because that is a way to get some other special characters recognized as string literals in a query.
The correct way to find this string is to replace the minus sign with spaces or the AND keyword.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.