Connections

The 'Data Visualizer' Web Part can be used alone but also connected to other Web Parts:

Input query text

The input query text can be either static or dynamic. In all cases, this value can be used using the {inputQueryText} token. See tokens for more information.

Static value

It corresponds to a free text keywords that you want to pass to your data source:

This value will be applied every time to your data source.

Dynamic value

You can connect a dynamic value from the page environment (ex: a query string parameter, the top bar search box, etc.) or a search box already added to the page.

Optionaly, you can set a default query text when there is no value for the connected source (ex: an empty search box at page load).

Filters Web Part

Send available filters for the current data source to a Data Filters Web Part to be rendered. This is a two-ways connection and you need to connect the Data Visualizer Web Part from the Data Filter Web Part as well.

For static filters (i.e. taxonomy picker and date range filter templates), this value can be used using the {filters.<FilterName>} token. See tokens for more information.

Verticals

When you connect the Web Part to a Data Verticals one, you must specify on which vertical the Web Part content should be displayed.

This mechanism allows to build a complete search center using verticals tabs.

Data Results

How to configure item selection?

Source Web Part configuration

1. In a Data Visualizer Web Part where you want to select items from, go to the second property pane configuration page and enable the Allow item selection flag:

1. Specifiy if you want to allow only single or multi selection.
2. Make sure some results are displayed in the Web Part by setting a default query.

Target Web Part(s) configuration

1. In a Data Visualizer Web Part where you want to filter values, go to the third configuration page and enable the Connect to a data results Web Part flag.

2. From here, select the previous Web Part as source.

   

3. Select the source field to use as filter value.

   

   Note

   If you don't see any fields in the dropdown list after selection a source Web Part, it could be because:

   • The source Web Part doesn't have any results displayed yet so we can't guess what are the available exposed fields. In this case, you can either type the field name manually in the dropdown and press 'Enter' or display results in the source Web Part to list all its available fields.
   • The source Web Part doesn't allow item selection. In this case, you can't add any field.

4. Select the destination field to filter the current Web Part results.

   

   Note

   If you don't see any fields in the dropdown list for target fields, it is because the Web Part doesn't display any result yet. In this case, you can either type the field name manually in the dropdown and press 'Enter' or display results in the source Web Part to list all available fields.

5. Select the selection mode.

   

   Note

   • Process values as filters: the values will be sent as regular filters, just like they were selected in the Data Filter Web Part. In this mode, the selected source field must be a valid filter for the current data source. For instance if the data source is SharePoint Search or Microsoft Search, the field must be a valid refinable managed property.
   • Process values as tokens: the values will be sent manually in the data source query using token {filter.source_field.valueAsText/valueAsObject} and/or adaptive expressions to craft a valid query. This scenario can be useful for instance if:
     • You use SharePoint Search or Microsoft Search data sources and you don't want to use a Refinable managed property as filters.
     • You use OData data source and you want to create a dynamic query using tokens.

   Examples

   SharePoint Search KQL (Single Value)

   Title:{filters.Title.valueAsText} will be translated to Title:docx

   SharePoint Search KQL (Multi Values)
   OR condition: {|Title:{filters.Title.valueAsText}} will be translated to (Title:docx) OR (Title:pdf)...
   AND condition: {&Title:{filters.Title.valueAsText}} will be translated to (Title:docx) AND (Title:pdf)...
   
   

   OData URL (Multi Values)
   OR condition: {|Title eq {filters.Title.valueAsText}}` will be translated to `(Title eq 'docx') or (Title eq 'pdf')
   AND condition: {&Title eq {filters.Title.valueAsText}}` will be translated to `(Title eq 'docx') or (Title eq 'pdf')

6. Select the logical operator to use between selected filter values if applicable (default mode only).

   

Filtering general behavior

• null ou empty filters values are ignored in the resulting query.
• Duplicate values are trimmed (ex: user select items with the same filter values).
• Filter values should be 'string' values. All other types will be ignored (ex: 'objects' from JSON response).