freshness

Author: mberdugo

powerbi-docs/developer/embedded/datasets-permissions.md

@@ -9,7 +9,7 @@ tags: ''
 ms.service: powerbi
 ms.subservice: powerbi-developer
 ms.topic: reference
-ms.date: 11/09/2023
+ms.date: 11/09/2024
 ---
 
 # Semantic model REST API permissions
@@ -28,7 +28,7 @@ Power BI has two sets of permissions:
 
 Workspace permissions, also known as folder permissions or [roles](../../collaborate-share/service-roles-new-workspaces.md), are the highest level of permissions in Power BI. These permissions override permissions that are given to a specific item in the workspace folder.
 
-The table below lists the four types of folder roles. It shows each role's level, and the code string returned by the Power BI REST APIs. Admin is the highest workspace permission level, and viewer is the lowest. Every permission level includes the capabilities of the permissions below it. You can review the capabilities of each permission in [Workspace roles](../../collaborate-share/service-roles-new-workspaces.md#workspace-roles).
+The following table lists the four types of folder roles. It shows each role's level, and the code string returned by the Power BI REST APIs. Admin is the highest workspace permission level, and viewer is the lowest. Every permission level includes the capabilities of the permissions below it. You can review the capabilities of each permission in [Workspace roles](../../collaborate-share/service-roles-new-workspaces.md#workspace-roles).
 
 |Folder Role |Level |Derived permissions for semantic models created in the workspace |
 |------------|------|--------------------------|
@@ -38,7 +38,7 @@ The table below lists the four types of folder roles. It shows each role's level
 |Viewer      |1     |`Read`                    |
 
 >[!NOTE]
->The *write* permission is applied to Power BI semantic models created by *admin*, *member* and *contributor* users in a workspace they own. The write permission can be granted or deleted using workspace permissions only. It cannot directly be granted to, or deleted from, a Power BI item.
+>The *write* permission is applied to Power BI semantic models created by *admin*, *member*, and *contributor* users in a workspace they own. The write permission can be granted or deleted using workspace permissions only. It can't directly be granted to, or deleted from, a Power BI item.
 
 #### Get and add workspace permissions with APIs
 
@@ -56,14 +56,14 @@ Power BI items, such as reports, semantic models, and dashboards have their own
 
 ## Semantic model permissions and REST APIs
 
