Merge pull request #13023 from MicrosoftDocs/main

2/26/2025 PM Publish

powerbi-docs/connect-data/desktop-connect-to-data.md

@@ -8,7 +8,7 @@ ms.custom: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: how-to
-ms.date: 01/04/2023
+ms.date: 02/26/2025
 LocalizationGroup: Connect to data
 ---
 # Connect to data sources in Power BI Desktop
@@ -17,7 +17,7 @@ With Power BI Desktop, you can easily connect to the ever expanding world of dat
 
 There are *all sorts* of data sources available in Power BI Desktop. The following image shows how to connect to data, by selecting **Get data** > **Other** > **Web**.
 
-![Get data from the web](media/desktop-connect-to-data/get-data-from-web.png)
+:::image type="content" source="media/desktop-connect-to-data/get-data-from-web.png" alt-text="Screenshot of selecting web from data sources.":::
 
 ## Example of connecting to data
 

powerbi-docs/connect-data/desktop-data-source-prerequisites.md

@@ -7,7 +7,7 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: conceptual
-ms.date: 02/07/2023
+ms.date: 02/26/2025
 LocalizationGroup: Connect to data
 ---
 # Power BI data source prerequisites

powerbi-docs/connect-data/desktop-data-types.md

@@ -7,7 +7,7 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: concept-article
-ms.date: 12/03/2024
+ms.date: 02/26/2025
 LocalizationGroup: Connect to data
 #customer intent: As a Power BI user, I want to understand the different data types available in Power BI Desktop so that I can properly format and analyze my data.
 ---
@@ -80,17 +80,20 @@ If a required calculation sums most of the positive numbers before summing most
 
 ## Date/time types
 
-Power BI Desktop supports five **Date/Time** data types in Power Query Editor. Both **Date/Time/Timezone** and **Duration** convert during load into the Power BI Desktop data model. The model supports **Date/Time**, or you can format the values as **Date** or **Time** independently.
+Power BI Desktop supports five Date/Time data types in the Power Query Editor. Both **Date/Time/Timezone** and **Duration** are converted during load into the data model, as follows:
 
-- **Date/Time**  represents both a date and time value. The underlying **Date/Time** value is stored as a **Decimal number** type, so you can convert between the two types. The time portion stores as a fraction to whole multiples of 1/300 seconds (3.33 ms). The data type supports dates between years 1900 and 9999.
+**Date/Time** represents both a date and time value. The underlying *Date/Time* value is stored as a *Decimal number*, so you can actually convert between the two.  The time portion is stored as a fraction to whole multiples of 1/300 seconds (3.33 ms).  The data type supports dates between years 1900 and 9999.
 
-- **Date** represents just a date with no time portion.  A **Date** converts into the model as a **Date/Time** value with zero for the fractional value.
+**Date** represents just a date with no time portion. A **Date** converts into the model as a **Date/Time** value with zero for the fractional value.
 
-- **Time** represents just a time with no date portion. A **Time** converts into the model as a **Date/Time** value with no digits to the left of the decimal point.
+**Time** represents just a time with no date portion. A **Time** converts into the model as a **Date/Time** value with no digits to the left of the decimal point.
 
-- **Date/Time/Timezone** represents a UTC date/time with a timezone offset, and converts into **Date/Time** when loaded into the model. The Power BI model doesn't adjust the timezone based on a user's location or locale. A value of 09:00 loaded into the model in the USA displays as 09:00 wherever the report is opened or viewed.
+**Date/Time/Timezone** represents a UTC date/time with a timezone offset, and converts into **Date/Time** when loaded into the model. The Power BI model doesn't adjust the timezone based on a user's location or locale. A value of 09:00 loaded into the model in the USA displays as 09:00 wherever the report is opened or viewed.
 
-- **Duration** represents a length of time, and converts into a **Decimal number** type when loaded into the model. As **Decimal number** type, you can add or subtract the values from **Date/Time** values with correct results, and easily use the values in visualizations that show magnitude.
+**Duration** represents a length of time, and converts into a **Decimal number** when loaded into the model. Therefore, you can add or subtract the values from **Date/Time** values with correct results, and easily use it in visualizations that show magnitude.
+
+> [!NOTE]
+> You can further format a converted **Date/Time** value in the model as **Date** or **Time** using the data types UI in Report, Table and Model view. Keep in mind that formatting doesn't change how data is stored in the model and any calculations or relationships are still evaluated with the **Date/Time** information stored, independent of formatting.
 
 ## Text type
 

powerbi-docs/connect-data/desktop-default-member-multidimensional-models.md

@@ -1,22 +1,22 @@
 ---
-title: Default member in multidimensional models in Power BI
+title: Default member in multidimensional semantic models in Power BI
 description: Learn about how Power BI processes data from a multidimensional model based on where the default member is found.
 author: davidiseminger
 ms.author: davidi
 ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: conceptual
-ms.date: 01/18/2023
+ms.date: 02/26/2025
 LocalizationGroup: Data from files
 ---
-# Work with multidimensional models in Power BI
+# Work with multidimensional semantic models in Power BI
 
