Skip to content

Updated support of operators in SharePoint Online #2

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Updated support of operators in SharePoint Online #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 9 additions & 23 deletions docs/general-development/fast-query-language-fql-syntax-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,33 +269,13 @@ Not applicable.
> [!NOTE]
> In SharePoint, the **ANY** operator is deprecated. Use the **OR** operator instead.

Similar to the [OR](#or) operator except that the dynamic rank (the relevance score in the result set) is affected by neither the number of operands that match nor the distance between the terms in the item. The operands may be a single term or any valid FQL sub-expression.

The dynamic ranking component for this part of the query is based on the best matching term within the **ANY** expression.

> [!NOTE]
> he difference from **OR** is related only to the ranking within the result set. The same total set of items will match the query.

#### Syntax

`any(operand, operand [,operand]*)`

#### Parameters

Not applicable.

#### Examples

The following expression matches items for which the default full-text index contains "cat" or "dog".

If the index contains both "cat" and "dog", but "cat" is considered a better match, the 'item's dynamic rank will be based on "cat" with no consideration given to "dog".

`any(cat, dog)`

### COUNT

Specifies the of number query term occurrences an item must include for the item to be returned as a result. The operand may be a single query term, a phrase, or a wildcard query term.

> [!NOTE]
> This operator is not available in SharePoint Online in Microsoft 365

#### Syntax

`property-spec:count(operand [,from=<numeric value>, to=<numeric value>])`
Expand Down Expand Up @@ -425,6 +405,9 @@ Using the **FILTER** operator automatically implies the following for the specif
> **Tip:**
> If you use the **STRING** operator inside a **FILTER** expression, by default, linguistics is disabled. You can enable linguistics processing within each **STRING** expression inside **FILTER** by using the operand `linguistics="ON"`.

> [!NOTE]
> This operator is not available in SharePoint Online in Microsoft 365. The operator is accepted, but ignored.

#### Syntax

`filter(<any valid FQL operator expression>)`
Expand Down Expand Up @@ -726,6 +709,9 @@ The **STRING** operator can also be used as a type conversion. The query `string
> [!NOTE]
> In SharePoint the _minexpansion_, _maxexpansion_ and _annotation_class_ parameters for the **STRING** operator are obsolete.

> [!NOTE]
> In SharePoint Online in Microsoft 365, the _weight_, _linguistics_, and _wildcard_ paramters for the **STRING** operator are not supported. The parameters are accepted but ignored.

#### Examples

**Example 1.** Because the default string mode is " **PHRASE** ", each of the following expressions returns the same results.
Expand Down