Skip to content

Commit 741af14

Browse files
authored
Merge branch 'main' into users/cotaylor/add-cards-alm-docs
2 parents e1eb32a + d386bfc commit 741af14

File tree

255 files changed

+2544
-2069
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

255 files changed

+2544
-2069
lines changed

powerapps-docs/developer/data-platform/aad-group-team.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ An AAD group team can be created in Dataverse by making an API call (programmati
4141

4242
Citizen developers wanting to programmatically create a Microsoft Dataverse AAD group team can do so by providing the object ID of an existing AAD group as shown in the following command.
4343

44-
**Request**
44+
**Request:**
4545

4646
```http
4747
POST [Organization URI]/api/data/v9.0/teams
@@ -63,7 +63,7 @@ Where:
6363

6464
An administrator can assign a security role to an AAD group team after the AAD group is created in AAD. The AAD group team is created into Dataverse automatically if it doesn't exist in Dataverse.
6565

66-
**Request**
66+
**Request:**
6767

6868
```http
6969
POST [Organization URI]/api/data/v9.0/teams(azureactivedirectoryobjectid=<group team ID>,membershiptype=0)/teamroles_association/$ref
@@ -78,7 +78,7 @@ Accept: application/json
7878

7979
An administrator can assign a security role to an AAD group user. The user is added into Dataverse automatically if the user doesn't exist in Dataverse and the role is assigned directly to the user.
8080

81-
**Request**
81+
**Request:**
8282

8383
```http
8484
POST [Organization URI]/api/data/v9.0/systemusers(azureactivedirectoryobjectid=<user object ID>)/systemuserroles_association/$ref
@@ -94,7 +94,7 @@ An administrator can assign a record to an AAD group. The AAD group team is cre
9494

9595
The example below shows the syntax for assigning an account record.
9696

97-
**Request**
97+
**Request:**
9898

9999
```http
100100
PATCH [Organization URI]/api/data/v9.0/accounts(<account ID>)
@@ -111,7 +111,7 @@ An administrator can assign a record to an AAD group member. The AAD group memb
111111

112112
The example below shows the syntax for assigning an account record.
113113

114-
**Request**
114+
**Request:**
115115

116116
```http
117117
PATCH [Organization URI]/api/data/v9.0/accounts(<account ID>)
@@ -127,7 +127,7 @@ Accept: application/json
127127
128128
The example below shows the syntax for sharing an account record.
129129
130-
**Request**
130+
**Request:**
131131
132132
```http
133133
POST [Organization URI]/api/data/v9.0/GrantAccess
@@ -153,7 +153,7 @@ Accept: application/json
153153
154154
The example below shows the syntax for sharing an account record.
155155
156-
**Request**
156+
**Request:**
157157
158158
```http
159159
POST [Organization URI]/api/data/v9.0/GrantAccess
@@ -179,7 +179,7 @@ You can retrieve a system user table row using an Azure user object identifier (
179179

180180
The example below shows the syntax for retrieving a user row.
181181

182-
**Request**
182+
**Request:**
183183

184184
```http
185185
GET [Organization URI]/api/data/v9.0/SystemUser(azureactivedirectoryobjectid=<user object ID>)
@@ -189,13 +189,13 @@ GET [Organization URI]/api/data/v9.0/SystemUser(azureactivedirectoryobjectid=<us
189189

190190
Members of an AAD group can query all the security roles that are directly and indirectly assigned to them using the following command.
191191

192-
**Request**
192+
**Request:**
193193

194194
```http
195195
GET [Organization URI]/api/data/v9.0/RetrieveAadUserRoles(DirectoryObjectId=<user object ID)?$select=_parentrootroleid_value,name
196196
```
197197

198-
**Response**
198+
**Response:**
199199

200200
```json
201201
{
@@ -217,13 +217,13 @@ GET [Organization URI]/api/data/v9.0/RetrieveAadUserRoles(DirectoryObjectId=<use
217217

218218
Members of an AAD group can check their security privileges without being a user of Dataverse using the following command.
219219

220-
**Request**
220+
**Request:**
221221

222222
```http
223223
GET [Organization URI]/api/data/v9.0/RetrieveAadUserPrivileges(DirectoryObjectId=<user object ID>)
224224
```
225225

226-
**Response**
226+
**Response:**
227227

228228
```json
229229
{

powerapps-docs/developer/data-platform/analyze-performance.md

Lines changed: 8 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Analyze plug-in performance (Microsoft Dataverse) | Microsoft Docs"
33
description: "Learn how to find and analyze performance data on plug-ins execution."
4-
ms.date: 02/24/2023
4+
ms.date: 08/15/2023
55
ms.reviewer: "pehecke"
66
ms.topic: "article"
77
author: "divkamath"
@@ -10,7 +10,7 @@ ms.author: "pehecke"
1010
search.audienceType:
1111
- developer
1212
contributors:
13-
- PHecke
13+
- phecke
1414
---
1515
# Analyze plug-in performance
1616

@@ -33,22 +33,12 @@ More information: [Best practices and guidance regarding plug-in and workflow de
3333

3434
## Monitor performance
3535

36-
Run-time information about plug-ins and custom workflow extensions is captured and stored in the [PluginTypeStatistic Table](reference/entities/plugintypestatistic.md). These records are populated within 30 minutes to one hour after the custom code executes. This table provides the following data points:
37-
38-
|**Column**|**Description**|
39-
|--|--|
40-
|AverageExecuteTimeInMilliseconds|The average execution time (in milliseconds) for the plug-in type. |
41-
|CrashContributionPercent|The plug-in type percentage contribution to crashes. |
42-
|CrashCount|Number of times the plug-in type has crashed. |
43-
|CrashPercent|Percentage of crashes for the plug-in type. |
44-
|ExecuteCount|Number of times the plug-in type has been executed. |
45-
|FailureCount |Number of times the plug-in type has failed. |
46-
|FailurePercent|Percentage of failures for the plug-in type. |
47-
|PluginTypeIdName|Unique identifier of the user who last modified the plug-in type statistic. |
48-
|TerminateCpuContributionPercent |The plug-in type percentage contribution to Worker process termination due to excessive CPU usage. |
49-
|TerminateHandlesContributionPercent |The plug-in type percentage contribution to Worker process termination due to excessive handle usage. |
50-
|TerminateMemoryContributionPercent|The plug-in type percentage contribution to Worker process termination due to excessive memory usage. |
51-
|TerminateOtherContributionPercent|The plug-in type percentage contribution to Worker process termination due to unknown reasons. |
36+
> [!IMPORTANT]
37+
> This feature is no longer operational or supported. Do not use.
38+
>
39+
> This section will be removed in a future article update.
40+
41+
Run-time information about plug-ins and custom workflow extensions is captured and stored in the [PluginTypeStatistic Table](reference/entities/plugintypestatistic.md). These records are populated within 30 minutes to one hour after the custom code executes.
5242

5343
## Plug-in performance analytics
5444

0 commit comments

Comments
 (0)