Update how-to-use-web-report-designer-in-react-js.md (#1231)

* Update how-to-use-web-report-designer-in-react-js.md

* Update conversion-functions.md

* Update overview.md

* Update about-telerik-reporting.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update load-report-dialog.md

* Update datasource-wizard.md

* Update import-report-wizard.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update shared-resources.md

* Update export-formats.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update installation-approaches.md

* Update set-up-and-create-basic-report.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update angular-report-viewer-overview.md

* Update options.md

* Update how-to-pass-values-to-report-parameters.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update report-viewer-initialization.md

* Update overview.md

* Update ready().md

* Update overview.md

* Update commands.md

* Update events.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update options.md

* Update passing-parameter-values.md

* Update overview.md

* Update options.md

* Update how-to-create-custom-parameter-editors.md

* Update react-report-viewer-overview.md

* Update options.md

* Update how-to-create-a-custom-parameter-editor.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update register-client.md

* Update resolve-document.md

* Update get-version.md

* Update reportsource.md

* Update resolve-report-instance.md

* Update get-report-parameters.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update document-map.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update 1d-overview.md

* Update 2d-overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update title.md

* Update overview.md

* Update overview.md

* Update title.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update overview.md

* Update using-styles-to-customize-reports.md

* Update overview.md

* Update q3-2013.md

* Update q3-2014.md

* Update q3-2015.md

* Update r3-2016.md

* Update r3-2017.md

* Update r3-2018.md

* Update r3-2019.md

* Update r3-2020.md

* Update r3-2021.md

* Update r3-2022.md

* Update r3-2023.md

Author: todorarabadzhiev

designing-reports/connecting-to-data/data-items/filtering-data/overview.md

@@ -6,34 +6,34 @@ slug: telerikreporting/designing-reports/connecting-to-data/data-items/filtering
 tags: overview
 published: True
 position: 0
-previous_url: /data-items-filtering-data
+previous_url: /data-items-filtering-data, /designing-reports/connecting-to-data/data-items/filtering-data/
 ---
 
 # Filtering Data Overview
 
-In Telerik Reporting the expressions are the main tool for describing the run-time behavior of the report. They are used to determine the number of records in the [Data Source]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}) or the number of Group members. In Conditional Formatting rules filters are used to express the conditions on which the styling rules are applied. Filters are predicate expressions which should evaluate to True or False.
+In Telerik Reporting the expressions are the main tool for describing the run-time behavior of the report. They are used to determine the number of records in the [Data Source]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}) or the number of Group members. In Conditional Formatting rules filters are used to express the conditions on which the styling rules are applied. Filters are predicate expressions that should be evaluated as True or False.
 
 You can determine where you want to set a filter by the effect you want to achieve in your report. At run time, the report processor applies the defined filters in the following order: on the [Data Source]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}), and then on the DataItem, and then on Groups from the top down in each Group hierarchy. On a Crosstab, Table, and List, filters for row groups, column groups, and adjacent groups are applied independently. On a Graph, filters for CategoryGroups and SeriesGroups are applied independently. When the report processor calculates a filter, all filter equations are applied in the order they are defined in the Filters collection which is the equivalent of combining them with Boolean AND operations.
 
 ## Filter DataSource records
 
-The idea behind filtering the retrieved data source records is the same as in the WHERE clause in a SQL statement. However there are two ways to achieve this effect:
+The idea behind filtering the retrieved data source records is the same as in the WHERE clause in a SQL statement. However, there are two ways to achieve this effect:
 
-### "Server side" filtering
+### "Server-side" filtering
 
-__The most efficient way to save bandwidth__ is to filter data records before they are retrieved by the DataSource component. This is called filtering on the “server side”. To accomplish this you can use parameterized DataSource component for each DataSource component that support this. The next step is to map each DataSource parameter to Report Parameters using expressions. In this approach no Filters are needed. If however the data source does not support parameters, or you must run stored procedures and cannot modify the query use report filters.
+__The most efficient way to save bandwidth__ is to filter data records before they are retrieved by the DataSource component. This is called filtering on the “server-side”. To accomplish this you can use a parameterized DataSource component for each DataSource component that supports this. The next step is to map each DataSource parameter to Report Parameters using expressions. In this approach, no Filters are needed. If however the data source does not support parameters, or you must run stored procedures and cannot modify the query use report filters.
 
-### "Client side" filtering
+### "Client-side" filtering
 
-A filter can be added to the Filters collection on a Report, a DataItem level or in the Report Parameter’s AvailableValues. Filters are applied to the data set after it is retrieved by the DataSource. This method of filtering is called "client side" filtering and should be avoided for big data. Usually the Filter expressions compare fields of the data against report parameters or master data fields. These filters are calculated over the entire set of data and should not use the aggregate functions for the Expressions.
+A filter can be added to the Filters collection on a Report, a DataItem level, or in the Report Parameter’s AvailableValues. Filters are applied to the data set after it is retrieved by the DataSource. This method of filtering is called "client-side" filtering and should be avoided for big data. Usually, the Filter expressions compare fields of the data against report parameters or master data fields. These filters are calculated over the entire set of data and should not use the aggregate functions for the Expressions.
 
 ## Filter Group members
 
 Set a filter on a Group when you want to include or exclude certain members for a Group. These filters operate over the group members after the groups are calculated and can contain aggregate functions. Group filters are similar to the HAVING clause in a SQL statement.
 
 Filters applied to Report Groups will control the visibility of the Group members and GroupHeader/GroupFooter sections.
 
