revamp main and refer related articles

NansiYancheva · NansiYancheva · commit 3eab836e9d11 · 2024-10-18T20:54:20.000+03:00
diff --git a/common-features/data-binding/cloud-services.md b/common-features/data-binding/cloud-services.md
@@ -5,7 +5,7 @@ description: How to data bind Telerik Blazor components to cloud data services s
 slug: common-features-data-binding-cloud
 tags: telerik,blazor,binding,databinding,cloud
 published: True
-position: 15
+position: 30
 ---
 
 # Databinding to Cloud Services
diff --git a/common-features/data-binding/descriptors.md b/common-features/data-binding/descriptors.md
@@ -5,14 +5,25 @@ description: Discover the FilterDescriptor, SortDescriptor, SearchFilter and Gro
 slug: common-features-descriptors
 tags: telerik,blazor,filterdescriptor, sortdescriptor, groupdescriptor, searchfilter
 published: True
-position: 8
+position: 10
 ---
 
-# Common
+
+## Components with Descriptors
+
+This article explains how to retrieve the applied filtering, searching, sorting, and grouping criteria in Blazor components. The article applies to components that support these features. The components that offer one or all of the functionalities are:
+* The [Filter]({%slug filter-overview%})
+* The [Gantt]({%slug gantt-overview%})
+* The [TreeList]({%slug treelist-overview%})
+* All components that [expose the `OnRead` event]({%slug common-features-data-binding-onread%}#components-with-onread-event).
+
+## Obtain Filtering, Searching, Sorting, Grouping criteria
 
 There are two ways to obtain the applied filtering, searching, sorting, grouping criteria:
 
-* Through the component [`OnRead` event]({%slug common-features-data-binding-onread%}) handler. Use the [`Request` property]({%slug common-features-data-binding-onread%}#event-argument) of the [event argument object](/blazor-ui/api/Telerik.Blazor.Components.ReadEventArgs):
+#### Through the OnRead Event
+
+Use the [`Request` property]({%slug common-features-data-binding-onread%}#event-argument) of the [`OnRead` event argument object](/blazor-ui/api/Telerik.Blazor.Components.ReadEventArgs):
 
 ````CS
 async Task OnReadHandler(...ReadEventArgs args)
@@ -32,8 +43,8 @@ async Task OnReadHandler(...ReadEventArgs args)
 }
 ````
 
-
-* Through the component state. Use the component state property of the `OnStateChanged` event argument. For example:
+#### Through the Component State
+Use the component state property of the `OnStateChanged` event argument. For example:
 
 ````CS
 async Task OnStateChangedHandler(GridStateEventArgs<Product> args)
@@ -56,17 +67,19 @@ async Task OnStateChangedHandler(GridStateEventArgs<Product> args)
 }
 ````
 
+At the bottom of the article you will find full examples.
+
 
-# Filtering
+## Filtering
 
 The filtering criteria for each filtered field is stored in an individual collection of [`IFilterDescriptor`](/blazor-ui/api/Telerik.DataSource.IFilterDescriptor). To access the filtering criteria, cast each `IFilterDescriptor` to [`CompositeFilterDescriptor`](/blazor-ui/api/Telerik.DataSource.CompositeFilterDescriptor).
 
 The `CompositeFilterDescriptor` exposes:
-* [`FilterDescriptors`](/blazor-ui/api/telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_FilterDescriptors) property. This property represents another collection of `IFilterDescriptor`. To get the properties of each filter descriptor instance cast the `IFilterDescriptor` to a [`FilterDescriptor`](/blazor-ui/api/telerik.datasource.filterdescriptor). Each `FilterDescriptor` instance gives access to:
+* [`FilterDescriptors`](/blazor-ui/api/telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_FilterDescriptors) property. This property represents another collection of `IFilterDescriptor`. To access the filtering criteria cast the `IFilterDescriptor` to a [`FilterDescriptor`](/blazor-ui/api/telerik.datasource.filterdescriptor). Each `FilterDescriptor` instance gives access to:
     * The `Member`&mdash;The field where the user filters. Each filter descriptor describes also the `MemberType`, that represents the type of the field.
     * The `Operator`&mdash;The [`FilterOperator`](/blazor-ui/api/telerik.datasource.filteroperator) that applies. There are different operators depending on the `MemberType`. Read more about the [filter operators]({%slug common-features-filter-operators%}).
     * The `Value`&mdash;The user input to filter by.
-* [`LogicalOperator`](/blazor-ui/api/telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_LogicalOperator) property. This property can be either AND or OR. The logical operator applies between the filter descriptor instances.
+* [`LogicalOperator`](/blazor-ui/api/telerik.datasource.compositefilterdescriptor#Telerik_DataSource_CompositeFilterDescriptor_LogicalOperator) property. This property can be either AND or OR. This property represents the logical operator applied between the instances in the `FilterDescriptors` collection.
 
 When the filtering is initiated, the `CompositeFilterDescriptor` properties get different values, depending on the filter mode:
 
@@ -78,24 +91,26 @@ When the filtering is initiated, the `CompositeFilterDescriptor` properties get
 | FilterRow | Two filter descriptor instances per each filtered field. The second filter descriptor instance always gets null as `Value`, because there is no second input field. | AND |
 
 
-# Searching
+## Searching
 
-The searching criteria is stored in an individual `IFilterDescriptor`. To access the filtering criteria, cast the `IFilterDescriptor` to `CompositeFilterDescriptor`. The `FilterDescriptors` property of the `CompositeFilterDescriptor` gets filter descriptor instances for all string fields. Each filter descriptor instance gets the user input as `Value`. The value of the `LogicalOperator` property of the `CompositeFilterDescriptor` is OR.
+The searching criteria are stored in an individual `IFilterDescriptor`. To access the filtering criteria, cast the `IFilterDescriptor` to `CompositeFilterDescriptor`. The `FilterDescriptors` property of the `CompositeFilterDescriptor` gets filter descriptor instances for all string fields. Each filter descriptor instance gets the user input as `Value`. The value of the `LogicalOperator` property of the `CompositeFilterDescriptor` is OR.
 
 
-# Sorting
+## Sorting
 
-The current sorting criteria is stored in a collection of [`SortDescriptor`](/blazor-ui/api/telerik.datasource.sortdescriptor). Each `SortDescriptor` instance gives access to:
-    * The `Member`&mdash;The field where the user sorts.
-    * The `SortDirection`&mdash;The sort direction for this sort descriptor.
+The sorting criteria are stored in a collection of [`SortDescriptor`](/blazor-ui/api/telerik.datasource.sortdescriptor). Each `SortDescriptor` instance gives access to:
+* The `Member`&mdash;The field where the user sorts.
+* The `SortDirection`&mdash;The sort direction for this sort descriptor.
 
 
-# Grouping
+## Grouping
 
 Тhe grouping criteria for each group is stored in an individual collection of [`GroupDescriptor`](/blazor-ui/api/telerik.datasource.groupdescriptor). The `GroupDescriptor` class inherits the `SortDescriptor` class and gives access to the same properties as the `SortDescriptor` class.
 
 
-# Example with `OnRead` Event
+## Examples
+
+#### Obtain the FilterDescriptor, SearchFilter, SortDescriptor, GroupDescriptor in the OnRead Event Handler
 
 ````CSHTML
 @using Telerik.DataSource
@@ -185,7 +200,8 @@ The current sorting criteria is stored in a collection of [`SortDescriptor`](/bl
 }
 ````
 
-# Example Through the Component State
+#### Obtain the FilterDescriptor, SearchFilter, SortDescriptor, GroupDescriptor Through the Component State
+
 ````CSHTML
 @using System.Text.Json
 @using Telerik.DataSource
diff --git a/common-features/data-binding/filter-operators.md b/common-features/data-binding/filter-operators.md
@@ -5,7 +5,7 @@ description: Supported Filter Operators in the Telerik UI for Blazor component s
 slug: common-features-filter-operators
 tags: telerik,blazor,filter,operator
 published: True
-position: 10
+position: 15
 ---
 
 # Filter Operators
diff --git a/common-features/data-binding/observable-data.md b/common-features/data-binding/observable-data.md
@@ -6,7 +6,7 @@ slug: common-features-observable-data
 tags: telerik,blazor,observable,data,live,INotifyCollectionChanged 
 published: True
 previous_url: /common-features/observable-data
-position: 10
+position: 25
 ---
 
 # Observable Data and Refresh Data
diff --git a/common-features/data-binding/telerik-datasource-package.md b/common-features/data-binding/telerik-datasource-package.md
@@ -5,7 +5,7 @@ description: Details about the Telerik.DataSource NuGet package that come with T
 slug: common-features-datasource-package
 tags: telerik,blazor,data,source,package
 published: True
-position: 50
+position: 20
 ---
 
 # Telerik DataSource Package
diff --git a/components/autocomplete/events.md b/components/autocomplete/events.md
@@ -124,6 +124,8 @@ You can use the he [`OnRead` event]({%slug common-features-data-binding-onread%}
 
 You can also call remote data through async operations.
 
+Find out how to [get the applied by the user filtering and grouping criteria]({%slug common-features-descriptors%}).
+
 When using `OnRead`, make sure to set `TItem` and `TValue`.
 
 >caption Custom Data according to the user input in the AutoComplete
diff --git a/components/autocomplete/filter.md b/components/autocomplete/filter.md
@@ -12,7 +12,11 @@ position: 10
 
 The AutoComplete component can filter the available suggestions, according to the current input. In this way users can find the desired value faster. To see the difference in behavior, visit the [Live Demo: AutoComplete Filtering](https://demos.telerik.com/blazor-ui/autocomplete/filtering) page.
 
-To enable filtering, set the `Filterable` parameter to `true`. The filtering is case insensitive. You can also implement custom (server) filtering and set a data source dynamically through the [`OnRead` event]({%slug autocomplete-events%}#onread).
+To enable filtering, set the `Filterable` parameter to `true`. The filtering is case insensitive.
+
+You can also use the [`OnRead` event]({%slug autocomplete-events%}#onread) to:
+* Get the [applied filtering criteria]({%slug common-features-descriptors%}#through-the-onread-event).
+* Implement custom (server) filtering and set a data source dynamically.
 
 ## Filter Operator
 
diff --git a/components/combobox/events.md b/components/combobox/events.md
@@ -183,6 +183,8 @@ You can use the [`OnRead` event]({%slug common-features-data-binding-onread%}) t
 
 You can also call remote data through `async` operations.
 
+Find out how to [get the applied by the user filtering and grouping criteria]({%slug common-features-descriptors%}).
+
 When using `OnRead`, make sure to set `TItem` and `TValue`.
 
 >caption Custom Data according to the user input in the ComboBox
diff --git a/components/combobox/filter.md b/components/combobox/filter.md
@@ -12,7 +12,11 @@ position: 10
 
 The ComboBox component allows the user to filter the available items by their text, so they can find the one they need faster.
 
-To enable filtering, set the `Filterable` parameter to `true`. The filtering is case insensitive. You can also implement custom (server) filtering and set a data source dynamically through the [`OnRead` event]({%slug components/combobox/events%}#onread).
+To enable filtering, set the `Filterable` parameter to `true`. The filtering is case insensitive. 
+
+You can also use the [`OnRead` event]({%slug components/combobox/events%}#onread) to:
+* Get the [applied filtering criteria]({%slug common-features-descriptors%}#through-the-onread-event).
+* Implement custom (server) filtering and set a data source dynamically.
 
 Filtering looks in the `TextField`, and the filter is reset when the dropdown closes.
 
diff --git a/components/dropdownlist/events.md b/components/dropdownlist/events.md
@@ -103,7 +103,9 @@ You can use the [`OnRead` event]({%slug common-features-data-binding-onread%}) t
 
 * the component initializes
 * the user [filters]({%slug components/dropdownlist/filter%})
-* the user scrolls with [virtualization]({%slug dropdownlist-virtualization%}) enabled
+* the user scrolls with [virtualization]({%slug dropdownlist-virtualization%}) enabled.
+
+Find out how to [get the applied by the user filtering and grouping criteria]({%slug common-features-descriptors%}).
 
 You can also call remote data through `async` operations.
 
diff --git a/components/dropdownlist/filter.md b/components/dropdownlist/filter.md
@@ -12,7 +12,11 @@ position: 10
 
 The DropDownList filter textbox allows users to filter the available items by their text and find the one they need faster. The filtering input is at the top of the dropdown popup.
 
-To enable filtering, set the `Filterable` parameter to `true`. The filtering is case insensitive. You can also implement custom (server) filtering and set a data source dynamically through the [`OnRead` event]({%slug components/dropdownlist/events%}#onread).
+To enable filtering, set the `Filterable` parameter to `true`. The filtering is case insensitive.
+
+You can also use the [`OnRead` event]({%slug components/dropdownlist/events%}#onread) to:
+* Get the [applied filtering criteria]({%slug common-features-descriptors%}#through-the-onread-event).
+* Implement custom (server) filtering and set a data source dynamically.
 
 Filtering looks in the `TextField`, and the filter is reset when the dropdown closes.
 
diff --git a/components/filter/overview.md b/components/filter/overview.md
@@ -63,7 +63,7 @@ The Blazor Filter provides parameters that allow you to configure the component:
 | Parameter | Type | Description |
 | ----------- | ----------- | ----------- |
 | `Class` | `string` | The class that will be rendered on the outermost element. |
-| `Value` | [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}) | Sets the value of the filter component. |
+| `Value` | [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}#filtering) | Sets the value of the filter component. |
 
 ## Filter Reference and Methods
 
diff --git a/components/gantt/gantt-tree/filter/overview.md b/components/gantt/gantt-tree/filter/overview.md
@@ -26,17 +26,7 @@ You can filter more than one column at a time, and all filter rules will be appl
 
 ## Filter Descriptors
 
-The filtering criteria for each filtered field is stored in an individual [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}). The below information is important if you want to [get or change the Gantt filters programmatically]({%slug gantt-state%}).
-
-When the filtering is initiated, the `CompositeFilterDescriptor` properties get different values, depending on the filter mode:
-
-@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
-
-| Filter Mode | FilterDescriptors Property Value | LogicalOperator Property Value |
-| --- | --- | --- |
-| FilterMenu | Two filter descriptor instances per each filtered field. Each filter descriptor instance gets the user input as `Value`. If there is no user input in one of the input fields of the menu, then the  `Value` of this filter descriptor instance is null. | Depending on the user's choice. |
-| FilterRow | Two filter descriptor instances per each filtered field. The second filter descriptor instance always gets null as `Value`, because there is no second input field. | AND |
-
+The filtering criteria for each filtered field are stored in an individual [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}#filtering).
 
 ## Customize The Filter Editors
 
diff --git a/components/gantt/gantt-tree/sorting.md b/components/gantt/gantt-tree/sorting.md
@@ -24,6 +24,8 @@ Sorting keeps the expanded/collapsed state of items. For example, if filtering b
 
 You can let the user sort by more than one field by setting the `SortMode` parameter to `Telerik.Blazor.SortMode.Multiple`.
 
+The sorting criteria are stored in a [collection of `SortDescriptor`]({%slug common-features-descriptors%}#sorting).
+
 >caption Enable Sorting in Telerik TreeList
 
 ````CSHTML
diff --git a/components/gantt/state.md b/components/gantt/state.md
@@ -564,6 +564,8 @@ Sometimes you may want to know what the user changed in the Gantt (e.g., when th
 
 Find out what the user changed in the Gantt through the `PropertyName` of the `GanttStateEventArgs`. Override the user action by changing and then setting your desired state.
 
+Find out how to [get the applied by the user filtering and sorting criteria]({%slug common-features-descriptors%}).
+
 >caption Know when the Gantt state changes, which parameter changes, and amend the change
 
 ````CSHTML
diff --git a/components/grid/filter/overview.md b/components/grid/filter/overview.md
@@ -37,17 +37,7 @@ The filter menu can display a [list of checkboxes]({%slug grid-checklist-filter%
 
 ## Filter Descriptors
 
-The filtering criteria for each filtered field is stored in an individual [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}). Use the following information if you want to [get or change the Grid filters programmatically]({%slug grid-state%}).
-
-When the filtering is initiated, the `CompositeFilterDescriptor` properties get different values, depending on the filter mode:
-
-@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
-
-| Filter Mode | FilterDescriptors Property Value | LogicalOperator Property Value |
-| --- | --- | --- |
-| FilterMenu | Two filter descriptor instances per each filtered field. Each filter descriptor instance gets the user input as `Value`. If there is no user input in one of the input fields in the menu then this filter descriptor instance `Value` is null. | Depending on the user choice. |
-| FilterRow | Two filter descriptor instances per each filtered field. The second filter descriptor instance always gets null as `Value`, because there is no second input field. | AND |
-| SearchBox | Filter descriptor instances for all string fields. Each filter descriptor instance gets the user input as `Value`. | OR |
+The filtering criteria for each filtered field are stored in an individual [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}#filtering).
 
 ## Custom Filtering
 
diff --git a/components/grid/state.md b/components/grid/state.md
@@ -34,12 +34,12 @@ The Grid state is a generic [class `GridState<TItem>`](/blazor-ui/api/Telerik.Bl
 | `EditField` | `string` | The currently edited data item property in [`Incell` edit mode]({%slug components/grid/editing/incell%}). |
 | `EditItem` | `TItem`* | The currently edited data item in [any edit mode]({%slug components/grid/editing/overview%}). |
 | `ExpandedItems` | `ICollection<TItem>` | The expanded data items, when [using `<DetailTemplate>` (hierarchy)]({%slug components/grid/features/hierarchy%}). |
-| `FilterDescriptors` | `ICollection<IFilterDescriptor>` | All filtering criteria, except the ones that relate to the[`GridSearchBox`]({%slug grid-searchbox%}). |
+| `FilterDescriptors` | `ICollection<IFilterDescriptor>` | A collection of [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}#filtering), except the ones that relate to the [`GridSearchBox`]({%slug grid-searchbox%}). |
 | `GroupDescriptors` | `ICollection<GroupDescriptor>` | Information about currently applied [grouping]({%slug components/grid/features/grouping%}). |
 | `InsertedItem` | `TItem`* | The data item that is being added in `Inline` or `Popup` edit mode. [Not applicable for `Incell` editing]({%slug components/grid/editing/incell%}#event-sequence). |
 | `OriginalEditItem` | `TItem`* | The original copy of the data item that is currently in edit mode. This `GridState` property holds the unmodified data item values. |
 | `Page` | `int?` | The current [page index]({%slug components/grid/features/paging%}). Some user actions reset the page index to 1, such as filtering or changing the page size. |
-| `SearchFilter` | `IFilterDescriptor` | The [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}) that holds the filter descriptors for the [`GridSearchBox`]({%slug grid-searchbox%}). |
+| `SearchFilter` | `IFilterDescriptor` | The [`CompositeFilterDescriptor`]({%slug common-features-descriptors%}#filtering) that holds the filter descriptors for the [`GridSearchBox`]({%slug grid-searchbox%}). |
 | `SelectedItems` | `ICollection<TItem>` | The currently [selected data item(s)]({%slug grid-selection-overview%}). |
 | `Skip` | `int?` | The number of scrolled data items when using [virtual row scrolling]({%slug components/grid/virtual-scrolling%}). In other words, this is the number of rows above the currently visible ones. |
 | `SortDescriptors` | `ICollection<SortDescriptor>` | The currently applied [sorts]({%slug components/grid/features/sorting%}). |
@@ -176,6 +176,8 @@ Here is some additional information about certain `PropertyName` values:
 
 To observe the changes in the Grid state more easily, copy and run the following example in a local app and at full screen.
 
+Find out how to [get the applied by the user filtering, sorting and grouping criteria]({%slug common-features-descriptors%}).
+
 >caption Using Grid OnStateChanged
 
 ````CSHTML
diff --git a/components/multicolumncombobox/events.md b/components/multicolumncombobox/events.md
@@ -206,6 +206,8 @@ You can use the `OnRead` event to provide data to the component according to som
 
 You can also call remote data through `async` operations.
 
+Find out how to [get the applied by the user filtering and grouping criteria]({%slug common-features-descriptors%}).
+
 When using `OnRead`, make sure to set `TItem` and `TValue`.
 
 >tip You can also [debounce the service calls and implement minimum filter length]({%slug combo-kb-debounce-onread%}).
diff --git a/components/multicolumncombobox/filter.md b/components/multicolumncombobox/filter.md
diff --git a/components/multiselect/events.md b/components/multiselect/events.md
diff --git a/components/multiselect/filter.md b/components/multiselect/filter.md
diff --git a/components/treelist/filter/overview.md b/components/treelist/filter/overview.md
diff --git a/components/treelist/sorting.md b/components/treelist/sorting.md
diff --git a/components/treelist/state.md b/components/treelist/state.md