-You can connect to multidimensional models in Power BI, and create reports that visualize all sorts of data within the model. With multidimensional models, Power BI applies rules to how it processes data, based on which column is defined as the *default member*.
+You can connect to multidimensional semantic models in Power BI, and create reports that visualize all sorts of data within the model. With multidimensional semantic models, Power BI applies rules to how it processes data, based on which column is defined as the *default member*.
 
-With multidimensional models, Power BI handles data from the model based on where the column that contains the **Default Member** is used. The **DefaultMember** property value for an attribute hierarchy is set in CSDL (Conceptual Schema Definition Language) for a particular column in a multidimensional model. For more information about the default member, see [Attribute properties - Define a default member](/sql/analysis-services/multidimensional-models/attribute-properties-define-a-default-member). When a data analysis expression (DAX) query is executed, the default member specified in the model is applied automatically.
+With multidimensional semantic models, Power BI handles data from the model based on where the column that contains the **Default Member** is used. The **DefaultMember** property value for an attribute hierarchy is set in CSDL (Conceptual Schema Definition Language) for a particular column in a multidimensional model. For more information about the default member, see [Attribute properties - Define a default member](/sql/analysis-services/multidimensional-models/attribute-properties-define-a-default-member). When a data analysis expression (DAX) query is executed, the default member specified in the model is applied automatically.
 
-This article describes how Power BI behaves under various circumstances when working with multidimensional models, based on where the default member is found.
+This article describes how Power BI behaves under various circumstances when working with multidimensional semantic models, based on where the default member is found.
 
 ## Work with filter cards
 
@@ -95,7 +95,7 @@ Power BI doesn't clear a default member for a specified column, if:
 
 ## Related content
 
-This article described the behavior of Power BI when working with default members in multidimensional models. You might also be interested in the following articles:
+This article described the behavior of Power BI when working with default members in multidimensional semantic models. You might also be interested in the following articles:
 
 * [Show items with no data in Power BI](../create-reports/desktop-show-items-no-data.md)
 * [Data sources in Power BI Desktop](desktop-data-sources.md)

powerbi-docs/connect-data/desktop-directquery-sap-bw.md

@@ -7,7 +7,7 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: how-to
-ms.date: 01/24/2023
+ms.date: 02/26/2025
 LocalizationGroup: Connect to data
 ---
 # Connect to SAP Business Warehouse by using DirectQuery in Power BI
@@ -52,11 +52,11 @@ The following table lists all SAP BW features that aren't fully supported, or be
 | --- | --- |
 | **Local calculations** | Local calculations defined in a BEx Query change the numbers as displayed through tools like BEx Analyzer. However, they aren't reflected in the numbers returned from SAP, through the public MDX interface. |
 | | **As such, the numbers seen in a Power BI visual don't necessarily match those for a corresponding visual in an SAP tool.** |
-| | For example, when connecting to a query cube from a BEx query that sets the aggregation to be *Cumulated*, or running sum, Power BI would get back the base numbers, ignoring that setting. An analyst could certainly then apply a running sum calculation locally in Power BI, but would need to exercise caution in how the numbers are interpreted if this action isn't done. |
+| | For example, when connecting to a query cube from a BEx query that sets the aggregation to be *Cumulated*, or running sum, Power BI would get back the base numbers, ignoring that setting. An analyst could then apply a running sum calculation locally in Power BI, but would need to exercise caution in how the numbers are interpreted if this action isn't done. |
 | **Aggregations** | In some cases, particularly when dealing with multiple currencies, the aggregate numbers returned by the SAP public interface don't match the results shown by SAP tools. |
 | | **As such, the numbers seen in a Power BI visual don't necessarily match those for a corresponding visual in an SAP tool.** |
 | | For example, totals over different currencies would show as "*" in BEx Analyzer, but the total would get returned by the SAP public interface, without any information that such an aggregate number is meaningless. Thus the number aggregating, say, $, EUR, and AUD, would get displayed by Power BI. |
-| **Currency formatting** | Any currency formatting, for example, *$2,300* or *4000 AUD*, isn't reflected in Power BI. |
+| **Currency formatting** | Any currency formatting, for example, *$2,300* or *4,000 AUD*, isn't reflected in Power BI. |
 | **Units of measure** | Units of measure, for example, *230 KG*, aren't reflected in Power BI. |
 | **Key versus text** (short, medium, long) | For an SAP BW characteristic like `CostCenter`, the field list shows a single column *Cost Center*.  Using that column displays the default text. By showing hidden fields, it's also possible to see the unique name column that returns the unique name assigned by SAP BW, and is the basis of uniqueness. |
 | | The key and other text fields aren't available. |

powerbi-docs/connect-data/desktop-directquery-troubleshoot.md

@@ -7,12 +7,12 @@ ms.reviewer: asaxton
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: troubleshooting
-ms.date: 02/21/2023
+ms.date: 02/26/2025
 ---
 
 # Troubleshoot DirectQuery models in Power BI Desktop
 
