Merge pull request #12647 from MicrosoftDocs/main

11/19/2024 PM Publish

.openpublishing.redirection.json

@@ -20,6 +20,11 @@
             "redirect_url": "/power-bi/visuals/power-bi-visualization-new-card",
             "redirect_document_id": true
         },
+        {
+            "source_path": "powerbi-docs/create-reports/copilot-pane-summarize-report-data.md",
+            "redirect_url": "/power-bi/create-reports/copilot-pane-summarize-content",
+            "redirect_document_id": true
+        },
         {
             "source_path": "powerbi-docs/connect-data/service-aml-integrate.md",
             "redirect_url": "/fabric/data-science/use-ai-samples",

powerbi-docs/collaborate-share/end-user-subscribe.md

@@ -8,7 +8,7 @@ featuredvideoid:
 ms.service: powerbi
 ms.subservice: pbi-explore
 ms.topic: how-to
-ms.date: 11/05/2024
+ms.date: 11/08/2024
 ms.custom: retail analysis sample
 LocalizationGroup: Common tasks
 ---
@@ -233,6 +233,7 @@ From here, you see a list of all your subscriptions across all workspaces. Power
 
 ### Workspace administrators
 Users who are assigned the [Admin role](../collaborate-share/service-roles-new-workspaces.md) in a workspace can view all subscriptions created for Power BI reports, dashboards, or paginated reports in that workspace, regardless of owner. Information on the subscription name, owner, report or dashboard name, and content type is provided. Workspace admins can also edit and take over subscriptions owned by others.
+If you have subscribed to reports through Power BI Organizational App, you have to install the organizational app to see the subscriptions. 
 
 > [!NOTE]
 > Subscriptions created for reports and dashboards in an app or those hosted in your **My workspace** can only be managed by the user who created the subscriptions. 

powerbi-docs/enterprise/TOC.yml

@@ -147,7 +147,12 @@
     - name: Synchronize scale-out replicas   
       href: service-premium-scale-out-sync-replica.md  
     - name: Compare semantic model scale-out replicas      
-      href: service-premium-scale-out-app.md                     
+      href: service-premium-scale-out-app.md   
+  - name: Workspace monitoring
+    expanded: false
+    items:
+    - name: Semantic model operations
+      href: semantic-model-operations.md                       
   - name: Automation tools
     expanded: false
     items:

powerbi-docs/enterprise/semantic-model-operations.md

@@ -0,0 +1,63 @@
+---
+title: Semantic model operation logs
+description: View a set of GraphQL operation logs that you can query in your Fabric workspace monitoring database.
+author: KesemSharabi
+ms.author: kesharab
+ms.service: powerbi
+ms.topic: reference
+ms.date: 11/07/2024
+
+---
+
+# Semantic model operations
+
+Semantic model operation logs are part of the workspace monitoring logs and are registered in the Eventhouse KQL database, which is part of the Real-Time Intelligence solution. You can use these logs to monitor the usage and performance of your workspace.
+
+## Semantic model operation logs
+
+Analysis services engine process events such as the start of a batch or transaction. For example, execute query and process partition. Typically used to monitor the performance, health and usage of Power BI's data engine. Contains information from the entire tenant.
+
+Use semantic model logs to:
+
+* Identify periods of high or unusual Analysis Services engine activity by capacity, workspace, report, or user.
+* Analyze query performance and trends, including external DirectQuery operations.
+* Analyze semantic model refresh duration, overlaps, and processing steps.
+* Analyze custom operations sent using the Premium XMLA endpoint.
+
+This table lists the semantic model logs. For more information on the events and drill-down into the `ExecutionMetrics` event, see [Events and schema](/power-bi/transform-model/log-analytics/desktop-log-analytics-configure#events-and-schema).
+
+| ColumnName | ColumnType | Description |
+|--|--|--|
+| ApplicationContext | dynamic | Property bag of unique identifiers providing details about the application executing the request. For example, report ID. |
+| ApplicationName | string | Contains the name of the client application that created the connection to the server. This column is populated with the values passed by the application rather than the displayed name of the program. |
+| CallerIpAddress | string | Called IP address |
+| CapacityId | string | Unique identifier of the capacity hosting the artifact being operated on. |
+| Category | string | Category of the events, like Audit/Security/Request. |
+| CorrelationId | string | The ID for correlated events. Can be used to identify correlated events between multiple tables. |
+| CpuTimeMs | long | Amount of CPU time (in milliseconds) used by the event. |
+| CustomerTenantId | string | Fabric tenant identifier |
+| DatasetMode | string | The mode of the semantic model. Import, DirectQuery, or Composite. |
+| DurationMs | long | Amount of time (in milliseconds) taken by the   operation. |
+| EventText | string | Contains verbose information associated with the   operation, for example, DAX Query. |
+| ExecutingUser | string | The user running the operation. |
+| Identity | dynamic | Information about user and claims. |
+| ItemId | string | Unique identifier of the resource logging the data. |
+| ItemKind | string | Type of artifact logging the operation, for example, semantic model. |
+| ItemName | string | The name of the Power BI artifact logging this   operation. |
+| Level | string | Contains the severity level of the operation being logged. Success, informational, warning, or error. |
+| OperationDetailName | string | More details about the operation |
+| OperationId | string | Unique identifier of the operation or the request. Same as `XmlaRequestId` |
+| OperationName | string | The operation associated with the log record. |
+| ProgressCounter | long | Progress counter |
+| Region | string | Contains the Fabric region |
+| ReplicaId | string | Replica identifier that will let you identify the replica when Query Scale Out (QSO) is enabled. Read-write replica always has ReplicaId='AAA' and read-only replicas have ReplicaId starting 'AAB' onwards. For non-QSO enabled semantic models the ReplicaId is always 'AAA' |
+| Status | string | Status of the operation. |
+| StatusCode | int | Status code of the operation. It covers success and failure. |
+| Timestamp | datetime | The timestamp (UTC) of when the log was generated. |
+| User | string | The user associated with the running operation. Used when an end-user identity must be impersonated on the server. |
+| WorkspaceId | string | Unique identifier of the workspace containing the item being operated on. |
+| WorkspaceMonitoringTableName | string | Name of the table the events are available in Fabric Workspace monitoring |
+| WorkspaceName | string | Name of the Fabric workspace containing the item. |
+| XmlaObjectPath | string | Object path. A comma-separated list of parents, starting with the object's parent. |
+| XmlaProperties | string | Properties of the XMLA request |
+| XmlaSessionId | string | Analysis services session identifier |

powerbi-docs/transform-model/desktop-visual-calculations-overview.md

@@ -169,11 +169,6 @@ RUNNINGSUM([Sales Amount], LOWESTPARENT)
 RUNNINGSUM([Sales Amount], 2)
 ```
 
-```dax
-RUNNINGSUM([Sales Amount], [Quarter])
-```
-
-
 Finally, this visual calculation does **not** reset, and continues adding the *Sales Amount* value for each month to the previous values, without restarting.
 
 ```dax
@@ -199,7 +194,7 @@ You can think of the ORDERBY and PARTITIONBY pair as pinning field references do
 
 You can use many of the existing DAX functions in visual calculations. Since visual calculations work within the confines of the visual matrix, functions that rely on model relationships such as [USERELATIONSHIP](/dax/userelationship-function-dax), [RELATED](/dax/related-function-dax) or [RELATEDTABLE](/dax/relatedtable-function-dax) aren't available.
 
-Visual calculations also introduce a set of functions specific to visual calculations. Many of these functions are easier to use shortcuts to DAX window functions. 
+Visual calculations also introduce a set of functions specific to visual calculations. Many of these functions are easier to use shortcuts to DAX window functions.
 
 > [!NOTE]
 > Only use the visual calculations specific functions mentioned in the table below. Other visual calculations specific functions are for internal use only at this time and should not be used. Refer to the table below for any updates of the functions available for use as this preview progresses.
@@ -220,7 +215,7 @@ Visual calculations also introduce a set of functions specific to visual calcula
 | [RUNNINGSUM](/dax/runningsum-function-dax) | Adds a running sum on an axis. | RunningSumSales = RUNNINGSUM([Sales Amount]) | [WINDOW](/dax/window-function-dax) |
 
 ## Formatting visual calculations
- 
+
 You can format a visual calculation using data types and formatting options. You can also set a [custom visual level format string](../create-reports/desktop-custom-format-strings.md). Use the **Data format** options in the General section of the formatting pane for your visual to set the format:
 
 :::image type="content" source="media/desktop-visual-calculations-overview/desktop-visual-calculations-format-strings.png" alt-text="Screenshot of the visual calculations edit mode showing a visual calculation that returns a percentage formatted as a percentage.":::
@@ -267,12 +262,12 @@ Visual calculations are currently in preview, and during preview, you should be
 
 ## Next steps
 
-The following articles may be useful when learning and using visual calculations: 
+The following articles may be useful when learning and using visual calculations:
 
+* [Create visual calculations in Power BI Desktop (Training module)](/training/modules/power-bi-visual-calculations/)
 * [Using calculations options in Power BI Desktop](desktop-calculations-options.md)
 * [Create measures for data analysis in Power BI Desktop](desktop-measures.md)
 * [WINDOW DAX function](/dax/window-function-dax)
 * [OFFSET DAX function](/dax/offset-function-dax)
 * [INDEX DAX function](/dax/index-function-dax)
 * [ORDERBY DAX function](/dax/orderby-function-dax)
-