-Semantic model permissions are part of the [item permissions](#item-permissions). The table below lists the Power BI semantic model permissions and their representation in the [Power BI REST APIs](/rest/api/power-bi/).
+Semantic model permissions are part of the [item permissions](#item-permissions). The following table lists the Power BI semantic model permissions and their representation in the [Power BI REST APIs](/rest/api/power-bi/).
 
 >[!TIP]
 >Although the API permissions are identical to the Power BI service permissions, [`build`](#build-permissions-and-rest-apis) permissions are referred to as *explore* permissions in the APIs.
 
 |Permission             |Read     |Explore  |Reshare  |
 |-----------------------|---------|---------|---------|
-|Description            |Allows the user to read the content of the semantic model|Equivalent to [build permissions](#build-permissions-and-rest-apis) |Allows the user to share the content of the semantic model with other users who will get read, reshare, or explore permissions for it |
+|Description            |Allows the user to read the content of the semantic model|Equivalent to [build permissions](#build-permissions-and-rest-apis) |Allows the user to share the content of the semantic model with other users who get read, reshare, or explore permissions for it |
 |**ReadReshareExplore** | :::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::     |:::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::       |:::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::        |
 |**ReadReshare**        |:::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::        |:::image type="icon" source="../../includes/media/no-icon.svg" border="false":::      |:::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::        |
 |**ReadExplore**        |:::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::        |:::image type="icon" source="../../includes/media/yes-icon.svg" border="false":::       |:::image type="icon" source="../../includes/media/no-icon.svg" border="false":::       |
@@ -74,7 +74,7 @@ Semantic model permissions are part of the [item permissions](#item-permissions)
 
 ### Build permissions and REST APIs
 
-In the [Power BI REST APIs](/rest/api/power-bi/), the `build` permission is returned as *explore*. For example, a string with the *read*, *reshare* and *build* permissions, will look like this: `ReadReshareExplore`.
+In the [Power BI REST APIs](/rest/api/power-bi/), the `build` permission is returned as *explore*. For example, a string with the *read*, *reshare* and *build* permissions, looks like this: `ReadReshareExplore`.
 
 When you give a user `build` permission, they can build new content on your semantic model. Examples of content they can build are reports, dashboards, pinned tiles from Q&A, paginated reports, and Insights Discovery.
 
@@ -88,7 +88,7 @@ Users also need `build` permissions to work with data outside Power BI:
 
 ### Row-level security
 
-For a semantic model that uses row-level security (RLS), any permissions *higher* than `build` will enable the user to view all the data in the semantic model. `Build`, and permissions lower than `build`, will only give the semantic model user access to the data they're allowed to see as configured in your RLS settings.
+For a semantic model that uses row-level security (RLS), any permissions *higher* than `build` enables the user to view all the data in the semantic model. `Build`, and permissions lower than `build`, only give the semantic model user access to the data they're allowed to see as configured in your RLS settings.
 
 ### Get and update semantic model permissions with APIs
 
@@ -107,9 +107,7 @@ For a semantic model that uses row-level security (RLS), any permissions *higher
   * [Datasets - Get Dataset Users](/rest/api/power-bi/datasets/get-dataset-users)
   * [Datasets - Get Dataset Users In Group](/rest/api/power-bi/datasets/get-dataset-users-in-group)
 
-## Considerations and limitations
-
-Each of the above APIs comes with certain limitations regarding who can use them and how. To see the limitations of each API, select the link for that API.
+Each of these APIs comes with certain limitations regarding who can use them and how. To see the limitations of each API, select the link for that API.
 
 ## Related content
 

powerbi-docs/developer/visuals/fetch-more-data.md

@@ -178,7 +178,7 @@ btn_click(){
 As a response to calling the `this.host.fetchMoreData` method, Power BI calls the `update` method of the visual with a new segment of data.
 
 > [!NOTE]
-> Although the data in the different updates of the data views are mostly exclusive, there is some overlap between consecutive data views.
+> Although the data in the different updates of the data views are mostly exclusive, there's some overlap between consecutive data views.
 >
 > For table and categorical data mapping, the first `N` data view rows can be expected to contain data copied from the previous data view.
 >

powerbi-docs/developer/visuals/permissions-api.md

@@ -7,7 +7,7 @@ ms.reviewer:
 ms.service: powerbi
 ms.subservice: powerbi-custom-visuals
 ms.topic: reference
-ms.date: 06/28/2022
+ms.date: 06/28/2024
 ---
 
 # Check permissions API

powerbi-docs/developer/visuals/total-subtotal-api.md

@@ -7,7 +7,7 @@ ms.reviewer: tebercov
 ms.service: powerbi
 ms.subservice: powerbi-custom-visuals
 ms.topic: how-to
-ms.date: 11/22/2023
+ms.date: 11/22/2024
 #customer intent: As a Power BI visual developer, I want to learn how to use the Total and Subtotal API to request aggregated subtotal data from the Power BI host.
 ---
 
@@ -31,7 +31,7 @@ The API offers the following customization for each data-view type (currently, o
 * `columnSubtotals`: (boolean) Indicates if the *subtotal* data should be requested for all fields in the columns field well.
 * `columnSubtotalsPerLevel`: (boolean) Indicates if the *subtotal* data can be toggled for individual fields in the columns field well.
 * `levelSubtotalEnabled`: (boolean) Indicates if the subtotals are requested for the row or column. Unlike all the other properties, this property is applied to individual rows or columns.
-* `rowSubtotalsType`: ("Top" or "Bottom") Indicates if the row with the *total* data should be retrieved before (`top`) or after (`bottom`) the rest of the data. If this property is set to `bottom`, the total can only be displayed after all the data has been fetched. The default is `bottom`.
+* `rowSubtotalsType`: ("Top" or "Bottom") Indicates if the row with the *total* data should be retrieved before (`top`) or after (`bottom`) the rest of the data. If this property is set to `bottom`, the total can only be displayed after all the data is fetched. The default is `bottom`.
 
 Each of these switches is assigned a value based on the related properties in the property pane and the defaults.
 

powerbi-docs/developer/visuals/utils-formatting-model.md

@@ -8,7 +8,7 @@ ms.reviewer: tebercov
 ms.service: powerbi
 ms.subservice: powerbi-custom-visuals
 ms.topic: reference
-ms.date: 10/23/2023
+ms.date: 10/23/2024
 ms.custom: engagement-fy23
 ---
 
@@ -347,7 +347,7 @@ new formattingSettings.ColorPicker({
 
 ## Reset settings to default
 
-Formatting model utils will enable you to [reset settings to default](./format-pane-example.md#reset-settings-to-default) by automatically adding all the formatting properties descriptors to the formatting card list of features to revet to default descriptors `revertToDefaultDescriptors`.
+Formatting model utils enable you to [reset settings to default](./format-pane-example.md#reset-settings-to-default) by automatically adding all the formatting properties descriptors to the formatting card list of features to revet to default descriptors `revertToDefaultDescriptors`.
 
 You can enable resetting formatting settings from: