From bb275907b1021b995270da47ad83911426a3e5a7 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Tue, 3 Sep 2024 14:09:28 -0600 Subject: [PATCH 01/14] Testing V2 --- powerbi-docs/transform-model/desktop-query-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerbi-docs/transform-model/desktop-query-overview.md b/powerbi-docs/transform-model/desktop-query-overview.md index 8ed0870aaa..9e26356cd2 100644 --- a/powerbi-docs/transform-model/desktop-query-overview.md +++ b/powerbi-docs/transform-model/desktop-query-overview.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: pbi-transform-model ms.topic: conceptual -ms.date: 10/24/2023 +ms.date: 09/01/2024 LocalizationGroup: Transform and shape data --- # Query overview in Power BI Desktop From 9f3c549ca9d73f5a3245eeb9aa582d441b677968 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Tue, 10 Sep 2024 10:05:53 -0600 Subject: [PATCH 02/14] Creating new Vis Troubleshooting article --- powerbi-docs/troubleshoot/TOC.yml | 2 + .../power-bi-visualization-troubleshoot.md | 121 ++++++++++++++++++ 2 files changed, 123 insertions(+) create mode 100644 powerbi-docs/visuals/power-bi-visualization-troubleshoot.md diff --git a/powerbi-docs/troubleshoot/TOC.yml b/powerbi-docs/troubleshoot/TOC.yml index d49fb6159a..8cfff640b0 100644 --- a/powerbi-docs/troubleshoot/TOC.yml +++ b/powerbi-docs/troubleshoot/TOC.yml @@ -101,6 +101,8 @@ - name: Visuals expanded: false items: + - name: Troubleshoot visualizations in Power BI + href: ../visuals/power-bi-visualization-troubleshoot.md - name: Debug Power BI custom visuals href: ../developer/visuals/visuals-how-to-debug.md - name: Troubleshoot custom visuals in Power BI Desktop for Power BI Report Server diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md new file mode 100644 index 0000000000..79688b4c6d --- /dev/null +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -0,0 +1,121 @@ +--- +title: Troubleshoot visualizations in Power BI +description: Troubleshoot visualizations in Power BI, including common issues and workarounds to overcome known obstacles or potential problems. +author: JaedenArmstrong +ms.author: miguelmyers +ms.reviewer: davidi +ms.service: powerbi +ms.subservice: pbi-visuals +ms.topic: +ms.date: 09/03/2024 +ms.custom: TSG - Troubleshooting Guide +LocalizationGroup: Visualizations +#customer intent: As a Power BI user, I want to be aware of the various considerations, limitations, workarounds to overcome known obstacles or potential issues with Power BI Visualizations, so I can effectively and easily identify solutions in both Power BI Desktop and Power BI service. +--- +# Troubleshoot visualizations in Power BI + +[!INCLUDE [applies-yes-desktop-yes-service](../includes/applies-yes-desktop-yes-service.md)] + +The document provides considerations and limitations for Power BI visualizations, and how to troubleshoot common content distribution issues. It addresses potential issues, and known issues, while offering solutions to ensure consistency and optimal performance in report design and user experience. + +## Fonts + +This section addresses potential issues users may encounter with fonts in Power BI. + +### Default fonts + +- MacOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these are not included by default on MacOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), MacOS will default to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their MacOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and MacOS platforms to avoid such issues. + +### Custom fonts + +- When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. +- The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts are not embedded within the report itself. If a font is not installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it is recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy will facilitate the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. + +## Slicers and filters + +This section addresses potential issues users may encounter with slicers and filters. + +### Clear button + +- Users may experience difficulty locating the ‘Clear’ selection option within slicers. This challenge is due to the ‘Clear’ button’s design, which is embedded within the slicer header and only becomes visible upon mouse hover. The ‘Clear’ function is represented by a subtle eraser icon located in the top right corner of the slicer’s visual container. Its inconspicuous placement can lead to it being easily missed by users. If the eraser icon is not present, it typically indicates that the report creator has opted to disable the visual header in the report settings. To rectify this issue, the report creator must re-enable the visual header within the report’s settings. This action will make the eraser icon reappear, thus restoring the ‘Clear’ selection functionality for users. +- In the new slicer (Preview), users may find it challenging to locate the ‘Clear’ button as it is situated in the visual header, not within the slicer header as previously designed. The absence of the ‘Clear’ button upon hovering over the slicer’s visual container typically signifies that the visual headers have been disabled by the report creator. To make the ‘Clear’ button accessible again, the report creator needs to enable the visual headers. This action will restore the visibility of the ‘Clear’ button, allowing users to easily reset their slicer selections. + +### Persistent filters + +- In Power BI Desktop, the default setting may allow user filters to be saved automatically. This can lead to complications if users modify the original report filters, potentially causing discrepancies in the displayed data. When filters are modified and saved, they become persistent, meaning any changes made by the user will be retained, and when the same user returns to the report, they'll see the saved slicer selections. To prevent such issues, navigate to the ‘Options’ dialog within Power BI Desktop. Locate the ‘[Persistent filters](../create-reports/power-bi-report-filter.md#allow-saving-filters)’ section and select the option ‘*Don’t allow end users to save filters on this file in the Power BI service*’. This setting ensures that user modifications to filters are not saved, maintaining the report’s original filter configuration as published by the author. +- In the Power BI service, there is a possibility that users may unintentionally save personal filters, which can disrupt what the report author had intended to display. This issue occurs when a user applies filters to a report and those filters are saved as part of their personal view. When returning to the report, and filters have been saved, the same user will see the filtered report rather than what the report author published. To address this problem, navigate to ‘File’ in the Power BI service, then select ‘Settings’. Within the ‘[Persistent filters](../create-reports/power-bi-report-filter.md#allow-saving-filters)’ section, opt for ‘*Don’t allow end users to save filters on this report*’. This setting will prevent the saving of individual filter configurations, thus maintaining the report’s original filter configuration as published by the author. + +### Selection + +- The term ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ can be misleading in its operation. Contrary to what the term suggests, ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ does not actually select every item. Instead, it operates on an inverted selection principle, meaning that any item you deselect becomes part of the query. This approach is more efficient as it avoids sending thousands of values in the query. By only sending the deselected values in a negated filter, we streamline the process and reduce the query load. +- When using the Slicer to filter reports, the ‘Selected Values’ may persist as selected even when they are no longer applicable, potentially leading to confusion and a misleading restatement of selected items. The Slicer saves the selected values, which can remain visible and selected in subsequent views of the report. However, if the underlying data or user permissions change, these selections may no longer be relevant or appropriate. Report authors should exercise caution to ensure that they do not save and publish reports with selected items that may be inappropriate for certain users, particularly in environments where Row-Level Security (RLS) is implemented. It is advisable to clear any selections that should not be universally applied before saving and distributing the report. + +### What if + +- The '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters in Power BI are designed to handle up to 1000 unique values. If a parameter exceeds this limit, the values will be evenly sampled, which may not meet the needs of detailed scenario analysis. This limitation is in place to ensure performance and manageability within Power BI. When more than 1000 unique values are needed, the parameter values are sampled to fit within this constraint, potentially leading to a loss of granularity. To work around this limitation, you can adjust the granularity of your '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters to ensure that the total number of unique values does not exceed 1000. + +## Colors + +This section addresses potential issues users may encounter with report colors. + +### Series color assignment + +- In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors reserved for a series may change depending on the sequence in which report pages are viewed or when different filters are applied, such as with Row-Level Security (RLS). To maintain color consistency for dynamic series, it is recommended to explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. + +## Themes + +This section addresses potential issues users may encounter when working with custom themes. + +### Default settings + +- When setting visual-specific format options in Power BI, this can override any of the predefined properties in a [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports). This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) settings will not apply if existing format options have been set for a particular visual. To allow [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) colors to take effect, you will need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) colors should apply as intended, provided that an explicit color has not been set for that visual. + +## Maps + +This section addresses potential issues users may encounter when working with map visuals. + +### Bing maps + +- Bing Maps is being deprecated and should no longer be used for geographical data representation in Power BI. As part of the transition to more advanced and supported services, [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) is recommended as the alternative to Bing Maps. [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) provides a rich set of geographical data services and features that are continually updated. To adapt to this change, users should start utilizing [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) for their mapping needs in Power BI. By selecting your Bing Map visuals, you can click the Azure Map visual icon to convert them, and maintain the majority of your format settings. Alternatively, you may notice the popup when opening the report in Desktop, with an option to convert all your Bing Maps to Azure Maps. For a comprehensive understanding of [Azure Maps](/azure/azure-maps/power-bi-visual-get-started), including how to get started, what data is sent to Azure, and its limitations, refer to the detailed documentation provided by Microsoft. + +### Geocoding + +- To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Power BI, make sure your model has pristine data for each distinct location entity and avoid concatenating strings. Assign the correct Data Category to each location entity, like ‘State’ or ‘Zipcode’. Build a Location hierarchy within your model or place multiple fields in the location field well for precise [geocoding](/azure/azure-maps/power-bi-visual-geocode). Use the ‘Expand All Down’ icon to drill into the lowest hierarchy level, which includes all higher levels. This helps resolve ambiguities in locations with the same names, such as distinguishing ‘Paris, Texas’ from ‘Paris, France’. Adding ‘Country’ into your Location hierarchy and using the ‘Drill Down’ or ‘Expand All’ functions will improve [geocoding](/azure/azure-maps/power-bi-visual-geocode) outcomes. + +## Report locale + +This section addresses potential issues users may encounter with dates in visuals. + +### Format strings + +[Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer) + +- In Power BI, certain visual elements do not utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format does not match the user’s expectations.  For these elements, Power BI leverages the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. + +## Tooltips + +This section addresses potential issues users may experience with tooltips. + +### Page tooltips + +- Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations) are not displayed for Dashboards or Dashboard tiles. Users expecting to see tooltips when hovering over these elements may find this behavior confusing. This is by design - Dashboards in Power BI do not currently support Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations). Tooltips are a feature designed for use within individual report pages rather than the Dashboard view. While report tooltips can be highly informative within reports, they are not available for Dashboards. As a best practice, it’s recommended to design Dashboards with this in mind, ensuring that necessary information is clearly presented without relying on tooltips. + +### Line chart tooltips + +- Users may notice that Line Chart Tooltips are not consistently displaying column labels, or that the displayed information changes with slicer value adjustments. This can cause confusion when trying to interpret the data represented in the chart. This behavior is likely due to the [high-density](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) line sampling feature in Power BI, which is designed to optimize performance. When there is a large amount of data, Power BI samples the data to create a more manageable number of data points for the line chart. Understanding this is by design, users can adjust their expectations of tooltip consistency in [high-density](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) scenarios. If precise data points are required, consider using alternative visualizations that can handle large datasets without sampling, or adjust the chart settings to reduce the density of the data points, if possible. + +## Images + +This section addresses potential issues users may encounter with including images into their visualizations. + +### Image URLS + +- If an image within a Power BI report is not rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires that the [image URL](../create-reports/power-bi-images-tables.md#considerations) be anonymously accessible and do not require a sign-in to view, meaning they cannot be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window; if the image loads without requiring a sign-in, it is correctly configured for use in Power BI. Note that loading images from a local path is also not supported in Power BI Desktop or in the Power Bi service. +- Likewise, Power BI mobile apps will only display if the [image URL](../create-reports/power-bi-images-tables.md#considerations) is anonymously accessible. Again, the image cannot be hosted on a site that requires a sign-in, such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power Bi service. + +## Related content + +- [Visualization types in Power BI](power-bi-visualization-types-for-reports-and-q-and-a.md) +- [Add visuals to a Power BI report (part 1)](power-bi-report-add-visualizations-i.md) +- [Add visuals to a Power BI report (part 2)](power-bi-report-add-visualizations-ii.md) +- [Get started formatting report visualizations](service-getting-started-with-color-formatting-and-axis-properties.md) From ca83fcfd5643306d149ca6fe669659c0475adc33 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Tue, 17 Sep 2024 11:53:47 -0600 Subject: [PATCH 03/14] Edits to article before adding content from engineer --- .../power-bi-visualization-troubleshoot.md | 53 ++++++++++--------- 1 file changed, 28 insertions(+), 25 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index 79688b4c6d..daae3e80ed 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -6,7 +6,7 @@ ms.author: miguelmyers ms.reviewer: davidi ms.service: powerbi ms.subservice: pbi-visuals -ms.topic: +ms.topic: conceptual ms.date: 09/03/2024 ms.custom: TSG - Troubleshooting Guide LocalizationGroup: Visualizations @@ -18,19 +18,6 @@ LocalizationGroup: Visualizations The document provides considerations and limitations for Power BI visualizations, and how to troubleshoot common content distribution issues. It addresses potential issues, and known issues, while offering solutions to ensure consistency and optimal performance in report design and user experience. -## Fonts - -This section addresses potential issues users may encounter with fonts in Power BI. - -### Default fonts - -- MacOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these are not included by default on MacOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), MacOS will default to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their MacOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and MacOS platforms to avoid such issues. - -### Custom fonts - -- When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. -- The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts are not embedded within the report itself. If a font is not installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it is recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy will facilitate the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. - ## Slicers and filters This section addresses potential issues users may encounter with slicers and filters. @@ -39,6 +26,7 @@ This section addresses potential issues users may encounter with slicers and fil - Users may experience difficulty locating the ‘Clear’ selection option within slicers. This challenge is due to the ‘Clear’ button’s design, which is embedded within the slicer header and only becomes visible upon mouse hover. The ‘Clear’ function is represented by a subtle eraser icon located in the top right corner of the slicer’s visual container. Its inconspicuous placement can lead to it being easily missed by users. If the eraser icon is not present, it typically indicates that the report creator has opted to disable the visual header in the report settings. To rectify this issue, the report creator must re-enable the visual header within the report’s settings. This action will make the eraser icon reappear, thus restoring the ‘Clear’ selection functionality for users. - In the new slicer (Preview), users may find it challenging to locate the ‘Clear’ button as it is situated in the visual header, not within the slicer header as previously designed. The absence of the ‘Clear’ button upon hovering over the slicer’s visual container typically signifies that the visual headers have been disabled by the report creator. To make the ‘Clear’ button accessible again, the report creator needs to enable the visual headers. This action will restore the visibility of the ‘Clear’ button, allowing users to easily reset their slicer selections. +- It’s recommended that report authors click the ‘Clear’ icon and ‘Save’ before publishing, especially for range slicers. For other slicer types, you may prefer to save selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. ### Persistent filters @@ -54,6 +42,27 @@ This section addresses potential issues users may encounter with slicers and fil - The '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters in Power BI are designed to handle up to 1000 unique values. If a parameter exceeds this limit, the values will be evenly sampled, which may not meet the needs of detailed scenario analysis. This limitation is in place to ensure performance and manageability within Power BI. When more than 1000 unique values are needed, the parameter values are sampled to fit within this constraint, potentially leading to a loss of granularity. To work around this limitation, you can adjust the granularity of your '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters to ensure that the total number of unique values does not exceed 1000. +## Report locale + +This section addresses potential issues users may encounter with dates in visuals. + +### Format strings + +- In Power BI, certain visual elements do not utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format does not match the user’s expectations.  For these elements, Power BI leverages the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. + +## Fonts + +This section addresses potential issues users may encounter with fonts in Power BI. + +### Default fonts + +- MacOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these are not included by default on MacOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), MacOS will default to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their MacOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and MacOS platforms to avoid such issues. + +### Custom fonts + +- When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. +- The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts are not embedded within the report itself. If a font is not installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it is recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy will facilitate the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. + ## Colors This section addresses potential issues users may encounter with report colors. @@ -68,7 +77,11 @@ This section addresses potential issues users may encounter when working with cu ### Default settings -- When setting visual-specific format options in Power BI, this can override any of the predefined properties in a [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports). This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) settings will not apply if existing format options have been set for a particular visual. To allow [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) colors to take effect, you will need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) colors should apply as intended, provided that an explicit color has not been set for that visual. +- When setting visual-specific format options in Power BI, this can override any of the predefined properties in a custom theme. This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any custom theme settings will not apply if existing format options have been set for a particular visual. + + For example, to allow [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) to take effect, you will need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) should apply as intended, provided that an explicit color has not been set for that visual. + + As another example, if “Legend Position = Left” has been specified in a custom theme file, but something else has been set at the visual level, the user would need to ‘Reset to Default’ to allow the custom theme to apply. ## Maps @@ -82,16 +95,6 @@ This section addresses potential issues users may encounter when working with ma - To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Power BI, make sure your model has pristine data for each distinct location entity and avoid concatenating strings. Assign the correct Data Category to each location entity, like ‘State’ or ‘Zipcode’. Build a Location hierarchy within your model or place multiple fields in the location field well for precise [geocoding](/azure/azure-maps/power-bi-visual-geocode). Use the ‘Expand All Down’ icon to drill into the lowest hierarchy level, which includes all higher levels. This helps resolve ambiguities in locations with the same names, such as distinguishing ‘Paris, Texas’ from ‘Paris, France’. Adding ‘Country’ into your Location hierarchy and using the ‘Drill Down’ or ‘Expand All’ functions will improve [geocoding](/azure/azure-maps/power-bi-visual-geocode) outcomes. -## Report locale - -This section addresses potential issues users may encounter with dates in visuals. - -### Format strings - -[Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer) - -- In Power BI, certain visual elements do not utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format does not match the user’s expectations.  For these elements, Power BI leverages the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. - ## Tooltips This section addresses potential issues users may experience with tooltips. From f7b55e58620320a8eeb8f9a628956313705c2e20 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Tue, 17 Sep 2024 13:33:07 -0600 Subject: [PATCH 04/14] PBI Visualizations - WIP Final Edit --- .../power-bi-visualization-troubleshoot.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index daae3e80ed..b5fc75e9a2 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -24,14 +24,13 @@ This section addresses potential issues users may encounter with slicers and fil ### Clear button -- Users may experience difficulty locating the ‘Clear’ selection option within slicers. This challenge is due to the ‘Clear’ button’s design, which is embedded within the slicer header and only becomes visible upon mouse hover. The ‘Clear’ function is represented by a subtle eraser icon located in the top right corner of the slicer’s visual container. Its inconspicuous placement can lead to it being easily missed by users. If the eraser icon is not present, it typically indicates that the report creator has opted to disable the visual header in the report settings. To rectify this issue, the report creator must re-enable the visual header within the report’s settings. This action will make the eraser icon reappear, thus restoring the ‘Clear’ selection functionality for users. -- In the new slicer (Preview), users may find it challenging to locate the ‘Clear’ button as it is situated in the visual header, not within the slicer header as previously designed. The absence of the ‘Clear’ button upon hovering over the slicer’s visual container typically signifies that the visual headers have been disabled by the report creator. To make the ‘Clear’ button accessible again, the report creator needs to enable the visual headers. This action will restore the visibility of the ‘Clear’ button, allowing users to easily reset their slicer selections. -- It’s recommended that report authors click the ‘Clear’ icon and ‘Save’ before publishing, especially for range slicers. For other slicer types, you may prefer to save selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. +- Users may experience difficulty locating the ‘Clear’ button for the original slicer visuals. The ‘Clear’ button, indicated by an eraser icon, is located in the Slicer Header and only becomes visible upon mouse hover. Some report authors may choose to disable the Slicer Header and enable the Visual Container Title which is disabled by default for these visuals. To ensure access to the 'Clear' button, restore the Slicer Header visibility. For the New Slicer visuals, we have moved the 'Clear' button into the Visual Container Header and have removed the concept of a separate Slicer Header. For these New Slicers, if the report author has disabled the Visual Container Header, the 'Clear' button will not be available. + +- It’s recommended that report authors click the ‘Clear’ icon and ‘Save’ in that state before publishing, especially for range slicers. For other slicer types, you may prefer to intentionally save a default selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. Use care to ensure slicers are cleared, or intentionally set, when creating Bookmarks. ### Persistent filters -- In Power BI Desktop, the default setting may allow user filters to be saved automatically. This can lead to complications if users modify the original report filters, potentially causing discrepancies in the displayed data. When filters are modified and saved, they become persistent, meaning any changes made by the user will be retained, and when the same user returns to the report, they'll see the saved slicer selections. To prevent such issues, navigate to the ‘Options’ dialog within Power BI Desktop. Locate the ‘[Persistent filters](../create-reports/power-bi-report-filter.md#allow-saving-filters)’ section and select the option ‘*Don’t allow end users to save filters on this file in the Power BI service*’. This setting ensures that user modifications to filters are not saved, maintaining the report’s original filter configuration as published by the author. -- In the Power BI service, there is a possibility that users may unintentionally save personal filters, which can disrupt what the report author had intended to display. This issue occurs when a user applies filters to a report and those filters are saved as part of their personal view. When returning to the report, and filters have been saved, the same user will see the filtered report rather than what the report author published. To address this problem, navigate to ‘File’ in the Power BI service, then select ‘Settings’. Within the ‘[Persistent filters](../create-reports/power-bi-report-filter.md#allow-saving-filters)’ section, opt for ‘*Don’t allow end users to save filters on this report*’. This setting will prevent the saving of individual filter configurations, thus maintaining the report’s original filter configuration as published by the author. +- Power BI Reports have a setting that allows end-user slicer and filter choices to be saved automatically and reapplied when they return to view a report later on. This setting is enabled by default.  This can lead to different experiences for different users. When reports also utilize Bookmarks, this can potentially lead to unexpected results. If you prefer that all report consumers start from the exact same filter state, you can disable Persistent Filters on the report. In Desktop, open the ‘Options’ dialog from the 'File' menu, and click 'Report settings' in the 'Current File' section. In the service, you can find the same setting in the Report Settings Blade.  Choose ‘Don’t allow end users to save filters on this file in the Power BI service’. This setting ensures that user modifications to filters are not saved, maintaining the report’s original filter configuration as published by the author. Users can always reset to the authored state by clicking the 'Reset to default' button in the top right area. ### Selection @@ -62,6 +61,7 @@ This section addresses potential issues users may encounter with fonts in Power - When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. - The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts are not embedded within the report itself. If a font is not installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it is recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy will facilitate the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. +- Also note that Custom Fonts may not be available when an Export command is executed that causes rendering on the server, such Export to PDF or Image generation with Copy, PowerPoint, or email Subscriptions. ## Colors @@ -69,7 +69,7 @@ This section addresses potential issues users may encounter with report colors. ### Series color assignment -- In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors reserved for a series may change depending on the sequence in which report pages are viewed or when different filters are applied, such as with Row-Level Security (RLS). To maintain color consistency for dynamic series, it is recommended to explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. +- In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors chosen for a series may change depending on the sequence in which report pages are viewed, when filters are applied in a different order, or depending on the user if Row-Level Security (RLS) is employed. To maintain color consistency for dynamic series, it is recommended to explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. ## Themes @@ -89,7 +89,7 @@ This section addresses potential issues users may encounter when working with ma ### Bing maps -- Bing Maps is being deprecated and should no longer be used for geographical data representation in Power BI. As part of the transition to more advanced and supported services, [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) is recommended as the alternative to Bing Maps. [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) provides a rich set of geographical data services and features that are continually updated. To adapt to this change, users should start utilizing [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) for their mapping needs in Power BI. By selecting your Bing Map visuals, you can click the Azure Map visual icon to convert them, and maintain the majority of your format settings. Alternatively, you may notice the popup when opening the report in Desktop, with an option to convert all your Bing Maps to Azure Maps. For a comprehensive understanding of [Azure Maps](/azure/azure-maps/power-bi-visual-get-started), including how to get started, what data is sent to Azure, and its limitations, refer to the detailed documentation provided by Microsoft. +- Bing Maps for Power BI is being deprecated and should no longer be used for geographical data representation in Power BI. As part of the transition to more advanced and business focused services, [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) is recommended as the alternative to Bing Maps for Power BI. [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) provides a rich set of geographical data services and features that are continually updated. To adapt to this change, users should start utilizing [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) for their mapping needs in Power BI. You can convert your Bing Map visuals to Azure Maps by selecting them and clicking the Azure Map icon in the Visualization Pane. We will attempt to preserve your formatting settings during conversion. Alternatively, you may notice the popup when opening the report in Desktop, with an option to convert all your Bing Maps to Azure Maps. For a comprehensive understanding of [Azure Maps](/azure/azure-maps/power-bi-visual-get-started), including how to get started, what data is sent to Azure, and its limitations, refer to the detailed documentation provided by Microsoft. ### Geocoding @@ -101,11 +101,11 @@ This section addresses potential issues users may experience with tooltips. ### Page tooltips -- Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations) are not displayed for Dashboards or Dashboard tiles. Users expecting to see tooltips when hovering over these elements may find this behavior confusing. This is by design - Dashboards in Power BI do not currently support Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations). Tooltips are a feature designed for use within individual report pages rather than the Dashboard view. While report tooltips can be highly informative within reports, they are not available for Dashboards. As a best practice, it’s recommended to design Dashboards with this in mind, ensuring that necessary information is clearly presented without relying on tooltips. +- Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations) are not displayed for Dashboard Visual Tiles or Report-Page Dashboard Tiles.  This is by design - Dashboards in Power BI do not currently support Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations). Dashboard Tiles take minimal snapshots of pinned content, and do not have a reference to the Report Page that is designed as a Tooltip.  As a best practice, it’s recommended to design Dashboards with this in mind, ensuring that necessary information is clearly presented without relying on report-page tooltips. ### Line chart tooltips -- Users may notice that Line Chart Tooltips are not consistently displaying column labels, or that the displayed information changes with slicer value adjustments. This can cause confusion when trying to interpret the data represented in the chart. This behavior is likely due to the [high-density](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) line sampling feature in Power BI, which is designed to optimize performance. When there is a large amount of data, Power BI samples the data to create a more manageable number of data points for the line chart. Understanding this is by design, users can adjust their expectations of tooltip consistency in [high-density](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) scenarios. If precise data points are required, consider using alternative visualizations that can handle large datasets without sampling, or adjust the chart settings to reduce the density of the data points, if possible. +- Users may notice that Line Chart Tooltips are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) ## Images From c8255b1438164fde425b42b41fd55bd5a5227a39 Mon Sep 17 00:00:00 2001 From: Jill Grant Date: Tue, 17 Sep 2024 15:40:40 -0600 Subject: [PATCH 05/14] Apply suggestions from code review Acrolinx fixes --- powerbi-docs/visuals/power-bi-visualization-troubleshoot.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index b5fc75e9a2..e0f2a80717 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -113,8 +113,8 @@ This section addresses potential issues users may encounter with including image ### Image URLS -- If an image within a Power BI report is not rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires that the [image URL](../create-reports/power-bi-images-tables.md#considerations) be anonymously accessible and do not require a sign-in to view, meaning they cannot be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window; if the image loads without requiring a sign-in, it is correctly configured for use in Power BI. Note that loading images from a local path is also not supported in Power BI Desktop or in the Power Bi service. -- Likewise, Power BI mobile apps will only display if the [image URL](../create-reports/power-bi-images-tables.md#considerations) is anonymously accessible. Again, the image cannot be hosted on a site that requires a sign-in, such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power Bi service. +- If an image within a Power BI report is not rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires that the [image URL](../create-reports/power-bi-images-tables.md#considerations) be anonymously accessible and do not require a sign-in to view, meaning they cannot be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window; if the image loads without requiring a sign-in, it is correctly configured for use in Power BI. Note that loading images from a local path is also not supported in Power BI Desktop or in the Power BI service. +- Likewise, Power BI mobile apps will only display if the [image URL](../create-reports/power-bi-images-tables.md#considerations) is anonymously accessible. Again, the image cannot be hosted on a site that requires a sign-in, such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power BI service. ## Related content From d70e7ef33d97eea863700a0d7e0bb547c8e54297 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Tue, 17 Sep 2024 18:09:21 -0600 Subject: [PATCH 06/14] Updating article to improve Acrolinx score. --- .../power-bi-visualization-troubleshoot.md | 50 ++++++++++--------- 1 file changed, 27 insertions(+), 23 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index b5fc75e9a2..eb02bf7d03 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -20,26 +20,27 @@ The document provides considerations and limitations for Power BI visualizations ## Slicers and filters -This section addresses potential issues users may encounter with slicers and filters. +This section addresses potential issues users might encounter with slicers and filters. ### Clear button -- Users may experience difficulty locating the ‘Clear’ button for the original slicer visuals. The ‘Clear’ button, indicated by an eraser icon, is located in the Slicer Header and only becomes visible upon mouse hover. Some report authors may choose to disable the Slicer Header and enable the Visual Container Title which is disabled by default for these visuals. To ensure access to the 'Clear' button, restore the Slicer Header visibility. For the New Slicer visuals, we have moved the 'Clear' button into the Visual Container Header and have removed the concept of a separate Slicer Header. For these New Slicers, if the report author has disabled the Visual Container Header, the 'Clear' button will not be available. +Users might experience difficulty locating the ‘Clear’ button for the original slicer visuals. The ‘Clear’ button, indicated by an eraser icon, is located in the Slicer Header and only becomes visible upon mouse hover. Some report authors might choose to disable the Slicer Header and enable the Visual Container Title which is disabled by default for these visuals. To ensure access to the 'Clear' button, restore the Slicer Header visibility. For the New Slicer visuals, we moved the 'Clear' button into the Visual Container Header and removed the concept of a separate Slicer Header. For these New Slicers, if the report author disabled the Visual Container Header, the 'Clear' button won't be available. -- It’s recommended that report authors click the ‘Clear’ icon and ‘Save’ in that state before publishing, especially for range slicers. For other slicer types, you may prefer to intentionally save a default selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. Use care to ensure slicers are cleared, or intentionally set, when creating Bookmarks. +We recommended report authors select the ‘Clear’ icon and ‘Save’ in that state before publishing, especially for range slicers. For other slicer types, you might prefer to intentionally save a default selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. Use care to ensure slicers are cleared, or intentionally set, when creating Bookmarks. ### Persistent filters -- Power BI Reports have a setting that allows end-user slicer and filter choices to be saved automatically and reapplied when they return to view a report later on. This setting is enabled by default.  This can lead to different experiences for different users. When reports also utilize Bookmarks, this can potentially lead to unexpected results. If you prefer that all report consumers start from the exact same filter state, you can disable Persistent Filters on the report. In Desktop, open the ‘Options’ dialog from the 'File' menu, and click 'Report settings' in the 'Current File' section. In the service, you can find the same setting in the Report Settings Blade.  Choose ‘Don’t allow end users to save filters on this file in the Power BI service’. This setting ensures that user modifications to filters are not saved, maintaining the report’s original filter configuration as published by the author. Users can always reset to the authored state by clicking the 'Reset to default' button in the top right area. +Power BI Reports have a setting that allows end-user slicer and filter choices to be saved automatically and reapplied when they return to view a report later on. This setting is enabled by default. This can lead to different experiences for different users. When reports also utilize Bookmarks, this can potentially lead to unexpected results. If you prefer that all report consumers start from the exact same filter state, you can disable Persistent Filters on the report. In Power BI Desktop, open the 'Options' dialog from the 'File' menu, and select 'Report settings' in the 'Current File' section. In the Power BI service, you can open 'Settings' from the 'File' menu to open the Report Settings panel, then toggle the Persistent Filters option to enable the 'Don't allow end user to save filters on this report.' option. This setting ensures that user modifications to filters aren't saved, maintaining the report’s original filter configuration as published by the author. Users can always reset to the authored state by clicking the 'Reset to default' button in the top right area. ### Selection -- The term ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ can be misleading in its operation. Contrary to what the term suggests, ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ does not actually select every item. Instead, it operates on an inverted selection principle, meaning that any item you deselect becomes part of the query. This approach is more efficient as it avoids sending thousands of values in the query. By only sending the deselected values in a negated filter, we streamline the process and reduce the query load. -- When using the Slicer to filter reports, the ‘Selected Values’ may persist as selected even when they are no longer applicable, potentially leading to confusion and a misleading restatement of selected items. The Slicer saves the selected values, which can remain visible and selected in subsequent views of the report. However, if the underlying data or user permissions change, these selections may no longer be relevant or appropriate. Report authors should exercise caution to ensure that they do not save and publish reports with selected items that may be inappropriate for certain users, particularly in environments where Row-Level Security (RLS) is implemented. It is advisable to clear any selections that should not be universally applied before saving and distributing the report. +The term ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ can be misleading in its operation. Contrary to what the term suggests, ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ doesn't actually select every item. Instead, it operates on an inverted selection principle, meaning that any item you deselect becomes part of the query. This approach is more efficient as it avoids sending thousands of values in the query. By only sending the deselected values in a negated filter, we streamline the process and reduce the query load. + +When using the Slicer to filter reports, the ‘Selected Values’ may persist as selected even when they're no longer applicable, potentially leading to confusion and a misleading restatement of selected items. The Slicer saves the selected values, which can remain visible and selected in subsequent views of the report. However, if the underlying data or user permissions change, these selections may no longer be relevant or appropriate. Report authors should exercise caution to ensure that they don't save and publish reports with selected items that might be inappropriate for certain users, particularly in environments where Row-Level Security (RLS) is implemented. It's advisable to clear any selections that shouldn't be universally applied before saving and distributing the report. ### What if -- The '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters in Power BI are designed to handle up to 1000 unique values. If a parameter exceeds this limit, the values will be evenly sampled, which may not meet the needs of detailed scenario analysis. This limitation is in place to ensure performance and manageability within Power BI. When more than 1000 unique values are needed, the parameter values are sampled to fit within this constraint, potentially leading to a loss of granularity. To work around this limitation, you can adjust the granularity of your '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters to ensure that the total number of unique values does not exceed 1000. +The '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters in Power BI are designed to handle up to 1,000 unique values. If a parameter exceeds this limit, the values are evenly sampled, which may not meet the needs of detailed scenario analysis. This limitation is in place to ensure performance and manageability within Power BI. When more than 1,000 unique values are needed, the parameter values are sampled to fit within this constraint, potentially leading to a loss of granularity. To work around this limitation, you can adjust the granularity of your '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters to ensure that the total number of unique values doesn't exceed 1000. ## Report locale @@ -47,7 +48,7 @@ This section addresses potential issues users may encounter with dates in visual ### Format strings -- In Power BI, certain visual elements do not utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format does not match the user’s expectations.  For these elements, Power BI leverages the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. +In Power BI, certain visual elements don't utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format doesn't match the user’s expectations. For these elements, Power BI leverages the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. ## Fonts @@ -55,13 +56,15 @@ This section addresses potential issues users may encounter with fonts in Power ### Default fonts -- MacOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these are not included by default on MacOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), MacOS will default to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their MacOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and MacOS platforms to avoid such issues. +macOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these aren't included by default on macOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), macOS defaults to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their macOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and macOS platforms to avoid such issues. ### Custom fonts -- When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. -- The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts are not embedded within the report itself. If a font is not installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it is recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy will facilitate the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. -- Also note that Custom Fonts may not be available when an Export command is executed that causes rendering on the server, such Export to PDF or Image generation with Copy, PowerPoint, or email Subscriptions. +When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. + +The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts aren't embedded within the report itself. If a font isn't installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it's recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy facilitates the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. + +Also note that Custom Fonts may not be available when an Export command is executed that causes rendering on the server, such Export to PDF or Image generation with Copy, PowerPoint, or email Subscriptions. ## Colors @@ -69,7 +72,7 @@ This section addresses potential issues users may encounter with report colors. ### Series color assignment -- In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors chosen for a series may change depending on the sequence in which report pages are viewed, when filters are applied in a different order, or depending on the user if Row-Level Security (RLS) is employed. To maintain color consistency for dynamic series, it is recommended to explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. +In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors that are chosen for a series may change depending on the sequence in which report pages are viewed, when filters are applied in a different order, or depending on the user if Row-Level Security (RLS) is employed. To maintain color consistency for dynamic series, it's recommended to explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. ## Themes @@ -77,11 +80,11 @@ This section addresses potential issues users may encounter when working with cu ### Default settings -- When setting visual-specific format options in Power BI, this can override any of the predefined properties in a custom theme. This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any custom theme settings will not apply if existing format options have been set for a particular visual. +When setting visual-specific format options in Power BI, this can override any of the predefined properties in a custom theme. This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any custom theme settings won't apply if existing format options have been set for a particular visual. - For example, to allow [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) to take effect, you will need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) should apply as intended, provided that an explicit color has not been set for that visual. +For example, to allow [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) to take effect, you need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) should apply as intended, if an explicit color isn't set for that visual. - As another example, if “Legend Position = Left” has been specified in a custom theme file, but something else has been set at the visual level, the user would need to ‘Reset to Default’ to allow the custom theme to apply. +As another example, when you specify “Legend Position = Left” in a custom theme file, but specify something else at the visual level, you should always ‘Reset to Default’ to allow the custom theme to apply. ## Maps @@ -89,11 +92,11 @@ This section addresses potential issues users may encounter when working with ma ### Bing maps -- Bing Maps for Power BI is being deprecated and should no longer be used for geographical data representation in Power BI. As part of the transition to more advanced and business focused services, [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) is recommended as the alternative to Bing Maps for Power BI. [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) provides a rich set of geographical data services and features that are continually updated. To adapt to this change, users should start utilizing [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) for their mapping needs in Power BI. You can convert your Bing Map visuals to Azure Maps by selecting them and clicking the Azure Map icon in the Visualization Pane. We will attempt to preserve your formatting settings during conversion. Alternatively, you may notice the popup when opening the report in Desktop, with an option to convert all your Bing Maps to Azure Maps. For a comprehensive understanding of [Azure Maps](/azure/azure-maps/power-bi-visual-get-started), including how to get started, what data is sent to Azure, and its limitations, refer to the detailed documentation provided by Microsoft. +Bing Maps for Power BI is being deprecated and should no longer be used for geographical data representation in Power BI. As part of the transition to more advanced and business focused services, [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) is recommended as the alternative to Bing Maps for Power BI. [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) provides a rich set of geographical data services and features that are continually updated. To adapt to this change, users should start utilizing [Azure Maps](/azure/azure-maps/power-bi-visual-get-started) for their mapping needs in Power BI. You can convert your Bing Map visuals to Azure Maps by selecting them and clicking the Azure Map icon in the Visualization Pane. We attempt to preserve your formatting settings during conversion. Alternatively, you might notice the popup when opening the report in Desktop, with an option to convert all your Bing Maps to Azure Maps. For a comprehensive understanding of [Azure Maps](/azure/azure-maps/power-bi-visual-get-started), including how to get started, what data is sent to Azure, and its limitations, refer to the detailed documentation provided by Microsoft. ### Geocoding -- To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Power BI, make sure your model has pristine data for each distinct location entity and avoid concatenating strings. Assign the correct Data Category to each location entity, like ‘State’ or ‘Zipcode’. Build a Location hierarchy within your model or place multiple fields in the location field well for precise [geocoding](/azure/azure-maps/power-bi-visual-geocode). Use the ‘Expand All Down’ icon to drill into the lowest hierarchy level, which includes all higher levels. This helps resolve ambiguities in locations with the same names, such as distinguishing ‘Paris, Texas’ from ‘Paris, France’. Adding ‘Country’ into your Location hierarchy and using the ‘Drill Down’ or ‘Expand All’ functions will improve [geocoding](/azure/azure-maps/power-bi-visual-geocode) outcomes. +To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Power BI, make sure your model has pristine data for each distinct location entity and avoid concatenating strings. Assign the correct Data Category to each location entity, like ‘State’ or ‘Zipcode’. Build a Location hierarchy within your model or place multiple fields in the location field well for precise [geocoding](/azure/azure-maps/power-bi-visual-geocode). Use the ‘Expand All Down’ icon to drill into the lowest hierarchy level, which includes all higher levels. This helps resolve ambiguities in locations with the same names, such as distinguishing ‘Paris, Texas’ from ‘Paris, France’. Adding ‘Country’ into your Location hierarchy, and using the ‘Drill Down’ or ‘Expand All’ functions, improves your desired [geocoding](/azure/azure-maps/power-bi-visual-geocode) outcomes. ## Tooltips @@ -101,20 +104,21 @@ This section addresses potential issues users may experience with tooltips. ### Page tooltips -- Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations) are not displayed for Dashboard Visual Tiles or Report-Page Dashboard Tiles.  This is by design - Dashboards in Power BI do not currently support Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations). Dashboard Tiles take minimal snapshots of pinned content, and do not have a reference to the Report Page that is designed as a Tooltip.  As a best practice, it’s recommended to design Dashboards with this in mind, ensuring that necessary information is clearly presented without relying on report-page tooltips. +Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations) aren't displayed for Dashboard Visual Tiles or Report-Page Dashboard Tiles. By design, Dashboards in Power BI don't currently support Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and-limitations). Dashboard Tiles take minimal snapshots of pinned content, and don't have a reference to the Report Page that is designed as a Tooltip. As a best practice, we recommended designing Dashboards without relying on report-page tooltips to ensure necessary information is clearly presented. ### Line chart tooltips -- Users may notice that Line Chart Tooltips are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) +Users might notice that Line Chart Tooltips are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) ## Images This section addresses potential issues users may encounter with including images into their visualizations. -### Image URLS +### Image URLs + +If an image within a Power BI report isn't rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires the [image URL](../create-reports/power-bi-images-tables.md#considerations) to be anonymously accessible without requiring a sign-in to view. Images can't be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window. If the image loads without requiring a sign-in, you correctly configured the image URL for use in Power BI. Loading images from a local path is also not supported in Power BI Desktop or in the Power BI service. -- If an image within a Power BI report is not rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires that the [image URL](../create-reports/power-bi-images-tables.md#considerations) be anonymously accessible and do not require a sign-in to view, meaning they cannot be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window; if the image loads without requiring a sign-in, it is correctly configured for use in Power BI. Note that loading images from a local path is also not supported in Power BI Desktop or in the Power Bi service. -- Likewise, Power BI mobile apps will only display if the [image URL](../create-reports/power-bi-images-tables.md#considerations) is anonymously accessible. Again, the image cannot be hosted on a site that requires a sign-in, such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power Bi service. +Likewise, Power BI mobile apps can't display the image with an [image URL](../create-reports/power-bi-images-tables.md#considerations) unless it's anonymously accessible. Again, images can't be hosted on sites requiring a sign-in such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power BI service. ## Related content From 56a34c2276715c1f6d6cfe97d2eb12c106f9b3b4 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Tue, 17 Sep 2024 18:29:22 -0600 Subject: [PATCH 07/14] Updates to article to improve Acrolinx score --- .../visuals/power-bi-visualization-troubleshoot.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index eb02bf7d03..9eb115245a 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -48,7 +48,7 @@ This section addresses potential issues users may encounter with dates in visual ### Format strings -In Power BI, certain visual elements don't utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format doesn't match the user’s expectations. For these elements, Power BI leverages the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. +In Power BI, certain visual elements don't utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format doesn't match the user’s expectations. For these elements, Power BI uses the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. ## Fonts @@ -56,13 +56,13 @@ This section addresses potential issues users may encounter with fonts in Power ### Default fonts -macOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these aren't included by default on macOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), macOS defaults to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their macOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and macOS platforms to avoid such issues. +macOS users may encounter font rendering issues with [Microsoft-owned fonts](../fundamentals/power-bi-browsers.md#fonts), as these fonts aren't included by default on macOS systems. Due to the absence of certain [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts), macOS defaults to alternative fonts. This fallback can result in discrepancies in text rendering, particularly in terms of font size and layout consistency. To address this, users can manually install the missing [Microsoft fonts](../fundamentals/power-bi-browsers.md#fonts) on their macOS devices. This ensures that reports and documents render with the intended appearance. Alternatively, report creators can opt for fonts that are commonly available across both Windows and macOS platforms to avoid such issues. ### Custom fonts -When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. The font must be referenced by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. +When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. You must reference the font by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. -The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts aren't embedded within the report itself. If a font isn't installed locally, it will not be displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, it's recommended to use an IT Group Policy for the centralized distribution of fonts within your company. This policy facilitates the installation of the required fonts on all relevant machines, thereby maintaining the intended design and readability of the report. +The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts aren't embedded within the report itself. If a font isn't installed locally, it isn't displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, we recommend using an IT Group Policy for the centralized distribution of fonts within your company. This policy facilitates the installation of the required fonts on all relevant machines, thus maintaining the intended design and readability of the report. Also note that Custom Fonts may not be available when an Export command is executed that causes rendering on the server, such Export to PDF or Image generation with Copy, PowerPoint, or email Subscriptions. @@ -72,7 +72,7 @@ This section addresses potential issues users may encounter with report colors. ### Series color assignment -In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors that are chosen for a series may change depending on the sequence in which report pages are viewed, when filters are applied in a different order, or depending on the user if Row-Level Security (RLS) is employed. To maintain color consistency for dynamic series, it's recommended to explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. +In Power BI, the assignment of [theme colors](../create-reports/desktop-report-themes.md#dynamic-series) to series can vary depending on whether the series is static or dynamic. This can lead to inconsistencies in color representation across different report views. For static series, Power BI assigns theme colors based on the index order of the series. However, for dynamic series, colors are allocated on a first-come, first-served basis. As a result, the colors that are chosen for a series may change depending on the sequence in which report pages are viewed, when filters are applied in a different order, or depending on the user if Row-Level Security (RLS) is employed. To maintain color consistency for dynamic series, we recommend you explicitly define the color for each series within the report’s formatting settings. This ensures that each series retains its designated color regardless of the viewing order or applied filters. ## Themes From 0bdf871419040d336ca9bc1a1f8b9c73519f4814 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Wed, 18 Sep 2024 12:51:30 -0600 Subject: [PATCH 08/14] Nudging the build system --- powerbi-docs/visuals/power-bi-visualization-troubleshoot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index 9eb115245a..2c474b0ab8 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -7,7 +7,7 @@ ms.reviewer: davidi ms.service: powerbi ms.subservice: pbi-visuals ms.topic: conceptual -ms.date: 09/03/2024 +ms.date: 09/18/2024 ms.custom: TSG - Troubleshooting Guide LocalizationGroup: Visualizations #customer intent: As a Power BI user, I want to be aware of the various considerations, limitations, workarounds to overcome known obstacles or potential issues with Power BI Visualizations, so I can effectively and easily identify solutions in both Power BI Desktop and Power BI service. From 75656b0f2d70de76c31a88d8a16fcaca95a69835 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Wed, 18 Sep 2024 13:47:54 -0600 Subject: [PATCH 09/14] ** --- .../power-bi-visualization-troubleshoot.md | 27 ++++++++++--------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index 0208ecd495..03f0e82bac 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -24,23 +24,23 @@ This section addresses potential issues users might encounter with slicers and f ### Clear button -Users might experience difficulty locating the ‘Clear’ button for the original slicer visuals. The ‘Clear’ button, indicated by an eraser icon, is located in the Slicer Header and only becomes visible upon mouse hover. Some report authors might choose to disable the Slicer Header and enable the Visual Container Title which is disabled by default for these visuals. To ensure access to the 'Clear' button, restore the Slicer Header visibility. For the New Slicer visuals, we moved the 'Clear' button into the Visual Container Header and removed the concept of a separate Slicer Header. For these New Slicers, if the report author disabled the Visual Container Header, the 'Clear' button won't be available. +Users might experience difficulty locating the **Clear** button for the original slicer visuals. The **Clear** button, indicated by an eraser icon, is located in the **Slicer Header** and only becomes visible upon mouse hover. Some report authors might choose to disable the **Slicer Header** and enable the **Visual Container Title** which is disabled by default for these visuals. To ensure access to the **Clear** button, *restore* the **Slicer Header** visibility. For the **New Slicer visuals**, we moved the **Clear** button into the **Visual Container Header** and removed the concept of a separate Slicer Header. For these **New Slicers**, if the report author disabled the **Visual Container Header**, the **Clear** button won't available. -We recommended report authors select the ‘Clear’ icon and ‘Save’ in that state before publishing, especially for range slicers. For other slicer types, you might prefer to intentionally save a default selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. Use care to ensure slicers are cleared, or intentionally set, when creating Bookmarks. +We recommended report authors *select* the **Clear** icon and **Save** in that state before publishing, especially for range slicers. For other slicer types, you might intentionally save a default selection so that report consumers start with a specific set of filters, but Date Range slicers typically work best when starting cleared. Use care to ensure slicers are cleared, or intentionally set, when creating Bookmarks. ### Persistent filters -Power BI Reports have a setting that allows end-user slicer and filter choices to be saved automatically and reapplied when they return to view a report later on. This setting is enabled by default. This can lead to different experiences for different users. When reports also utilize Bookmarks, this can potentially lead to unexpected results. If you prefer that all report consumers start from the exact same filter state, you can disable Persistent Filters on the report. In Power BI Desktop, open the 'Options' dialog from the 'File' menu, and select 'Report settings' in the 'Current File' section. In the Power BI service, you can open 'Settings' from the 'File' menu to open the Report Settings panel, then toggle the Persistent Filters option to enable the 'Don't allow end user to save filters on this report.' option. This setting ensures that user modifications to filters aren't saved, maintaining the report’s original filter configuration as published by the author. Users can always reset to the authored state by clicking the 'Reset to default' button in the top right area. +Power BI Reports have a setting that allows end-user slicer and filter choices to be saved automatically and reapplied when they return to view a report later on. This setting, enabled by default, can lead to different experiences for different users. When reports also utilize Bookmarks, it can potentially lead to unexpected results. If you prefer that all report consumers start from the exact same filter state, you can disable Persistent Filters on the report. In **Power BI Desktop**, open the **Options** dialog from the **File** menu, and select **Report settings** in the **Current File** section. In the **Power BI service**, open **Settings** from the **File** menu to display the **Report Settings** panel, then *toggle* the **Persistent Filters** option to enable the **Don't allow end user to save filters on this report** option. This setting ensures that user modifications to filters aren't saved, maintaining the report’s original filter configuration as published by the author. Users can always reset to the authored state by clicking the **Reset to default** button in the top right area. ### Selection -The term ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ can be misleading in its operation. Contrary to what the term suggests, ‘[Select all](power-bi-visualization-slicers.md#selection-controls)’ doesn't actually select every item. Instead, it operates on an inverted selection principle, meaning that any item you deselect becomes part of the query. This approach is more efficient as it avoids sending thousands of values in the query. By only sending the deselected values in a negated filter, we streamline the process and reduce the query load. +The term [**Select all**](power-bi-visualization-slicers.md#selection-controls) can be misleading in its operation. Contrary to what the term suggests, [**Select all**](power-bi-visualization-slicers.md#selection-controls) doesn't actually *select* every item. Instead, it operates on an inverted selection principle, meaning that any item you deselect becomes part of the query. This approach is more efficient as it avoids sending thousands of values in the query. By only sending the deselected values in a negated filter, we streamline the process and reduce the query load. -When using the Slicer to filter reports, the ‘Selected Values’ may persist as selected even when they're no longer applicable, potentially leading to confusion and a misleading restatement of selected items. The Slicer saves the selected values, which can remain visible and selected in subsequent views of the report. However, if the underlying data or user permissions change, these selections may no longer be relevant or appropriate. Report authors should exercise caution to ensure that they don't save and publish reports with selected items that might be inappropriate for certain users, particularly in environments where Row-Level Security (RLS) is implemented. It's advisable to clear any selections that shouldn't be universally applied before saving and distributing the report. +When using the **Slicer** to filter reports, the **Selected Values** may persist as selected even when they're no longer applicable, potentially leading to confusion and a misleading restatement of selected items. The **Slicer** saves the selected values, which can remain visible and selected in subsequent views of the report. However, if the underlying data or user permissions change, these selections may no longer be relevant or appropriate. Report authors should avoid saving and publishing reports with selected items that might be inappropriate for certain users, particularly in environments where Row-Level Security (RLS) is implemented. It's advisable to clear any selections that shouldn't be universally applied before saving and distributing the report. ### What if -The '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters in Power BI are designed to handle up to 1,000 unique values. If a parameter exceeds this limit, the values are evenly sampled, which may not meet the needs of detailed scenario analysis. This limitation is in place to ensure performance and manageability within Power BI. When more than 1,000 unique values are needed, the parameter values are sampled to fit within this constraint, potentially leading to a loss of granularity. To work around this limitation, you can adjust the granularity of your '[What If](../transform-model/desktop-what-if.md#considerations-and-limitations)' parameters to ensure that the total number of unique values doesn't exceed 1000. +The [**What if**](../transform-model/desktop-what-if.md#considerations-and-limitations) parameters in Power BI are designed to handle up to 1,000 unique values. If a parameter exceeds this limit, the values are evenly sampled, which may not meet the needs of detailed scenario analysis. This limitation is in place to ensure performance and manageability within Power BI. When more than 1,000 unique values are needed, the parameter values are sampled to fit within this constraint, potentially leading to a loss of granularity. To work around this limitation, you can adjust the granularity of your [**What If**](../transform-model/desktop-what-if.md#considerations-and-limitations) parameters to ensure that the total number of unique values doesn't exceed 1000. ## Report locale @@ -48,7 +48,7 @@ This section addresses potential issues users may encounter with dates in visual ### Format strings -In Power BI, certain visual elements don't utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format doesn't match the user’s expectations. For these elements, Power BI uses the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [Slicers](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [Cartesian Axis Tick Labels](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the Filter Pane. +In Power BI, certain visual elements don't utilize the model format string for dates to conserve space and present only the necessary detail. This can lead to confusion when the displayed date format doesn't match the user’s expectations. For these elements, Power BI uses the browser’s locale settings to determine the date format. This means that the format may vary depending on the user’s browser configuration, which influences how dates are displayed in the report. To ensure consistency, report creators should be aware of the browser locale’s impact on date formatting. Common areas affected by this include [**Slicers**](../create-reports/desktop-slicer-numeric-range.md#display-formatting-with-the-date-range-slicer), and [**Cartesian Axis Tick Labels**](../visuals/power-bi-visualization-customize-x-axis-and-y-axis.md#considerations-and-limitations), and some sections of the **Filter Pane**. ## Fonts @@ -80,7 +80,7 @@ This section addresses potential issues users may encounter when working with cu ### Default settings -When setting visual-specific format options in Power BI, this can override any of the predefined properties in a custom theme. This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any custom theme settings won't apply if existing format options have been set for a particular visual. +When setting visual-specific format options in Power BI, this can override any of the predefined properties in a custom theme. This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any custom theme settings don't apply if existing format options have been set for a particular visual. For example, to allow [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) to take effect, you need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) should apply as intended, if an explicit color isn't set for that visual. @@ -96,7 +96,7 @@ Bing Maps for Power BI is being deprecated and should no longer be used for geog ### Geocoding -To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Power BI, make sure your model has pristine data for each distinct location entity and avoid concatenating strings. Assign the correct Data Category to each location entity, like ‘State’ or ‘Zipcode’. Build a Location hierarchy within your model or place multiple fields in the location field well for precise [geocoding](/azure/azure-maps/power-bi-visual-geocode). Use the ‘Expand All Down’ icon to drill into the lowest hierarchy level, which includes all higher levels. This helps resolve ambiguities in locations with the same names, such as distinguishing ‘Paris, Texas’ from ‘Paris, France’. Adding ‘Country’ into your Location hierarchy, and using the ‘Drill Down’ or ‘Expand All’ functions, improves your desired [geocoding](/azure/azure-maps/power-bi-visual-geocode) outcomes. +To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Power BI, make sure your model has pristine data for each distinct location entity and avoid concatenating strings. Assign the correct Data Category to each location entity, like *State* or *Zipcode*. Build a Location hierarchy within your model or place multiple fields in the location field well for precise [geocoding](/azure/azure-maps/power-bi-visual-geocode). Use the **Expand All Down** icon to drill into the lowest hierarchy level, which includes all higher levels. This helps resolve ambiguities in locations with the same names, such as distinguishing *Paris, Texas* from *Paris, France*. Adding *Country* into your Location hierarchy, and using the **Drill Down** or **Expand All** functions, improves your desired [geocoding](/azure/azure-maps/power-bi-visual-geocode) outcomes. ## Tooltips @@ -108,7 +108,7 @@ Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and- ### Line chart tooltips -Users might notice that Line Chart Tooltips are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) +Users might notice that Line Chart **Tooltips** are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) ## Images @@ -116,10 +116,11 @@ This section addresses potential issues users may encounter with including image ### Image URLs -If an image within a Power BI report isn't rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires the [image URL](../create-reports/power-bi-images-tables.md#considerations) to be anonymously accessible without requiring a sign-in to view. Images can't be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window. If the image loads without requiring a sign-in, you correctly configured the image URL for use in Power BI. Loading images from a local path is also not supported in Power BI Desktop or in the Power BI service. +If an image within a Power BI report isn't rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires the [image URL](../create-reports/power-bi-images-tables.md#considerations) to be anonymously accessible without requiring a sign-in to view. Images can't be hosted on sites that require authentication, such as SharePoint or OneDrive. -- If an image within a Power BI report is not rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires that the [image URL](../create-reports/power-bi-images-tables.md#considerations) be anonymously accessible and do not require a sign-in to view, meaning they cannot be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window; if the image loads without requiring a sign-in, it is correctly configured for use in Power BI. Note that loading images from a local path is also not supported in Power BI Desktop or in the Power BI service. -- Likewise, Power BI mobile apps will only display if the [image URL](../create-reports/power-bi-images-tables.md#considerations) is anonymously accessible. Again, the image cannot be hosted on a site that requires a sign-in, such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power BI service. +To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window. If the image loads without requiring a sign-in, you correctly configured the image URL for use in Power BI. Loading images from a local path is also not supported in Power BI Desktop or in the Power BI service. + +Likewise, Power BI mobile apps will only display if the [image URL](../create-reports/power-bi-images-tables.md#considerations) is anonymously accessible. Again, the image cannot be hosted on a site that requires a sign-in, such as SharePoint or OneDrive, even if you can see the image in Power BI Desktop or in the Power BI service. ## Related content From 016eec70b7d7a15fa101c7c57831513d1df7fba9 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Wed, 18 Sep 2024 13:50:12 -0600 Subject: [PATCH 10/14] Update wording and content - Final --- powerbi-docs/visuals/power-bi-visualization-troubleshoot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index 03f0e82bac..7df98ca40b 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -116,7 +116,7 @@ This section addresses potential issues users may encounter with including image ### Image URLs -If an image within a Power BI report isn't rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires the [image URL](../create-reports/power-bi-images-tables.md#considerations) to be anonymously accessible without requiring a sign-in to view. Images can't be hosted on sites that require authentication, such as SharePoint or OneDrive. +If an image within a Power BI report isn't rendering, it may be due to the [image URL](../create-reports/power-bi-images-tables.md#considerations) not being anonymously accessible. Power BI requires the [image URL](../create-reports/power-bi-images-tables.md#considerations) to be anonymously accessible without requiring a sign-in to view. Images can't be hosted on sites that require authentication, such as SharePoint or OneDrive. To ensure the [image URL](../create-reports/power-bi-images-tables.md#considerations) is publicly accessible, open the [image URL](../create-reports/power-bi-images-tables.md#considerations) in an InPrivate mode browser window. If the image loads without requiring a sign-in, you correctly configured the image URL for use in Power BI. Loading images from a local path is also not supported in Power BI Desktop or in the Power BI service. From 76598cb4a290c5fb38c9d6afe3f78a428daec734 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Wed, 18 Sep 2024 13:53:46 -0600 Subject: [PATCH 11/14] Removed punctuation for final edit --- powerbi-docs/visuals/power-bi-visualization-troubleshoot.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index 7df98ca40b..e17603f07d 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -82,9 +82,9 @@ This section addresses potential issues users may encounter when working with cu When setting visual-specific format options in Power BI, this can override any of the predefined properties in a custom theme. This occurs because explicit formatting at the visual level takes precedence over theme-level settings. As a result, any custom theme settings don't apply if existing format options have been set for a particular visual. -For example, to allow [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) to take effect, you need to reset the visual colors to default formatting. This can be done by clicking ‘Reset to Default’ within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) should apply as intended, if an explicit color isn't set for that visual. +For example, to allow [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) to take effect, you need to reset the visual colors to default formatting. This can be done by clicking **Reset to Default** within the color formatting options of the visual. Once the specific formatting is cleared, the [custom theme colors](../create-reports/desktop-report-themes.md#situations-when-report-theme-colors-wont-stick-to-your-reports) should apply as intended, if an explicit color isn't set for that visual. -As another example, when you specify “Legend Position = Left” in a custom theme file, but specify something else at the visual level, you should always ‘Reset to Default’ to allow the custom theme to apply. +As another example, when you specify *Legend Position = Left* in a custom theme file, but specify something else at the visual level, you should always **Reset to Default** to allow the custom theme to apply. ## Maps From 5e9dba3326fb7e227ad7fd9be5cb193f0a25e083 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Wed, 18 Sep 2024 14:29:02 -0600 Subject: [PATCH 12/14] Update to Custom fonts section from Matt Lee (engineer) --- powerbi-docs/visuals/power-bi-visualization-troubleshoot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index e17603f07d..7a64ee449c 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -64,7 +64,7 @@ When incorporating a custom font into Power BI reports, it’s essential to spec The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts aren't embedded within the report itself. If a font isn't installed locally, it isn't displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, we recommend using an IT Group Policy for the centralized distribution of fonts within your company. This policy facilitates the installation of the required fonts on all relevant machines, thus maintaining the intended design and readability of the report. -Also note that Custom Fonts may not be available when an Export command is executed that causes rendering on the server, such Export to PDF or Image generation with Copy, PowerPoint, or email Subscriptions. +Also note that custom fonts might not be available or render correctly when an export command is executed that causes rendering on the server, such as exporting to PDF, exporting to Powerpoint, or exporting to images when using email subscriptions. ## Colors From 36f67179bc71b5fccd892d263419aa0994223354 Mon Sep 17 00:00:00 2001 From: Jaeden Armstrong Date: Wed, 18 Sep 2024 14:42:51 -0600 Subject: [PATCH 13/14] Update - spelling correction. --- .../visuals/power-bi-visualization-troubleshoot.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index 7a64ee449c..ce45638af6 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -60,15 +60,15 @@ macOS users may encounter font rendering issues with [Microsoft-owned fonts](../ ### Custom fonts -When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. You must reference the font by its correct operating system (OS) name, which may differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. +When incorporating a custom font into Power BI reports, it’s essential to specify the font correctly in the Custom Theme file. You must reference the font by its correct operating system (OS) name, which could differ from its display name. Using the display name can result in the font not being recognized or applied in the report. To ensure the correct font name is used, navigate to the Fonts section in the Windows Control Panel. Here, you can verify the exact OS name of the font. Once confirmed, use this name in your Custom Theme file to successfully apply the custom font to your Power BI report. The font used in a Power BI report must be installed on the local machine of each end user. This is because fonts aren't embedded within the report itself. If a font isn't installed locally, it isn't displayed correctly when an end user views the report. This can lead to inconsistencies in the report’s appearance and can affect the overall user experience. To ensure uniformity in font usage across all end users, we recommend using an IT Group Policy for the centralized distribution of fonts within your company. This policy facilitates the installation of the required fonts on all relevant machines, thus maintaining the intended design and readability of the report. -Also note that custom fonts might not be available or render correctly when an export command is executed that causes rendering on the server, such as exporting to PDF, exporting to Powerpoint, or exporting to images when using email subscriptions. +Also note that custom fonts might not be available or render correctly when an export command is executed that causes rendering on the server, such as exporting to PDF, exporting to PowerPoint, or exporting to images when using email subscriptions. ## Colors -This section addresses potential issues users may encounter with report colors. +This section addresses potential issues users might encounter with report colors. ### Series color assignment @@ -76,7 +76,7 @@ In Power BI, the assignment of [theme colors](../create-reports/desktop-report-t ## Themes -This section addresses potential issues users may encounter when working with custom themes. +This section addresses potential issues users might encounter when working with custom themes. ### Default settings @@ -88,7 +88,7 @@ As another example, when you specify *Legend Position = Left* in a custom theme ## Maps -This section addresses potential issues users may encounter when working with map visuals. +This section addresses potential issues users might encounter when working with map visuals. ### Bing maps @@ -100,7 +100,7 @@ To ensure [geocoding](/azure/azure-maps/power-bi-visual-geocode) accuracy in Pow ## Tooltips -This section addresses potential issues users may experience with tooltips. +This section addresses potential issues users might experience with tooltips. ### Page tooltips @@ -112,7 +112,7 @@ Users might notice that Line Chart **Tooltips** are displayed differently than o ## Images -This section addresses potential issues users may encounter with including images into their visualizations. +This section addresses potential issues users might encounter with including images into their visualizations. ### Image URLs From 09a404c98efa87b34d67d9e01ad82b528e76ec9c Mon Sep 17 00:00:00 2001 From: Jill Grant Date: Wed, 18 Sep 2024 16:21:57 -0600 Subject: [PATCH 14/14] Update powerbi-docs/visuals/power-bi-visualization-troubleshoot.md Missing period. --- powerbi-docs/visuals/power-bi-visualization-troubleshoot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md index ce45638af6..b4238d4884 100644 --- a/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md +++ b/powerbi-docs/visuals/power-bi-visualization-troubleshoot.md @@ -108,7 +108,7 @@ Report Page [Tooltips](../create-reports/desktop-tooltips.md#considerations-and- ### Line chart tooltips -Users might notice that Line Chart **Tooltips** are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling) +Users might notice that Line Chart **Tooltips** are displayed differently than other charts. By default, we show all series values and a vertical alignment bar to help users compare all series values within a specific category. In some cases, the standard datapoint tooltip will render, such as for Combo Charts and when Line Charts enter high-density sampling due to hitting data limits. Different filters may push the query slightly above or below the limits, resulting in different tooltips at different times for the same line chart visual. For more information about high-density line sampling, see our article: [High-Density Line Sampling in Power BI](../create-reports/desktop-high-density-sampling.md#tooltips-and-high-density-line-sampling). ## Images