Merge pull request #12268 from MicrosoftDocs/main

Pushing monthly updates to live

powerbi-docs/connect-data/incremental-refresh-overview.md

@@ -7,7 +7,7 @@ ms.reviewer: chwade
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: concept-article
-ms.date: 08/13/2024
+ms.date: 08/20/2024
 #customer intent: As a Power BI user, I want to learn how to configure and use incremental refresh in Power BI to capture fast-moving data, so that I can improve the performance of model refreshes and reduce resource consumption.
 ---
 # Incremental refresh and real-time data for semantic models
@@ -152,9 +152,6 @@ For *very large* models in Premium capacities that likely contain billions of ro
 
 By default, the current date and time is determined based on Coordinated Universal Time (UTC) at the time of refresh. For on-demand and scheduled refreshes, you can configure a different time zone under 'Refresh' that will be taken into account when determining the current date and time. For example, a refresh that occurs at 8:00 PM Pacific Time (US and Canada) with a time zone configured determines the current date and time based on Pacific Time, not UTC, which would return the next day. 
 
-> [!NOTE]
-> The time zone configuration is taken into account even if the scheduled refresh is disabled.
-
 :::image type="content" source="media/incremental-refresh-overview/time-zone.png" alt-text="Screenshot of Scheduled refresh dialog showing the Time zone input field":::
 
 Refresh operations not invoked through the Power BI service, such as the [XMLA TMSL refresh command](/analysis-services/tmsl/refresh-command-tmsl?view=power-bi-premium-current&preserve-view=true) or [enhanced refresh API](/power-bi/connect-data/asynchronous-refresh#parameters), do not consider the configured scheduled refresh time zone and default to UTC.

powerbi-docs/create-reports/desktop-custom-format-strings.md

@@ -18,20 +18,60 @@ With custom format strings in **Power BI Desktop**, you can customize how fields
 
 ![Screenshot of Power BI desktop in Modeling view, highlighting Custom in the Format dropdown menu.](media/desktop-custom-format-strings/custom-format-strings-01.png)
 
+Format strings exist on three levels:
+
+-	**Model**. You can set a format string for fields in the model or use a [dynamic format string](../create-reports/desktop-dynamic-format-strings.md) to format your measure. Anywhere you use that field the format string is applied, unless overridden by a visual or element level format string. 
+-	**Visual**. You can set format strings on any column, measure, or visual calculation that is on your visual, even if they already had a format string. In that case the model level format string is overridden, and the visual level format string is used. If you change the aggregation on a field, which invalidates a previously set visual level format string, the format string is removed. Visual level format strings for fields are persisted for fields, but not for visual calculations. If you set a visual level format string on a field and then remove and readd that field to the same visual, the visual level format string is reinstated. In contrast, for a visual calculation, the format string isn't reinstated. 
+-	**Element**. You can set a format string for data labels and for specific elements of the new card and the new slicer visuals. This level will be expanded to include more in the future. Any format string you set here overrides the format string set on the visual and model level.
+
+These levels are hierarchical, with the model level being the lowest level and the element level the highest. A format string defined on a column, measure, or visual calculation on a higher level overrides what was defined on a lower level. 
+
+Since visual calculations aren't in the model, they can't have a format string set on the model level but can on the visual, or element level. Measures and columns can have format strings on all three levels:
+
+| **Level** | **Impacts** | **Available for**|
+| --- | --- | --- |
+| Element | Selected element of the selected visual | Measures, Columns, Visual Calculations |
+| Visual | Selected visual | Measures, Columns, Visual Calculations |
+| Model | All visuals, all pages, all reports on the same model | Measures, Columns |
+
+![Diagram showing the three levels of format strings available (model, visual, element. It also shows that visual calculations can only have visual and element level format strings, while measures and columns can have format strings on all levels.](media/desktop-custom-format-strings/custom-format-strings-levels.png)
+
+The element level format string is only available to specific visuals and data labels at this time.
+
 ## How to use custom format strings
 
-To create custom format strings, select the field in the **Modeling** view, and then select the dropdown arrow under **Format** in the **Properties** pane.
+To use custom format strings, you first need to decide which level you're going to work on: Model, Visual or Element.
+
+### Add a model level format string
+To create custom format strings in the model, select the field in the **Modeling** view, and then select the dropdown arrow under **Format** in the **Properties** pane.
 
 ![Screenshot of the Properties pane, highlighting the Format menu.](media/desktop-custom-format-strings/custom-format-strings-02.png)
 
 Once you've selected **Custom** from the **Format** dropdown menu, choose from a list of commonly used format strings.
 
 ![Screenshot of the Formatting menu, highlighting Custom.](media/desktop-custom-format-strings/custom-format-strings-03.png)
 
+### Add a visual level format string
+To create a visual level format string, first add the field or [visual calculation](../transform-model/desktop-visual-calculations-overview.md) to your visual. Then, with your visual selected, open the format pane and go to the **General** section of the format pane. Find the **Format data** settings and configure the format string there:
+
+![Screenshot of the Format pane for a visual, showing the Data format settings in the General section.](media/desktop-custom-format-strings/custom-format-strings-visual-level-format-string.png)
+
+> [!NOTE]
+> For now, you will need to enter a [.NET format string](/dotnet/standard/base-types/formatting-types#format-strings-and-net-types) instead of a [VBA format string](#supported-custom-format-syntax). This is a temporary issue that will be resolved in a future release.
+
+### Add an element level format string
+To create an element level format string, open the format pane and find the format string sections for the element you want to set the format on. Keep in mind that not all elements support format strings. To set a format string on a data label, open the **Visual** section of the format pane, set **Data Labels** > **Value** > **Display units** to custom and enter the format code:
+
+![Screenshot of the Format pane for a visual, showing the Value format settings for Data Labels in the Visual section.](media/desktop-custom-format-strings/custom-format-strings-element-level-format-string.png)
+
+
 ## Supported custom format syntax
 
 Custom format strings follow the VBA style syntax, common to Excel and other Microsoft products, but they don't support all syntax used in other products.
 
+> [!NOTE]
+> For now, visual level format strings require you to enter a [.NET format string](/dotnet/standard/base-types/formatting-types#format-strings-and-net-types) instead. This is a temporary issue that will be resolved in a future release.
+
 The following tables define the syntax supported in Power BI.
 
 ### Supported Date symbols
@@ -138,6 +178,10 @@ The following table identifies characters you can use to create **user-defined n
 | ( **\\** ) | Display the next character in the format string. To display a character that has special meaning as a literal character, precede it with a backslash (\\). The backslash itself isn't displayed. Using a backslash is the same as enclosing the next character in double quotation marks. To display a backslash, use two backslashes (\\\\). Date-formatting and time-formatting characters (a, c, d, h, m, n, p, q, s, t, w, /, and :) can't be displayed as literal characters, the numeric-formatting characters (#, 0, %, E, e, comma, and period), and the string-formatting characters (@, &, <, >, and !). |
 | ("ABC") | Display the string inside the double quotation marks (" "). |
 
+## Considerations and limitations
+
+- You can't set a custom format string for fields that are of type string or boolean.
+
 ## Related content
 
 For more information, see:

powerbi-docs/create-reports/desktop-excel-stunning-report.md

@@ -7,7 +7,7 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: pbi-reports-dashboards
 ms.topic: tutorial
-ms.date: 08/16/2024
+ms.date: 08/20/2024
 LocalizationGroup: Data from files
 ---
 # Tutorial: From Excel workbook to stunning report in Power BI Desktop
@@ -16,7 +16,7 @@ LocalizationGroup: Data from files
 
 In this tutorial, you build a beautiful report from start to finish in 20 minutes! 
 
-:::image type="content" source="media/desktop-excel-stunning-report/power-bi-excel-formatted-report.png" alt-text="Screenshot of finished Power BI report." lightbox="media/desktop-excel-stunning-report/power-bi-excel-formatted-report.png"::: 
+:::image type="content" source="media/desktop-excel-stunning-report/power-bi-excel-report-service.png" alt-text="Screenshot of your completed Power B I report in the Power B I service." lightbox="media/desktop-excel-stunning-report/power-bi-excel-report-service.png"::: 
 
 Your manager wants to see a report on your latest sales figures. They've requested an executive summary of: 
 
@@ -224,9 +224,9 @@ Create a bar chart to determine which companies and segments to invest in.
 
 1. Drag the chart so it's wide enough to fill the space under the two upper charts.
 
-    :::image type="content" source="media/desktop-excel-stunning-report/power-bi-clustered-column-chart-inline.png" alt-text="Screenshot of a clustered column chart." lightbox="media/desktop-excel-stunning-report/power-bi-clustered-column-chart-inline.png":::
+    :::image type="content" source="media/desktop-excel-stunning-report/power-bi-line-column-chart-inline.png" alt-text="Screenshot of a line chart." lightbox="media/desktop-excel-stunning-report/power-bi-line-column-chart-inline.png":::
 
-    Looks like the company should continue to invest in the Paseo product and target the Small Business and Government segments.  
+    It looks like the company should continue to invest in the Paseo product and target the Small Business and Government segments.  
 
 ### Visual 5: Year slicer 
 
@@ -236,7 +236,7 @@ Slicers are a valuable tool for filtering the visuals on a report page to a spec
 **Date slicer using the original table**
 
 1. In the Data pane, select the **Date** field in the Financials table. Drag it to the blank area on the left of the canvas. 
-2. In the Visualizations pane, choose **Slicer**. 
+1. In the Visualizations pane, choose **Slicer**. 
 
     Slicer is the icon with a funnel next to a tab, but without the small lightning bolt. Power BI automatically creates a numeric range slicer. 
 
@@ -247,18 +247,18 @@ Slicers are a valuable tool for filtering the visuals on a report page to a spec
 **Date slicer using the DAX table**
 
 1. In the Data pane, select the **Date** field in the Calendar table. Drag it to the blank area on the left of the canvas. 
-2. In the Visualizations pane, choose **Slicer**. 
-3. In the Data section of the Visualizations pane, select the drop-down in **Data**. Remove Quarter and Day so only Year and Month are left. 
+1. In the Visualizations pane, choose **Slicer**. 
+1. In the Data section of the Visualizations pane, select the drop-down in **Data**. Remove Quarter and Day so only Year and Month are left. 
 
     :::image type="content" source="media/desktop-excel-stunning-report/power-bi-date-hierarchy-trim.png" alt-text="Screenshot of changing the Date hierarchy.":::
 
-4. Expand each year and resize the visual, so all months are visible.
+1. Expand each year and resize the visual, so all months are visible.
 
     :::image type="content" source="media/desktop-excel-stunning-report/power-bi-hierarchy-date-slicer.png" alt-text="Screenshot of date hierarchy slicer.":::
 
     We'll use this slicer in the finished report.
 
-Now if your manager asks to see just 2013 data, you can use either slicer to select years, or specific months of each year.
+Now if your manager asks to see just 2013 data, you can use the slicer to select years, or specific months of each year.
 
 ### Extra credit: Format the report
 
@@ -306,7 +306,7 @@ Make the following changes on the **Format** tab in the Visualizations pane.
 
 Here's how your final polished report will look:  
 
-:::image type="content" source="media/desktop-excel-stunning-report/power-bi-excel-formatted-report.png" alt-text="Screenshot of final, formatted report." lightbox="media/desktop-excel-stunning-report/power-bi-excel-formatted-report.png":::
+:::image type="content" source="media/desktop-excel-stunning-report/power-bi-line-column-chart-inline.png" alt-text="Screenshot of final, formatted report." lightbox="media/desktop-excel-stunning-report/power-bi-line-column-chart-inline.png":::
 
 In summary, this report answers your manager’s top questions: 
 

powerbi-docs/developer/projects/projects-azdo.md

@@ -7,7 +7,7 @@ ms.reviewer: ruiromano
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: concept-article
-ms.date: 05/31/2024
+ms.date: 08/13/2024
 #customer intent: As a Power BI developer, I want to learn how to use Azure DevOps integration with Power BI Desktop projects so that I can streamline my development processes, source control, and collaboration with Azure DevOps Git repositories.
 ---
 

powerbi-docs/developer/projects/projects-build-pipelines.md

@@ -7,7 +7,7 @@ ms.reviewer: ruiromano
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: tutorial
-ms.date: 02/17/2024
+ms.date: 08/13/2024
 ---
 
 # Power BI Project (PBIP) and Azure DevOps build pipelines for validation

powerbi-docs/developer/projects/projects-dataset.md

@@ -7,7 +7,7 @@ ms.reviewer: ruiromano
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: conceptual
-ms.date: 03/14/2024
+ms.date: 08/13/2024
 ---
 
 # Power BI Desktop project semantic model folder

powerbi-docs/developer/projects/projects-git.md

@@ -7,7 +7,7 @@ ms.reviewer: ruiromano
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: concept-article
-ms.date: 05/31/2024
+ms.date: 08/13/2024
 #customer intent: As a Power BI developer, I want to learn how to use Git integration with Power BI Desktop projects so that I can streamline my development processes, source control, and collaboration with Git repositories.
 ---
 

powerbi-docs/developer/projects/projects-overview.md

@@ -7,7 +7,7 @@ ms.reviewer: ruiromano
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: conceptual
-ms.date: 07/24/2024
+ms.date: 08/13/2024
 ---
 
 # Power BI Desktop projects (PREVIEW)

powerbi-docs/developer/projects/projects-report.md

@@ -7,7 +7,7 @@ ms.reviewer: ruiromano
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: conceptual
-ms.date: 03/27/2024
+ms.date: 08/13/2024
 ---
 
 # Power BI Desktop project report folder

powerbi-docs/docfx.json

@@ -64,6 +64,25 @@
               "**/*.md": [
                  "show_binary_rating"
               ]
+          },
+          "ms.subservice": {
+              "collaborate-share/**/*.md": "pbi-collaborate-share",
+              "connect-data/**/*.md": "pbi-data-sources",
+              "consumer/**/*.md": "pbi-explore",
+              "create-reports/**/*.md": "pbi-reports-dashboards",
+              "developer/**/*.md": "powerbi-developer",
+              "enterprise/**/*.md": "powerbi-admin",
+              "fundamentals/**/*.md": "pbi-fundamentals",
+              "guidance/**/*.md": "admin",
+              "guided-learning/**/*.md": "*",
+              "learning-catalog/**/*.md": "*",
+              "natural-language/**/*.md": "powerbi-ai",
+              "paginated-reports/**/*.md": "pbi-reports-dashboards",
+              "report-server/**/*.md": "powerbi-report-server",
+              "support/**/*.md": "pbi-troubleshooting",
+              "transform-model/**/*.md": "pbi-transform-model",
+              "troubleshoot/**/*.md": "*",
+              "visuals/**/*.md": "pbi-visuals"
           }
     },
     "template": [],