-Filters applied to Crosstab, Table and List Row/Column Groups will change the visibility of corresponding rows and columns and also their headers.
+Filters applied to Crosstab, Table, and List Row/Column Groups will change the visibility of corresponding rows and columns and also their headers.
 
 For Graph Filters can be applied to SeriesGroups and CategoryGroups and will control the visibility of Series and Category members.
 

designing-reports/connecting-to-data/data-items/grouping-data/overview.md

@@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/connecting-to-data/data-items/grouping-
 tags: overview,data,item,report,group
 published: True
 position: 0
-previous_url: /data-items-grouping-data
+previous_url: /data-items-grouping-data, /designing-reports/connecting-to-data/data-items/grouping-data/
 ---
 
 # Grouping Data Overview

designing-reports/connecting-to-data/data-items/ordering-data/overview.md

@@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/connecting-to-data/data-items/ordering-
 tags: overview,ordering,sorting,data,item,group
 published: True
 position: 0
-previous_url: /data-items-ordering-data
+previous_url: /data-items-ordering-data, /designing-reports/connecting-to-data/data-items/ordering-data/
 ---
 
 # Ordering Data Overview

designing-reports/connecting-to-data/data-items/overview.md

@@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/connecting-to-data/data-items/overview
 tags: overview,data,item,report,table,crosstab,subreport,map,graph
 published: True
 position: 0
-previous_url: /data-items
+previous_url: /data-items, /designing-reports/connecting-to-data/data-items/
 ---
 
 # Data Items Overview
@@ -15,15 +15,15 @@ The data items display and manipulate data in Telerik Reports. With a data item,
 
 > Starting with [R3 2019 (13.2.19.918)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2019-13-2-19-918), when two or more __data items__ use the same DataSource component, the raw data is reused between them. For example, if a Table and a Graph use the same SqlDataSource, the data will be fetched just once from the database when rendering the report.
 
-The data item changes the data context. This means that the `ReportItem.DataObject` [Global Object]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/expressions-reference/global-objects%}) received from the parent is no longer equivalent to the `Fields` Global Object. This makes the data items special with respect to the [Expressions]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/overview%}) context applied to the data report item's Properties.
+The data item changes the data context. This means that the `ReportItem.DataObject` [Global Object]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/expressions-reference/global-objects%}) received from the parent is no longer equivalent to the `Fields` Global Object. This makes the data items special for the [Expressions]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/overview%}) context applied to the data report item's Properties.
 
 For example, in the [Bindings]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/using-expressions/bindings%}) and [Conditional Formattings]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/using-expressions/conditional-formatting%}), the `Fields` Global Object refers to the parent data scope, whereas in the [Filterings]({%slug telerikreporting/designing-reports/connecting-to-data/data-items/filtering-data/how-to-add-filtering-to-report%}), [Groupings]({%slug telerikreporting/designing-reports/connecting-to-data/data-items/grouping-data/how-to-add-groups-to-report%}), and [Sortings]({%slug telerikreporting/designing-reports/connecting-to-data/data-items/ordering-data/how-to-add-sorting-to-report%}), the `Fields` refers to the scope of the current data item. This lets you use both scopes in the Expressions in these properties. For example, when you want to filter the child data only for a particular parent value, you may use a Filtering Rule like `=ReportItem.DataObject.PrentFieldName	=	=Fields.ChildFieldName`.
 
 To make the best choice of data item to use for displaying report data, it helps to understand the characteristics of your data and the purpose of the report. The following list describes the features of each data region:
 
 * __Report__ The Report item consists of multiple horizontal sections (bands), one for each part of the report. For example, data and text in the report header section are rendered at the beginning of the report, data and text in the page header section are rendered at the beginning of each page, and data and text in the page footer sections are rendered at the end of each page. In the middle of the report are the report groups and the detail section. The report groups are always nested and display data for each value in the group, which is determined at runtime. The detail section displays at run-time one row for each detail item in the report data source.
 * __SubReport__ The SubReport item is a placeholder for another report you would like to integrate into the current one. Its structure is the same as the Report item except for the Page sections and PageSettings which are ignored. Starting with [R3 2022 SP1 16.2.22.1109](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2022-sp1-16-2-22-1109) the SubReport item has [its own DataSource property]({%slug telerikreporting/designing-reports/report-structure/subreport%}#the-property-datasource-of-the-subreport-item) that lets you pass data from the main report easily.
-* __Table__ The Table item has a fixed number of columns and displays detail or grouped data by rows. The Table expands down the page as needed. You can display all the detail data, row by row, or group the data by creating row groups. Row groups can be nested or adjacent. Each row group displays a dynamic row down the page for each value in the group, which is determined at run-time. You can also add static rows for labels or totals. You can add totals to the table or to a specific group.
+* __Table__ The Table item has a fixed number of columns and displays detailed or grouped data by rows. The Table expands down the page as needed. You can display all the detailed data, row by row, or group the data by creating row groups. Row groups can be nested or adjacent. Each row group displays a dynamic row down the page for each value in the group, which is determined at run-time. You can also add static rows for labels or totals. You can add totals to the table or to a specific group.
 * __Crosstab__ The Crosstab item is derived from the Table item and displays data grouped by rows and columns. A Crosstab has at least one row group and one column group. The Crosstab expands across the page for column groups and down the page for row groups. The Crosstab cells display summary and aggregate values scoped to the intersections of the row and column groups. You can create additional nested groups and adjacent groups. The number of rows and columns in a Crosstab depends on the values for each group, determined at run-time. You can also add static rows for labels or totals. You can add totals to the table or to a specific group.
 * __List__ The List item is derived from the Table item and contains one row that repeats for each value in the data source and displays data in a free-form format. For example, you might use a list to design a form or display both a table and a chart. Arrange text boxes anywhere in the list to create your layout.
 * __Graph__ The Graph item enables you to present large volumes of aggregated information at a glance in a visual format.

designing-reports/connecting-to-data/data-source-components/csvdatasource-component/overview.md

@@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/connecting-to-data/data-source-componen
 tags: overview
 published: True
 position: 0
-previous_url: /csvdatasource-component
+previous_url: /csvdatasource-component, /designing-reports/connecting-to-data/data-source-components/csvdatasource-component/
 ---
 <style>
 table th:first-of-type {
@@ -31,8 +31,8 @@ Multiple formats are supported through configuring the CsvDataSource settings.
 |`Field separators (column delimiters)`|Configures the list of separators by which the document is split to fields (columns) based on a delimiter.|
 |`Record separators (row delimiters)`|Configures the list of separators by which the document is split to records (rows) based on a delimiter.|
 |`Escape format`|Defines how the special symbols are escaped, like field and record separators and the escape symbols themselves. For more information please check [CsvDataSource Escape Formats]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/csvdatasource-component/csvdatasource-escape-formats%})|
