|
-{{ '' | markdownify }}
+{{ '' | markdownify }}
|
Export to CSV |
diff --git a/wpf/OLAP-Client/Filtering.md b/wpf/OLAP-Client/Filtering.md
index 6039a85ec..608b41a2b 100644
--- a/wpf/OLAP-Client/Filtering.md
+++ b/wpf/OLAP-Client/Filtering.md
@@ -51,7 +51,7 @@ The options in the filtering tab are as follows:
* **Filter on**: You can choose any one measure element from the list, on which you want to apply the filter.
* **Value**: Enter the conditional value for the expression.
-You can toggle the visibility of the filter and sort buttons in the OLAP client toolbar by using the `ShowFilterSortButtons` property.
+You can toggle the visibility of the filter and sort buttons in the OLAP Client toolbar by using the `ShowFilterSortButtons` property.
{% tabs %}
diff --git a/wpf/OLAP-Client/Getting-Started.md b/wpf/OLAP-Client/Getting-Started.md
index 8a0d3fc49..d006e4875 100644
--- a/wpf/OLAP-Client/Getting-Started.md
+++ b/wpf/OLAP-Client/Getting-Started.md
@@ -13,17 +13,17 @@ documentation: ug
>**Important**
Starting with v16.2.0.x, if you refer to Syncfusion® assemblies from trial setup or from the NuGet feed, include a license key in your projects. Refer to this [License Guidelines](https://help.syncfusion.com/wpf/licensing/overview) to learn about registering Syncfusion® license key in your WPF application to use the components.
-This section covers the information required to create a simple OLAP client bound to the OLAP data source.
+This section covers the information required to create a simple OLAP Client bound to the OLAP data source.
## Through Visual Studio
Open the Visual Studio IDE and navigate to File > New > Project > WPF application (inside Visual C# templates) to create a new WPF application.
-After creating the WPF application, go to View menu and select Toolbox option. Now, the toolbox will appear inside the Visual Studio IDE. From the Visual Studio Toolbox, drag the OLAP client under the **Syncfusion® BI WPF** tag. It will automatically add the required assemblies to the application.
+After creating the WPF application, go to View menu and select Toolbox option. Now, the toolbox will appear inside the Visual Studio IDE. From the Visual Studio Toolbox, drag the OLAP Client under the **Syncfusion® BI WPF** tag. It will automatically add the required assemblies to the application.
-Add a **Name** to the OLAP client component for accessing it through code-behind as shown in the following code sample.
+Add a **Name** to the OLAP Client component for accessing it through code-behind as shown in the following code sample.
{% highlight xaml %}
@@ -39,7 +39,7 @@ Add a **Name** to the OLAP client component for accessing it through code-behind
{% endhighlight %}
-Include the following namespace in the code-behind for using OlapDataManger in the application. The **OlapDataManager** class contains the connection details, current report, cube name, cube schema, and pivot engine for rendering the OLAP client control.
+Include the following namespace in the code-behind for using OlapDataManger in the application. The **OlapDataManager** class contains the connection details, current report, cube name, cube schema, and pivot engine for rendering the OLAP Client control.
* Syncfusion.Olap.Manager
@@ -113,11 +113,11 @@ Select the **Project** tab available in the left-corner of the Blend IDE, right-
N> You can also get the assemblies by browsing to the default assembly location {System Drive}:\Program Files (x86)\Syncfusion\Essential Studio\<version number>\precompiledassemblies\<version number>\<framework version>\
-On adding the above assemblies, the OLAP client control will be added under the **Assets** tab automatically. Now, choose the **Assets** tab and drag the OLAP client to the designer.
+On adding the above assemblies, the OLAP Client control will be added under the **Assets** tab automatically. Now, choose the **Assets** tab and drag the OLAP Client to the designer.
-Add a **Name** to the OLAP client component for accessing it through code-behind as shown in the following code sample.
+Add a **Name** to the OLAP Client component for accessing it through code-behind as shown in the following code sample.
{% highlight xaml %}
@@ -212,7 +212,7 @@ To add the dependency assemblies within the application, right-click the **Refer
N> You can also get the assemblies by browsing to the default assembly location {System Drive}:\Program Files (x86)\Syncfusion\Essential Studio\<version number>\precompiledassemblies\<version number>\<{framework version>\
-Include the following namespaces in code-behind for using OLAP client and OlapDataManger in the application.
+Include the following namespaces in code-behind for using OLAP Client and OlapDataManger in the application.
* Syncfusion.Olap.Manager
* Syncfusion.Windows.Client.Olap
diff --git a/wpf/OLAP-Client/Localization.md b/wpf/OLAP-Client/Localization.md
index c4e6b022f..7f3b31b7c 100644
--- a/wpf/OLAP-Client/Localization.md
+++ b/wpf/OLAP-Client/Localization.md
@@ -9,11 +9,11 @@ documentation: ug
# Localization in WPF OLAP Client
-Localization deals with customizing data and resources for specific culture or language. The built-in localization and globalization mechanism in WPF allows you to localize any string resource used by the OLAP client control.
+Localization deals with customizing data and resources for specific culture or language. The built-in localization and globalization mechanism in WPF allows you to localize any string resource used by the OLAP Client control.
You can create and place the resource files in a separate location in the user application. Then, you can access the culture specific resources from the current application assembly.
-For this, first create a resource file for our OLAP client control and translate the strings to your culture. Basically, the OLAP client contains control assemblies such as OlapChart.WPF and OlapGrid.WPF and Tools assemblies such as OlapShared.WPF and OlapTools.WPF within it. So, it is mandatory to localize the necessary strings available in those assemblies. Once it is translated, you might use the resources in your projects by setting the corresponding culture in your application.
+For this, first create a resource file for our OLAP Client control and translate the strings to your culture. Basically, the OLAP Client contains control assemblies such as OlapChart.WPF and OlapGrid.WPF and Tools assemblies such as OlapShared.WPF and OlapTools.WPF within it. So, it is mandatory to localize the necessary strings available in those assemblies. Once it is translated, you might use the resources in your projects by setting the corresponding culture in your application.
@@ -44,7 +44,7 @@ End Sub
## RTL support
-RTL support for OLAP client is used to display the content from right to left by setting the `FlowDirection` property to "RightToLeft". The following code sample explains how to set this property.
+RTL support for OLAP Client is used to display the content from right to left by setting the `FlowDirection` property to "RightToLeft". The following code sample explains how to set this property.
{% tabs %}
diff --git a/wpf/OLAP-Client/Named-Sets.md b/wpf/OLAP-Client/Named-Sets.md
index 160275d39..f41933bd7 100644
--- a/wpf/OLAP-Client/Named-Sets.md
+++ b/wpf/OLAP-Client/Named-Sets.md
@@ -9,7 +9,7 @@ documentation: ug
# Named Sets in WPF OLAP Client
-The OLAP client supports the binding of OLAP data with named set records pre-defined in the cube. A named set is a collection of tuples and members, which can be defined and saved as a part of the cube definition. Named set records reside inside the sets folder, which is under a dimension element. These elements can be dragged to categories/series/slicer axis of the axis element builder. To easily work with a lengthy, complex, or commonly used expression, use Multidimensional Expressions (MDX) that allows you to define a named set.
+The OLAP Client supports the binding of OLAP data with named set records pre-defined in the cube. A named set is a collection of tuples and members, which can be defined and saved as a part of the cube definition. Named set records reside inside the sets folder, which is under a dimension element. These elements can be dragged to categories/series/slicer axis of the axis element builder. To easily work with a lengthy, complex, or commonly used expression, use Multidimensional Expressions (MDX) that allows you to define a named set.
The cube dimension browser displays the dimensions, measures, and KPIs along with named sets from the selected cube inside a tree on the left. To visualize these members, you can drag the members to the axis element builder.
diff --git a/wpf/OLAP-Client/OlapClient-Elements.md b/wpf/OLAP-Client/OlapClient-Elements.md
index 15a31c951..c74c82823 100644
--- a/wpf/OLAP-Client/OlapClient-Elements.md
+++ b/wpf/OLAP-Client/OlapClient-Elements.md
@@ -123,7 +123,7 @@ True |
## Axis element builder
-The axis element builder allows you to build elements in the axes of OLAP client. This supports three axes: categorical, series, and slicer. Based on the construction of the axes, the OLAP grid and OLAP chart will display the resultant data.
+The axis element builder allows you to build elements in the axes of OLAP Client. This supports three axes: categorical, series, and slicer. Based on the construction of the axes, the OLAP grid and OLAP chart will display the resultant data.
### Categorical (column)
@@ -183,7 +183,7 @@ The Check All and Uncheck All options in the dialog allows you to select and des
The options available in the toolbar are:
-* **Connect to server**: Connects the data source with OLAP client through the offline cube, online server, or connection string.
+* **Connect to server**: Connects the data source with OLAP Client through the offline cube, online server, or connection string.
* **New report**: Creates a new report list and clears the existing report collection to provide a new platform for new deployment based on the existing cube elements.
* **Load report**: Picks a saved report collection from the database and loads it by clearing the existing collection of reports.
* **Save report**: Stores the report collection at that instant in the local system.
@@ -195,7 +195,7 @@ The options available in the toolbar are:
* **Show expander**: Displays an expander option for the grid and chart to perform drill-down operations.
* **Filter/sort column**: Filters or sorts the data in the OLAP report with respect to the column.
* **Filter/sort row**: Filters or sorts the data in the OLAP report with respect to the row.
-* **Report list**: Holds all reports of the current session of the OLAP client control and displays them in a drop-down list. You can select a report from the drop-down list.
+* **Report list**: Holds all reports of the current session of the OLAP Client control and displays them in a drop-down list. You can select a report from the drop-down list.
* **MDX query**: Displays the executed MDX query to retrieve the data at that instant.
## Report manipulation
@@ -248,7 +248,7 @@ After providing an appropriate name, click **Save**. The report will be saved in
### Load report
-This option loads a report from the local system. Click the load report icon on the toolbar to load a report into the OLAP client.
+This option loads a report from the local system. Click the load report icon on the toolbar to load a report into the OLAP Client.
diff --git a/wpf/OLAP-Client/OlapReport-Serialization.md b/wpf/OLAP-Client/OlapReport-Serialization.md
index 4a89bbe09..0deb37c8c 100644
--- a/wpf/OLAP-Client/OlapReport-Serialization.md
+++ b/wpf/OLAP-Client/OlapReport-Serialization.md
@@ -9,7 +9,7 @@ documentation: ug
# OlapReport Serialization in WPF OLAP Client
-This feature allows users to store the current session as a stream anywhere and load the saved stream back to populate the OLAP client control.
+This feature allows users to store the current session as a stream anywhere and load the saved stream back to populate the OLAP Client control.
The following code sample describes getting the report as stream.
@@ -29,7 +29,7 @@ Dim stream As Stream = Me.olapClient1.GetReportStream()
{% endtabs %}
-The following code sample illustrates loading the report which is in stream type to OLAP client.
+The following code sample illustrates loading the report which is in stream type to OLAP Client.
{% tabs %}
@@ -50,7 +50,7 @@ Me.olapClient1.LoadReportStream(reportStream)
The following code sample describes
* storing of the report as stream in database and
- * retrieving the report as stream from the database and loading it back to OLAP client.
+ * retrieving the report as stream from the database and loading it back to OLAP Client.
**Storing report as stream in database**
diff --git a/wpf/OLAP-Client/Overview.md b/wpf/OLAP-Client/Overview.md
index 336444034..f1dc8118e 100644
--- a/wpf/OLAP-Client/Overview.md
+++ b/wpf/OLAP-Client/Overview.md
@@ -9,7 +9,7 @@ documentation: ug
# About Syncfusion WPF OLAP Client Control
-The OLAP client control for WPF supports browsing multidimensional data that is organized in the form of dimensions, measures, named sets, and KPI (key performance indicators) in a cube format. You can visualize the results in graphical and tabular formats (chart and grid). The OLAP client control is also used to create and edit a report on-the-fly that is stored for later use.
+The OLAP Client control for WPF supports browsing multidimensional data that is organized in the form of dimensions, measures, named sets, and KPI (key performance indicators) in a cube format. You can visualize the results in graphical and tabular formats (chart and grid). The OLAP Client control is also used to create and edit a report on-the-fly that is stored for later use.
## Key features
@@ -20,7 +20,7 @@ The OLAP client control for WPF supports browsing multidimensional data that is
* **Grid**: A grid is a tabular representation of data, arranged in the form of rows and columns and categorized accordingly.
* **Cube selector**: Comprises multiple cubes obtained from the data source.
* **Cube dimension browser**: Tree view structure that comprises measures, dimensions, hierarchies, named sets, KPI, and so on, belonging to the current cube into independent logical groups.
-* **AxisElementBuilder**: Allows building an OLAP report by placing elements in different axes of the OLAP client. There are three axes that are supported namely column, row, and slicer.
+* **AxisElementBuilder**: Allows building an OLAP report by placing elements in different axes of the OLAP Client. There are three axes that are supported namely column, row, and slicer.
* **Member editor**: A tree view control that displays the member elements of the selected dimension.
* **Measure editor**: Comprises a collection of measures.
* **Toolbar**: Toolbar provides options for filter, sorting, exporting, and manipulating the OLAP report.
diff --git a/wpf/OLAP-Client/Paging.md b/wpf/OLAP-Client/Paging.md
index a6a3d904a..6549b5be6 100644
--- a/wpf/OLAP-Client/Paging.md
+++ b/wpf/OLAP-Client/Paging.md
@@ -9,13 +9,13 @@ documentation: ug
# Paging in WPF OLAP Client
-Paging in the OLAP client supports you to load and render the large amount of data without any performance constraint.
+Paging in the OLAP Client supports you to load and render the large amount of data without any performance constraint.
-The OLAP pager (user control) is included and bound with the OlapDataManager object of the respective OLAP client. To enable paging, set the `EnablePaging` property to true.
+The OLAP pager (user control) is included and bound with the OlapDataManager object of the respective OLAP Client. To enable paging, set the `EnablePaging` property to true.
When you process the large CellSet, it is split into several number of segments and each segment is assigned and rendered in a separate page. You can navigate back and forth in all possible ways by using the UI options in the OLAP pager. You can also change the page size and other pager settings at runtime by using the **PageSetting** window.
-Include the following Syncfusion