-This article helps you diagnose performance issues with Power BI DirectQuery data models you develop in Power BI Desktop or the Power BI service. The article also describes how to get detailed information to help you optimize reports.
+This article helps you diagnose performance issues with Power BI DirectQuery semantic models you develop in Power BI Desktop or the Power BI service. The article also describes how to get detailed information to help you optimize reports.
 
 You should start any diagnosis of performance issues in Power BI Desktop, rather than in the Power BI service or Power BI Report Server. Performance issues often depend on the performance level of the underlying data source. You can more easily identify and diagnose these issues in the isolated Power BI Desktop environment, without involving components like an on-premises gateway.
 
@@ -95,7 +95,7 @@ Keep individual sessions reasonably small, perhaps 10 seconds of actions, not hu
 
 ## Query and subquery format
 
-The general format of Power BI Desktop queries is to use subqueries for each model table the queries reference. The Power Query Editor query defines the subselect queries. For example, assume you have the following [TPC-DS](https://www.tpc.org/tpcds/default5.asp) tables in a SQL Server relational database:
+The general format of Power BI Desktop queries is to use subqueries for each semantic model table the queries reference. The Power Query Editor query defines the subselect queries. For example, assume you have the following [TPC-DS](https://www.tpc.org/tpcds/default5.asp) tables in a SQL Server relational database:
 
 ![Screenshot of a Power BI Desktop model view diagram that shows the related Item, Web_Sales, Customer and Date-dim TPC-DS tables.](media/desktop-directquery-troubleshoot/desktop-directquery-troubleshoot-model-view-diagram.png)
 

powerbi-docs/connect-data/desktop-enhanced-dataset-metadata.md

@@ -7,7 +7,7 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: conceptual
-ms.date: 11/10/2023
+ms.date: 02/26/2025
 LocalizationGroup: Connect to data
 ---
 # Using enhanced semantic model metadata
@@ -23,15 +23,15 @@ The enhanced semantic model metadata feature is strategic and foundational. Futu
 
 ## Upgrade
 
-Your reports are automatically upgraded to the enhanced metadata format when you open them in the latest version of Power BI Desktop. If the report was saved with unapplied query changes, or there was an error during the auto-upgrade, there's a warning on the report canvas that you still need to upgrade. Selecting **Upgrade report** applies any pending changes and upgrades the data model to the new format.
+Your reports are automatically upgraded to the enhanced metadata format when you open them in the latest version of Power BI Desktop. If the report was saved with unapplied query changes, or there was an error during the auto-upgrade, there's a warning on the report canvas that you still need to upgrade. Selecting **Upgrade report** applies any pending changes and upgrades the semantic model to the new format.
 
 ## Exclude table from report refresh
 
 Once a data model has been upgraded to the enhanced metadata format, some metadata that was previously only used in Power BI Desktop is now respected in the Power BI service as well. This metadata includes the **Include in Report Refresh** option. For upgraded models, if the **Include in Report Refresh** option is unselected in the Power Query Editor, then that table isn't refreshed when the report or semantic model is refreshed in Power BI Desktop or the Power BI service. Reports already published in the Power BI service that aren't yet upgraded to the new enhanced metadata formal need to be upgraded in Power BI Desktop before this new behavior takes effect.
 
 ## Considerations and limitations
 
-Before enhanced metadata support, for SQL Server, Oracle, Teradata, and legacy HANA connections, Power BI Desktop added a native query to the data model. This query is used by the Power BI service data models. With enhanced metadata support, the Power BI service data model regenerates the native query at runtime. It doesn't use the query that Power BI Desktop created. In most cases, this retrieval resolves itself correctly, but some transformations don't work without reading underlying data. You might see some errors in reports that previously worked. For example, an error might say:
+Before enhanced metadata support, for SQL Server, Oracle, Teradata, and legacy HANA connections, Power BI Desktop added a native query to the semantic model. This query is used by the Power BI service semantic models. With enhanced metadata support, the Power BI service semantic model regenerates the native query at runtime. It doesn't use the query that Power BI Desktop created. In most cases, this retrieval resolves itself correctly, but some transformations don't work without reading underlying data. You might see some errors in reports that previously worked. For example, an error might say:
 
 - Unable to convert an M query in table 'Dimension City' into a native source query. Try again later or contact support. If you contact support, provide these details.
 

powerbi-docs/connect-data/desktop-enter-data-directly-into-desktop.md

@@ -8,7 +8,7 @@ ms.custom: ''
 ms.service: powerbi
 ms.subservice: pbi-data-sources
 ms.topic: how-to
-ms.date: 01/05/2023
+ms.date: 02/26/2025
 LocalizationGroup: Connect to data
 ---
 # Enter data directly into Power BI Desktop
@@ -35,7 +35,7 @@ You're now ready to use the data in Power BI Desktop. You can create visuals, re
 
 > [!NOTE]
 > To update, add, or delete data within items created by **Enter Data**, changes must be made in Power BI Desktop, and published.
-> Data updates cannot be made directly from the Power BI service.
+> Data updates can't be made directly from the Power BI service.
 
 ## Related content