Merge pull request #7023 from MicrosoftDocs/jdaly-main-dependent-assembly-known-issues

Added Known issues

Author: JimDaly

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

@@ -1,7 +1,7 @@
 ---
 title: "Dependent Assembly plug-ins (preview) (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 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.
-ms.date: 08/23/2022
+ms.date: 09/20/2022
 ms.reviewer: jdaly
 ms.topic: article
 author: divka78 # GitHub ID
@@ -345,7 +345,28 @@ More information:
 
 ## Known issues
 
-You cannot use Plug-in Profiler to debug plug-ins that are part of a plug-in package.
+The following are known issues that should be resolved before dependent assemblies for plug-ins becomes generally available.
+
+### Plug-in profiler
+
+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)
+
+### Solution containing plugin package cannot include any steps using the plug-in
+
+When you prepare a solution that contains a plugin package, do not include any plug-in step registrations that use an assembly included in the plug-in package.
+
+The export of the solution will succeed, but you will not be able to import the solution. To test plug-ins that use a dependent assembly in a different environment, you must manually register the steps.
+
+One exception for this are Custom APIs which use an assembly for the main operation stage. There is no separate step registration for this specific step. More information: [Create and use Custom APIs](custom-api.md)
+
+### Users must be granted read access to plug-in package
+
+Any users without the System Administrator security role must be granted read access to the [PluginPackage table](reference/entities/pluginpackage.md).
+
+You can manually edit this for each security role following the steps here: [Edit a security role](/power-platform/admin/create-edit-security-role#edit-a-security-role). **Plugin Package** is located in the **Custom Entities** tab.
+
+:::image type="content" source="media/set-pluginpackage-read-access.png" alt-text="Setting plugin package read access.":::
+
 
 ### See also