Skip to content

Commit 3bb17f8

Browse files
authored
Update dependent-assembly-plugins.md
Removed known issue 'Asynchronous plug-in steps do not work'
1 parent 9aa03c9 commit 3bb17f8

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

powerapps-docs/developer/data-platform/dependent-assembly-plugins.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
---
22
title: "Dependent Assembly plug-ins (preview) (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
33
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
55
ms.reviewer: jdaly
66
ms.topic: article
77
author: divkamath # GitHub ID
88
ms.subservice: dataverse-developer
99
ms.author: dikamath # MSFT alias of Microsoft employees only
10-
manager: sunilg # MSFT alias of manager or PM counterpart
1110
search.audienceType:
1211
- developer
1312
search.app:
@@ -307,10 +306,6 @@ More information:
307306

308307
The following are known issues that should be resolved before dependent assemblies for plug-ins becomes generally available.
309308

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-
314309
### Plug-in profiler
315310

316311
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

Comments
 (0)