You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/aad-group-team.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ An AAD group team can be created in Dataverse by making an API call (programmati
41
41
42
42
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.
43
43
44
-
**Request**
44
+
**Request:**
45
45
46
46
```http
47
47
POST [Organization URI]/api/data/v9.0/teams
@@ -63,7 +63,7 @@ Where:
63
63
64
64
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.
65
65
66
-
**Request**
66
+
**Request:**
67
67
68
68
```http
69
69
POST [Organization URI]/api/data/v9.0/teams(azureactivedirectoryobjectid=<group team ID>,membershiptype=0)/teamroles_association/$ref
@@ -78,7 +78,7 @@ Accept: application/json
78
78
79
79
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.
80
80
81
-
**Request**
81
+
**Request:**
82
82
83
83
```http
84
84
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
94
94
95
95
The example below shows the syntax for assigning an account record.
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/analyze-performance.md
+8-18Lines changed: 8 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Analyze plug-in performance (Microsoft Dataverse) | Microsoft Docs"
3
3
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
5
5
ms.reviewer: "pehecke"
6
6
ms.topic: "article"
7
7
author: "divkamath"
@@ -10,7 +10,7 @@ ms.author: "pehecke"
10
10
search.audienceType:
11
11
- developer
12
12
contributors:
13
-
- PHecke
13
+
- phecke
14
14
---
15
15
# Analyze plug-in performance
16
16
@@ -33,22 +33,12 @@ More information: [Best practices and guidance regarding plug-in and workflow de
33
33
34
34
## Monitor performance
35
35
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.
0 commit comments