-|`Quote`|Configures the text qualifier if Quotes (RFC 4180 standard is applied to the CSV document) or Quotes Mixed (same as Quotes, but the escape symbol is escaped with backslash) Escape format is used.|
-|`Comment token`|Through providing a comment token for the CsvDataSource comments can be supported and omitted from the data output.|
+|`Quote`|Configures the text qualifier if Quotes (RFC 4180 standard is applied to the CSV document) or Quotes Mixed (same as Quotes, but the escape symbol is escaped with a backslash) Escape format is used.|
+|`Comment token`| By providing a comment token for the CsvDataSource comments can be supported and omitted from the data output.|
 
 ## CsvDataSource data format settings
 
@@ -43,7 +43,7 @@ Below are listed the available settings for formatting the data retrieved from t
 |`Consecutive field/record separators as one`|Configures if consecutive field/record separators are treated as one.|
 |`Decimal separator`|Configures the decimal separator when parsing numbers.|
 |`Thousand separator`|Configures the thousand separator when parsing numbers.|
-|`DateTime format`|A [Custom Date and Time Format String](https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings) which configures the format of the date and time when parsing date and time strings to DateTime data field values. A custom format string consists of one or more custom date and time format specifiers. For more information on date and time format specifiers please refer to the [Custom Date and Time Format Strings](https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings) MSDN article.For example, to correctly parse the string "12-30-11" to a valid DateTime you need to use the following DateTime format: "MM-dd-yy". If the date string does not conform to the specified DateTime format, the DateTime field will appear empty in the Data Preview window.|
+|`DateTime format`|A [Custom Date and Time Format String](https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings) which configures the format of the date and time when parsing date and time strings to DateTime data field values. A custom format string consists of one or more custom date and time format specifiers. For more information on date and time format specifiers please refer to the [Custom Date and Time Format Strings](https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings) MSDN article. For example, to correctly parse the string "12-30-11" to a valid DateTime you need to use the following DateTime format: "MM-dd-yy". If the date string does not conform to the specified DateTime format, the DateTime field will appear empty in the Data Preview window.|
 |`Columns`|Configures the column - data type mapping.|
 
 ## Supported developer platforms

designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview.md

@@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/connecting-to-data/data-source-componen
 tags: overview
 published: True
 position: 0
-previous_url: /CubeDataSource
+previous_url: /CubeDataSource, /designing-reports/connecting-to-data/data-source-components/cubedatasource-component/
 ---
 
 # CubeDataSource Component Overview