You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reporting-services/report-design/custom-code-and-assembly-references-in-expressions-in-report-designer-ssrs.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
-
title: "Custom Code and Assembly References in Expressions in Report Designer | Microsoft Docs"
3
-
description: Find out how to add references to custom code embedded in a report. Build and save to your computer and deploy to the report server in Report Builder.
2
+
title: "Custom code and assembly references in expressions in a paginated report in Report Designer | Microsoft Docs"
3
+
4
+
description: Find out how to add references to custom code embedded in a paginated report. Build and save to your computer and deploy to the report server in Report Builder.
# Custom Code and Assembly References in Expressions in Report Designer (SSRS)
25
-
You can add references to custom code embedded in a report or to custom assemblies that you build and save to your computer and deploy to the report server. Use embedded code for custom constants, complex functions or functions that are used multiple times in a single report. Use custom code assemblies to maintain code in a single place and share it for use by multiple reports. Custom code can include new custom constants, variables, functions, or subroutines. You can include read-only references to built-in collections such as the Parameters collection. However, you cannot pass sets of report data values to custom functions; specifically, custom aggregates are not supported.
25
+
# Custom code and assembly references in expressions in a paginated report in Report Designer (SSRS)
You can add references to custom code embedded in a paginated report or to custom assemblies that you build and save to your computer and deploy to the report server. Use embedded code for custom constants, complex functions or functions that are used multiple times in a single report. Use custom code assemblies to maintain code in a single place and share it for use by multiple reports. Custom code can include new custom constants, variables, functions, or subroutines. You can include read-only references to built-in collections such as the Parameters collection. However, you cannot pass sets of report data values to custom functions; specifically, custom aggregates are not supported.
26
31
27
32
> [!IMPORTANT]
28
33
> For time-sensitive calculations that are evaluated once at run-time and that you want to remain the same value throughout report processing, consider whether to use a report variable or group variable. For more information, see [Report and Group Variables Collections References (Report Builder and SSRS)](../../reporting-services/report-design/built-in-collections-report-and-group-variables-references-report-builder.md).
@@ -45,7 +50,7 @@ ms.author: maggies
45
50
2. Preview a report with references to custom assemblies in local mode.
46
51
47
52
## <aname="Common"></a> Including References to Commonly Used Functions
48
-
Use the **Expression** dialog box to view a categorized list of common functions built-in to [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)]. When you expand **Common Functions** and click a category, the **Item** pane displays the list of functions that you include in an expression. The common functions include classes from the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)]<xref:System.Math> and <xref:System.Convert> namespaces and [!INCLUDE[vbprvb](../../includes/vbprvb-md.md)] run-time library functions. For convenience, you can view the most commonly used functions in the **Expression** dialog box, where they are listed by category: Text, Date and Time, Math, Inspection, Program Flow, Aggregate, Financial, Conversion, and Miscellaneous. Less commonly used functions do not appear in the list but can still be used in an expression.
53
+
Use the **Expression** dialog box to view a categorized list of common functions built-in to Report Builder. When you expand **Common Functions** and click a category, the **Item** pane displays the list of functions that you include in an expression. The common functions include classes from the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)]<xref:System.Math> and <xref:System.Convert> namespaces and [!INCLUDE[vbprvb](../../includes/vbprvb-md.md)] run-time library functions. For convenience, you can view the most commonly used functions in the **Expression** dialog box, where they are listed by category: Text, Date and Time, Math, Inspection, Program Flow, Aggregate, Financial, Conversion, and Miscellaneous. Less commonly used functions do not appear in the list but can still be used in an expression.
49
54
50
55
To use a built-in function, double-click the function name in the Item pane. A description of the function appears in the Description pane and an example of the function call appears in the Example pane. In the code pane, when you type the function name followed by a left parenthesis **(**, the IntelliSense help displays each valid syntax for the function call. For example, to calculate the maximum value for a field named `Quantity` in a table, add the simple expression `=Max(` to the Code pane, and then use the smart tags to view all possible valid syntaxes for the function call. To complete this example, type `=Max(Fields!Quantity.Value)`.
51
56
@@ -155,7 +160,7 @@ End Function
155
160
## <aname="Custom"></a> Including References to Code from Custom Assemblies
156
161
To use custom assemblies in a report, you must first create the assembly, make it available to Report Designer, add a reference to the assembly in the report, and then use an expression in the report to refer to the methods contained in that assembly. When the report is deployed to the report server, you must also deploy the custom assembly to the report server.
157
162
158
-
For information about creating a custom assembly and making it available to [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)], see [Using Custom Assemblies with Reports](../../reporting-services/custom-assemblies/using-custom-assemblies-with-reports.md).
163
+
For information about creating a custom assembly and making it available to Report Builder, see [Using Custom Assemblies with Reports](../../reporting-services/custom-assemblies/using-custom-assemblies-with-reports.md).
159
164
160
165
To refer to custom code in an expression, you must call the member of a class within the assembly. How you do this depends on whether the method is static or instance-based. Static methods within a custom assembly are available globally within the report. You can access static methods in expressions by specifying the namespace, class, and method name. The following example calls the method **ToGBP**, which converts the value of the **StandardCost** value from dollar to pounds sterling:
Copy file name to clipboardExpand all lines: docs/reporting-services/report-design/customize-the-data-and-display-of-a-map-or-map-layer-report-builder-and-ssrs.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: "Customize the Data and Display of a Map or Map Layer (Report Builder) | Microsoft Docs"
3
-
description: Improve the user experience of data and display with changes to legends, color, labels, and resolution in Report Builder.
2
+
title: "Customize the display of a map or map layer in a paginated report | Microsoft Docs"
3
+
description: Improve the user experience of data and display in a paginated report with changes to legends, color, labels, and resolution in Report Builder.
# Customize the Data and Display of a Map or Map Layer (Report Builder and SSRS)
29
-
After you add a map or map layer to a [!INCLUDE[ssRSnoversion_md](../../includes/ssrsnoversion-md.md)] paginated report by using a wizard, you might want to change the way the map looks in the report. You can make improvements by considering the following ideas:
28
+
# Customize the display of a map or map layer in a paginated report (Report Builder)
After you add a map or map layer to a paginated report by using a wizard, you might want to change the way the map looks in the report. You can make improvements by considering the following ideas:
30
33
31
34
- To help your users understand how to interpret the data display on a map, you can add legends and a color scale, and add labels and tooltips.
When creating paginated reports with parameters in Report Builder, you can customize the Parameters pane. In report design view, you can drag a parameter to a specific column and row in the Parameters pane. You can add and remove columns to change the layout of the pane.
16
19
17
20
When you drag a parameter to a new column and row in the pane, the parameter order changes in the **Report Data** pane. When you change the order of the parameter in the **Report Data** pane, the location of the parameter in the pane is changed. For more information about why parameter order is important, see [Change the Order of a Report Parameter (Report Builder and SSRS)](../../reporting-services/report-design/change-the-order-of-a-report-parameter-report-builder-and-ssrs.md).
Copy file name to clipboardExpand all lines: docs/reporting-services/report-design/data-regions-and-maps-report-builder-and-ssrs.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: "Data Regions and Maps (Report Builder) | Microsoft Docs"
3
-
description: Explore the types and characteristics of data regions and maps to design the display from your report datasets in Report Builder.
2
+
title: "Data regions and maps in a paginated report | Microsoft Docs"
3
+
description: Explore the types and characteristics of data regions and maps to design the display from your paginated report datasets in Report Builder.
A data region is an object in a report that displays data from a report dataset. Report data can be displayed as numbers and text in a table, matrix, or list; graphically in a chart or gauge; and against a geographic background in a map. Tables, matrices, and lists are all based on the *tablix* data region, which expands as needed to display all the data from the dataset. A tablix data region supports multiple row and column groups and both static and dynamic rows and columns. A chart displays multiple series and category groups in a variety of chart formats. A gauge displays a single value or an aggregated value for a dataset. A map displays spatial data as map elements that can vary in appearance based on aggregated data from a dataset.
17
+
# Data regions and maps in a paginated report (Report Builder)
A data region is an object in a paginated report that displays data from a report dataset. Report data can be displayed as numbers and text in a table, matrix, or list; graphically in a chart or gauge; and against a geographic background in a map. Tables, matrices, and lists are all based on the *tablix* data region, which expands as needed to display all the data from the dataset. A tablix data region supports multiple row and column groups and both static and dynamic rows and columns. A chart displays multiple series and category groups in a variety of chart formats. A gauge displays a single value or an aggregated value for a dataset. A map displays spatial data as map elements that can vary in appearance based on aggregated data from a dataset.
19
22
20
23
You can save a data region or map as a *report part*. Read more about [Report Parts](../../reporting-services/report-design/report-parts-report-builder-and-ssrs.md).
Copy file name to clipboardExpand all lines: docs/reporting-services/report-design/data-types-in-expressions-report-builder-and-ssrs.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: "Data Types in Expressions (Report Builder) | Microsoft Docs"
3
-
description: Explore how data types represent different kinds of data so that the data can be stored and processed in Report Builder.
2
+
title: "Data types in expressions in a paginated report | Microsoft Docs"
3
+
description: Explore how data types represent different kinds of data in a paginated report so that the data can be stored and processed in Report Builder.
# Data Types in Expressions (Report Builder and SSRS)
16
-
Data types represent different kinds of data so that it can be stored and processed efficiently. Typical data types include text (also known as strings), numbers with and without decimal places, dates and times, and images. Values in a report must be an Report Definition Language (RDL) data type. You can format a value according to your preference when you display it in a report. For example, a field that represents currency is stored in the report definition as a floating point number, but can be displayed in a variety of formats depending on the format property you choose.
15
+
# Data types in expressions in a paginated report (Report Builder)
Data types represent different kinds of data in a paginated report so that it can be stored and processed efficiently. Typical data types include text (also known as strings), numbers with and without decimal places, dates and times, and images. Values in a report must be an Report Definition Language (RDL) data type. You can format a value according to your preference when you display it in a report. For example, a field that represents currency is stored in the report definition as a floating point number, but can be displayed in a variety of formats depending on the format property you choose.
17
20
18
21
For more information about display formats, see [Formatting Report Items (Report Builder and SSRS)](../../reporting-services/report-design/formatting-report-items-report-builder-and-ssrs.md).
You can change the color palette for a paginated report chart by selecting a pre-defined palette or defining a custom palette. Custom palettes are chart-specific.
Copy file name to clipboardExpand all lines: docs/reporting-services/report-design/display-data-point-labels-outside-a-pie-chart-report-builder-and-ssrs.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: "Display Data Point Labels Outside a Pie Chart (Report Builder) | Microsoft Docs"
3
-
description: Discover how displaying the labels outside a pie chart might create more room for longer data labels in Report Builder.
2
+
title: "Display data point labels outside a pie chart in a paginated report | Microsoft Docs"
3
+
description: Discover how displaying the labels outside a pie chart in a paginated report might create more room for longer data labels in Report Builder.
# Display Data Point Labels Outside a Pie Chart (Report Builder and SSRS)
16
-
In [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)], pie chart labeling is optimized to display labels on only several slices of data. Labels may overlap if the pie chart contains too many slices. One solution is to display the labels outside the pie chart, which may create more room for longer data labels. If you find that your labels still overlap, you can create more space for them by enabling 3D. This reduces the diameter of the pie chart, creating more space around the chart.
15
+
# Display data point labels outside a pie chart in a paginated report (Report Builder)
In paginated reports, pie chart labeling is optimized to display labels on only several slices of data. Labels may overlap if the pie chart contains too many slices. One solution is to display the labels outside the pie chart, which may create more room for longer data labels. If you find that your labels still overlap, you can create more space for them by enabling 3D. This reduces the diameter of the pie chart, creating more space around the chart.
0 commit comments