Update 26.1#272
Open
pollyndos wants to merge 9 commits into
Open
Conversation
ritazakhodyaeva
left a comment
ritazakhodyaeva
left a comment
Collaborator
There was a problem hiding this comment.
add suggestions
arminal
reviewed
Jun 19, 2026
| --- | ||
| # Coloring | ||
|
|
||
| The Dashboard Designer associates dimension values/measures and specified colors to paint dashboard item elements. This topic describes how to configure color settings in the WinForms Designer. |
Contributor
There was a problem hiding this comment.
What do you mean associates? This sentence sounds incomplete.
|  | ||
|
|
||
| Corresponding _State_ fields are painted with the same colors, so you can associate and compare data from all dashboard items. This happens because all items use **Global Colors** (the default setting). You can see the switch to **Global Colors** in the Ribbon. Click **Edit Colors** to modify the colors used in the palette: | ||
| Identical colors and styles correspond to the same _State_ values, so you can associate and compare data across all dashboard items. All items use **Global Colors** by default (you can toggle this in the Ribbon). Click **Edit Colors** to modify the colors and styles used in the palette: |
Contributor
There was a problem hiding this comment.
Suggested change
| Identical colors and styles correspond to the same _State_ values, so you can associate and compare data across all dashboard items. All items use **Global Colors** by default (you can toggle this in the Ribbon). Click **Edit Colors** to modify the colors and styles used in the palette: | |
| Identical colors and styles correspond to the same _State_ values, so you can associate and compare data across all dashboard items. All items use **Global Colors** by default (you can toggle this in the Ribbon). Click **Edit Colors** to modify colors and styles used in the palette: |
| If you want to use an independent set of colors in the selected dashboard item, switch to the **Local Color Scheme**. | ||
| If you want to use an independent set of colors and styles in the selected dashboard item, switch to the **Local Color Scheme**. | ||
|
|
||
| You can see the Treemap's arguments that use colors from the **Local Color Scheme**: |
Contributor
There was a problem hiding this comment.
Suggested change
| You can see the Treemap's arguments that use colors from the **Local Color Scheme**: | |
| You can see Treemap arguments that use colors from the **Local Color Scheme**: |
|  | ||
|  | ||
|
|
||
| For this dashboard item, the **Color Scheme** dialog will contain combinations of all dimension values and a specific measure. |
Contributor
There was a problem hiding this comment.
what do you mean by "and a specific measure"?
|
|
||
| For a global color scheme, the dashboard reserves automatically generated colors for specific values regardless of the filter state. | ||
| * A **Local Color Scheme** uses an independent set of colors for each dashboard item. The image below shows Pie segments that use colors from a local color scheme. These colors do not affect the Chart items that use a global scheme. | ||
| * A **Local Color Scheme** uses an independent set of colors and styles for each dashboard item. The image below shows Pie segments that use colors from a local color scheme. These colors do not affect the Chart items that use a global scheme. |
Contributor
There was a problem hiding this comment.
Suggested change
| * A **Local Color Scheme** uses an independent set of colors and styles for each dashboard item. The image below shows Pie segments that use colors from a local color scheme. These colors do not affect the Chart items that use a global scheme. | |
| * A **Local Color Scheme** uses an independent set of colors and styles for each dashboard item. The image below shows Pie segments that use colors from a local color scheme. These colors do not affect Chart items that use a global scheme. |
|
|
||
| ## Hide Report Controls in Documents Exported to Specific Formats | ||
|
|
||
| You can specify the **Can Publish Options** setting in the Properties grid to exclude report controls from certain export formats. |
Contributor
There was a problem hiding this comment.
Suggested change
| You can specify the **Can Publish Options** setting in the Properties grid to exclude report controls from export formats of your choosing. |
|  | ||
|
|
||
| Set the **PDF/UA Compatibility** property to **PDF/UA-1** to conform the exported PDF document to PDF/UA specification. Then, export the report to PDF format. | ||
| Set the **PDF/UA Compatibility** property to **PDF/UA-1** or **PDF/UA-2** to conform the exported PDF document to the PDF/UA specification. Then, export the report to PDF format. |
Contributor
There was a problem hiding this comment.
Suggested change
| Set the **PDF/UA Compatibility** property to **PDF/UA-1** or **PDF/UA-2** to conform the exported PDF document to the PDF/UA specification. Then, export the report to PDF format. | |
| Set the **PDF/UA Compatibility** property to **PDF/UA-1** or **PDF/UA-2** to conform the exported PDF document to PDF/UA specification. Then, export the report as a PDF. |
|
|
||
| Use this table to map report controls to accessibility structure roles in exported PDF files. | ||
|
|
||
| The table describes the following: |
| The table describes the following: | ||
|
|
||
| - How each control behaves when the **Accessible Role** property is set to **Default**. | ||
| - Roles you can assign to ensure that screen readers correctly identify the element's purpose in the exported PDF document. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Roles you can assign to ensure that screen readers correctly identify element purpose in the exported PDF document. |
| * The **Never Embedded Fonts** export option is not supported for PDF/UA-compatible documents. | ||
| * If a report contains an **XRPdfContent** control, you cannot export the report to PDF with the PDF/UA option enabled. | ||
| * If a report contains editing fields, the exported document does not comply with PDF/UA requirements. | ||
| * Hyperlinks are exported without the semantic tags required by **PDF/UA-2**. |
Contributor
There was a problem hiding this comment.
Suggested change
| * Hyperlinks are exported without the semantic tags required by **PDF/UA-2**. | |
| * Hyperlinks are exported without semantic tags required by **PDF/UA-2**. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.