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/dependent-assembly-plugins.md
+1-6Lines changed: 1 addition & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,12 @@
1
1
---
2
2
title: "Dependent Assembly plug-ins (preview) (Microsoft Dataverse) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
3
description: "Learn how to include additional assemblies that your plug-in assembly can depend on."# 115-145 characters including spaces. This abstract displays in the search result.
4
-
ms.date: 12/01/2022
4
+
ms.date: 01/05/2023
5
5
ms.reviewer: jdaly
6
6
ms.topic: article
7
7
author: divkamath # GitHub ID
8
8
ms.subservice: dataverse-developer
9
9
ms.author: dikamath # MSFT alias of Microsoft employees only
10
-
manager: sunilg # MSFT alias of manager or PM counterpart
11
10
search.audienceType:
12
11
- developer
13
12
search.app:
@@ -307,10 +306,6 @@ More information:
307
306
308
307
The following are known issues that should be resolved before dependent assemblies for plug-ins becomes generally available.
309
308
310
-
### Asynchronous plug-in steps do not work
311
-
312
-
If you use dependent assemblies for a plug-in registered for an asynchronous step an error with the message `Expected non-empty Guid.` will occur.
313
-
314
309
### Plug-in profiler
315
310
316
311
You cannot use Plug-in Profiler to debug plug-ins that are part of a plug-in package. More information: [Use Plug-in profiler](debug-plug-in.md#use-plug-in-profiler)
0 commit comments