Live publish

Author: buck1ey

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/getoutput.md",
+      "redirect_url": "getoutputs",
+      "redirect_document_id": false
+    },
     {
       "source_path": "powerapps-docs/cards/glossary.md",
       "redirect_url": "overview",

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
 

powerapps-docs/developer/data-platform/media/set-pluginpackage-read-access.png

@@ -294,8 +294,8 @@
         href: clientapi/reference/controls/getObject.md
       - name: getOptions
         href: clientapi/reference/controls/getOptions.md
-      - name: getOutput
-        href: clientapi/reference/controls/getoutput.md
+      - name: getOutputs
+        href: clientapi/reference/controls/getoutputs.md
       - name: getParent
         href: clientapi/reference/controls/getParent.md
       - name: getSearchQuery

powerapps-docs/developer/model-driven-apps/TOC.yml

@@ -51,7 +51,7 @@ These are the methods available for a Standard control.
 <ul>
 <li><a href="controls/getLabel.md" data-raw-source="[getLabel](controls/getLabel.md)">getLabel</a></li>
 <li><a href="controls/getName.md" data-raw-source="[getName](controls/getName.md)">getName</a></li>
-<li><a href="controls/getoutput.md" data-raw-source="[getOutput](controls/getName.md)">getOutput</a></li>
+<li><a href="controls/getoutputs.md" data-raw-source="[getOutputs](controls/getoutputs.md)">getOutputs</a></li>
 <li><a href="controls/getParent.md" data-raw-source="[getParent](controls/getParent.md)">getParent</a></li>
 <li><a href="controls/getVisible.md" data-raw-source="[getVisible](controls/getVisible.md)">getVisible</a></li>
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/controls.md

@@ -1,9 +1,9 @@
 ---
-title: control.getOutput (Client API reference)
-description: Includes description and supported parameters for the control.getOutput method.
+title: control.getOutputs (Client API reference)
+description: Includes description and supported parameters for the control.getOutputs method.
 ms.author: noazarur
 author: noazarur-microsoft
-ms.date: 08/17/2022
+ms.date: 09/20/2022
 ms.reviewer: jdaly
 ms.topic: reference
 applies_to: "Dynamics 365 (online)"
@@ -15,7 +15,7 @@ search.app:
 contributors:
   - JimDaly
 ---
-# control.getOutput (Client API reference)
+# control.getOutputs (Client API reference)
 
 Returns a dictionary of the output properties of the control.
 
@@ -25,7 +25,7 @@ Standard controls.
 
 ## Syntax
 
-`formContext.getControl(arg).getOutput();`
+`formContext.getControl(arg).getOutputs();`
 
 ## Return Value