Merge branch 'develop'

Author: FranckyC

docs/usage/data-filters/index.md

@@ -55,3 +55,14 @@ The Web Part supports two types of filters (_'Static'_ and _'Refiner'_). However
 - **Refiner**: a 'Refiner' filter means the filter gets its values from the data source and sends back the selected ones the data source. If the data source has no result, there won't be any refiner values, simple as that.
 - **Static filter**: a 'Static' filter means the filter doesn't care about filter values sent by the data source and provides its own arbitrary values regardless of input values. A date range picker or a taxonomy picker (or any picker) are good examples of what an 'Static' filter is. Such a filter do not need necessarily need a Data Visualizer connection.
 
+
+## Use indexed property bag properties with taxonomny values
+
+> **This behavior only works with the SharePoint Search Data source and the _Enabled localization_ flag activated.**
+
+Using an indexed property bag value could be useful to store information about a SharePoint site or other element that can't be tagged with a taxonomy value directly. The 'Modern Data Visualizer' solution supports property bag properties values that use the following taxonomy value format to be able to filter on them (ex: a taxonomy multi values separated by a semicolon (;)):
+
+`L0|#a2cf1afb-44b6-4cf4-bf37-642bb2e9bff3|Category 1;L0|#02e3406c0-1048-4bce-90eb-e7a51dfa7f31|Category3;L0|#07e094327-23d7-48af-9699-781eb26dc40f|Category2`
+
+These taxonomy values can then be used in the Data Filters Web Part using a `RefinableStringXX` search managed property to filter specific sites or elements. As an example, you can refer to the ["Create an end-to-end Office 365 groups provisioning solution"](https://github.com/pnp/tutorial-workspace-provisioning) tutorial GitHub project to leverage this format.
+

docs/usage/data-visualizer/data-sources/index.md

@@ -7,7 +7,7 @@ By default, the following data sources are provided:
 
 !["Available data sources"](../../../assets/webparts/data_visualizer/page1/available_datasources.png){: .center}
 
-> Be careful, when you switch the data source in the property pane, all the previous data source properties are lost. We do this to avoid polluting the Web Part property bag with multiple useless configurations..
+> Be careful, when you switch the data source in the property pane, all the previous data source properties are lost. We do this to avoid polluting the Web Part property bag with multiple useless configurations.
 
 ### SharePoint Search
 

docs/usage/data-visualizer/data-sources/odata.md

@@ -50,20 +50,23 @@ You can also call an API endpoint with no specific authentifcation like an Azure
 
 The only method allowed are `GET` or `POST`. For each, you have the ability so set your own HTTP headers. **The value must be a valid JSON value**:
 
-    {
-        "Content-Type": "application/json;odata=verbose",
-        "Accept": "application/json",
-        ...
-    }
-
+```json
+{
+    "Content-Type": "application/json;odata=verbose",
+    "Accept": "application/json",
+    ...
+}
+```
 
 > If you specify a `POST` request, you can also benefit of [builtin tokens](../tokens.md).
 
-    {
-        "ItemsCount": "{itemsCountPerPage}",
-        "MyProperty": "My Value",
-        ...
-    }
+```json
+{
+    "ItemsCount": "{itemsCountPerPage}",
+    "MyProperty": "My Value",
+    ...
+}
+```
 
 #### Pagination
 

docs/usage/data-visualizer/data-sources/sharepoint-caml.md

@@ -23,7 +23,7 @@ To build your CAML query, you have the choice to use the interactive builder or
 | **View Fields** | The item fields to return from the. They will be available in your templates with the same name. | <ul><li>UniqueId</li><li>EncodedAbsUrl</li><li>FileRef</li><li>File_x0020_Type</li><li>FileLeafRef</li><li>Name</li><li>Author</li><li>Created</li></ul>
 | **Order by field** | An optional field to sort results. If a field is selected, you have the option to select ascending or descending order. | None.
 | **Search within folders** | Enable this option if you want to search in folders recursively in your list or document library. | False.
-| **Filters** | The filter condition builder. From here you can select: </br><p align="center">!["Filter builder"](../../../assets/webparts/data_visualizer/caml/filter_builder.png)</p></br><ul><li><b>Field</b>: the list to apply the condition</li><li><b>Operator</b>: the operator to use. Supported operators are _"Equals,Does not equal, Is greater than, Is less than, Is grater or equal to, Is less or equal to, Is null, Is not null, Begins with and Contains"_</li><li><b>Value</b>: the value to use for the condition. You can use a plain text/date/taxonomy value here (depending of the selected field type) or use a dynamic token. For the second option, enable the corresponding checkbox to have access to the dynamic tokens menu. Notice that not all available tokens are listed here. If the token you want to use is not is the list, you can add it using the _'Custom value'_ option and press enter. All supported tokens can be found [here](../tokens.md)</li></ul>
+| **Filters** | The filter condition builder. From here you can select: </br><p align="center">!["Filter builder"](../../../assets/webparts/data_visualizer/caml/filter_builder.png)</p></br><ul><li><b>Field</b>: the list to apply the condition</li><li><b>Operator</b>: the operator to use. Supported operators are _"Equals,Does not equal, Is greater than, Is less than, Is grater or equal to, Is less or equal to, Is null, Is not null, Begins with and Contains"_.**Operator choices are automatically adjusted regarding the selected field type.**</li><li><b>Value</b>: the value to use for the condition. You can use a plain text/date/taxonomy value here (depending of the selected field type) or use a dynamic token. For the second option, enable the corresponding checkbox to have access to the dynamic tokens menu. Notice that not all available tokens are listed here. If the token you want to use is not is the list, you can add it using the _'Custom value'_ option and press enter. All supported tokens can be found [here](../tokens.md)</li></ul>
 
 ##### Using the advanced mode
 

extensibility-library-demo/package.json

@@ -12,7 +12,7 @@
     "test": "gulp test"
   },
   "dependencies": {
-    "@aequos/extensibility": "1.0.0",
+    "@aequos/extensibility": "1.0.1",
     "@microsoft/sp-component-base": "1.10.0",
     "@microsoft/sp-core-library": "1.10.0",
     "@microsoft/sp-http": "1.10.0",

extensibility-library-demo/src/libraries/CustomDataSource.ts

@@ -1,4 +1,4 @@
-import { BaseDataSource, IDataSourceData, ITemplateSlot, BuiltinTemplateSlots } from "@aequos/extensibility";
+import { BaseDataSource, IDataSourceData, ITemplateSlot, BuiltinTemplateSlots, IDataContext } from "@aequos/extensibility";
 import { IPropertyPaneGroup } from "@microsoft/sp-property-pane";
 import { PropertyPaneTextField } from '@microsoft/sp-webpart-base';
 
@@ -12,7 +12,7 @@ export class CustomDataSource extends BaseDataSource<ICustomDataSourceProperties
         return 0;
     }
 
-    public async getData(): Promise<IDataSourceData> {
+    public async getData(dataContext: IDataContext): Promise<IDataSourceData> {
 
         /* Your logic to get the data */
         return Promise.resolve({