Live publish

buck1ey · web-flow · commit 8d6c96a70a90 · 2022-02-16T11:00:01.000-08:00
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -6374,6 +6374,26 @@
       "source_path": "powerapps-docs/data-platform/best-practices/index.md",
       "redirect_url": "/powerapps/developer/data-platform/best-practices/",
       "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/component-framework/reference/linking/clear.md",
+      "redirect_url": "/powerapps/developer/component-framework/reference/linking",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/component-framework/reference/linking/includes/clear-description.md",
+      "redirect_url": "/powerapps/developer/component-framework/reference/linking",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/component-framework/reference/linking/includes/removeLinkedEntity-description.md",
+      "redirect_url": "/powerapps/developer/component-framework/reference/linking",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/component-framework/reference/linking/removeLinkedEntity.md",
+      "redirect_url": "/powerapps/developer/component-framework/reference/linking",
+      "redirect_document_id": "false"
     }
   ]
 }
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/includes/retrieveRecordCommand-description.md b/powerapps-docs/developer/component-framework/reference/dataset/includes/retrieveRecordCommand-description.md
@@ -19,3 +19,4 @@ applies_to:
 ---
 
 Retrieve record's associated commands.
+If there are multiple datasets in the manifest, retrieveRecordCommand returns the commands for the first dataset.
diff --git a/powerapps-docs/developer/component-framework/reference/linking.md b/powerapps-docs/developer/component-framework/reference/linking.md
@@ -26,9 +26,7 @@ Model-driven apps
 | Method                                              | Description                                                                                     |
 | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
 | [addLinkedEntity](linking/addLinkedEntity.md)       | [!INCLUDE [addlinkedentity-description](linking/includes/addlinkedentity-description.md)]       |
-| [clear](linking/clear.md)                           | [!INCLUDE [addlinkedentity-description](linking/includes/clear-description.md)]                 |
 | [getLinkedEntities](linking/getlinkedentities.md)   | [!INCLUDE [getlinkedentities-description](linking/includes/getlinkedentities-description.md)]   |
-| [removeLinkedEntity](linking/removeLinkedEntity.md) | [!INCLUDE [removeeinkedentity-description](linking/includes/removelinkedentity-description.md)] |
 
 ### Related topics
 
diff --git a/powerapps-docs/developer/component-framework/reference/linking/clear.md b/powerapps-docs/developer/component-framework/reference/linking/clear.md
diff --git a/powerapps-docs/developer/component-framework/reference/linking/includes/clear-description.md b/powerapps-docs/developer/component-framework/reference/linking/includes/clear-description.md
diff --git a/powerapps-docs/developer/component-framework/reference/linking/includes/removeLinkedEntity-description.md b/powerapps-docs/developer/component-framework/reference/linking/includes/removeLinkedEntity-description.md
diff --git a/powerapps-docs/developer/component-framework/reference/linking/removeLinkedEntity.md b/powerapps-docs/developer/component-framework/reference/linking/removeLinkedEntity.md
diff --git a/powerapps-docs/developer/component-framework/toc.yml b/powerapps-docs/developer/component-framework/toc.yml
@@ -1,5 +1,5 @@
 - name: Power Apps component framework
-  items: 
+  items:
   - name: Overview
     href: overview.md
   - name: What are code components
@@ -32,7 +32,7 @@
     href: code-components-best-practices.md
   - name: How-to guides
     items:
-    - name: Create and build a code component 
+    - name: Create and build a code component
       href: create-custom-controls-using-pcf.md
     - name: Package a code component
       href: import-custom-controls.md
@@ -55,7 +55,7 @@
   - name: FAQs
     href: faq.yml
   - name: Sample components
-    items: 
+    items:
     - name: How to use the sample components?
       href: use-sample-components.md
     - name: Angular Flip component
@@ -104,9 +104,9 @@
       href: sample-controls/webapi-control.md
   - name: Reference
     items:
-    - name: Power Apps component framework 
+    - name: Power Apps component framework
       href: reference/index.md
-      items: 
+      items:
       - name: Client
         href: reference/client.md
         items:
@@ -115,7 +115,7 @@
         - name: getFormFactor
           href: reference/client/getformfactor.md
         - name: isOffline
-          href: reference/client/isoffline.md      
+          href: reference/client/isoffline.md
       - name: Column
         href: reference/column.md
       - name: ConditionExpression
@@ -187,7 +187,7 @@
         items:
         - name: getColumnInfo
           href: reference/entityrecord/getcolumninfo.md
-        - name: getFormattedValue 
+        - name: getFormattedValue
           href: reference/entityrecord/getformattedvalue.md
         - name: getNamedReference
           href: reference/entityrecord/getnamedreference.md
@@ -261,14 +261,10 @@
       - name: Linking
         href: reference/linking.md
         items:
-        - name: clear
-          href: reference/linking/clear.md
         - name: addLinkedEntity
           href: reference/linking/addlinkedentity.md
         - name: getLinkedEntity
           href: reference/linking/getlinkedentities.md
-        - name: removeLinkedEntity
-          href: reference/linking/removelinkedentity.md
       - name: Metadata
         href: reference/metadata.md
       - name: Mode
diff --git a/powerapps-docs/developer/data-platform/webapi/aad-group-team.md b/powerapps-docs/developer/data-platform/webapi/aad-group-team.md
@@ -2,7 +2,7 @@
 title: "Work with Azure Active Directory group teams (Dataverse)| Microsoft Docs"
 description: "Learn about working with an Azure Active Directory group team using the Web API."
 ms.custom: ""
-ms.date: 09/14/2021
+ms.date: 02/15/2022
 
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -174,6 +174,18 @@ Accept: application/json
 }
 ``` -->
 
+## Retrieve a user
+
+You can retrieve a user row using an Azure user object identifier (ID). If the user doesn’t exist in Dataverse, the user is added to Dataverse automatically.
+
+The example below shows the syntax for retrieving a user row.
+
+**Request**
+
+```http
+GET [Organization URI]/api/data/v9.0/SystemUser(azureactivedirectoryobjectid=<user object ID>)
+```
+
 ## Security roles and privileges
 
 Members of an AAD group can query all the security roles that are directly and indirectly assigned to them using the following command.
diff --git a/powerapps-docs/maker/data-platform/query-visualize-hierarchical-data.md b/powerapps-docs/maker/data-platform/query-visualize-hierarchical-data.md
@@ -75,7 +75,7 @@ For some tables, such as account and user, the visualizations are provided out-o
   
 <a name="BKMK_Visualizedata"></a>   
 ## Visualize hierarchical data  
- The system tables that have visualizations available out-of-the-box include `Account`, `Position`, `Product`, and `User`. In the grid view of these tables, you can see the icon depicting the hierarchy chart, to the left of the row name. The hierarchy icon isn’t present for all rows by default. The icon is shown for the rows that have a parent row, a child row, or both.  
+ The system tables that have visualizations available out-of-the-box include `Account`, `Business Unit`, `Position`, `Product`, and `User`. In the grid view of these tables, you can see the icon depicting the hierarchy chart, to the left of the row name. The hierarchy icon isn’t present for all rows by default. The icon is shown for the rows that have a parent row, a child row, or both.  
  
  > [!div class="mx-imgBorder"] 
  > ![Active accounts.](media/cust-hs-active-account.png "Active accounts")  
@@ -126,4 +126,4 @@ For some tables, such as account and user, the visualizations are provided out-o
  > ![Widget's tree and tiles views.](media/widget-tree-tiles.png "Widget's tree and tiles views")  
   
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/maker/data-platform/solutions-overview.md b/powerapps-docs/maker/data-platform/solutions-overview.md
@@ -116,33 +116,29 @@ Some components may require certain Dataverse privileges for users to run the co
 
 ### Flows
 
-To use or run a flow from a canvas app that is included in a solution, you must be assigned a Dataverse security role with the following minimum permissions:
-
-- Read privilege on the **Solution** table.
-- Read privilege on the **Process** table.
+To use or run a flow from a canvas app that is included in a solution, you must have permissions to that flow through someone sharing ownership or run permissions. When an app in a solution is shared with a set of users, the flows must also be explictly shared.
 
 More information: [Security roles and privileges](/power-platform/admin/security-roles-privileges)
 
 ## Known limitations
 
 The following limitations apply to the use of canvas apps, flows, and custom connectors in solutions. 
 
-- Canvas app instant flows must be created from an app already in a solution. Adding this type of flow from outside solutions is blocked.
+- Canvas app instant flows must be created from an app already in a solution since adding this type of flow from outside solutions is blocked. 
+   - Workaround for this limitation: Remove the trigger, replace with another trigger like recurrence, save the flow, add it into a solution, and then change the trigger as needed.
 -	Canvas apps won't display in the classic solution explorer. Use the modern experience. There are no plans for them to be added to classic solution explorer. 
 - Flows created from solutions will not be displayed in the "Team Flows" list. They must be accessed through a solution. 
 - The [Power Automate mobile app](/power-automate/mobile-manage-flows) does not currently support flows created in a solution. 
 - The Flow action menu in [Power Apps Mobile](/powerapps/mobile/run-powerapps-on-mobile) and [Dynamics 365 for phones and tablets](/dynamics365/mobile-app/overview) does not currently support flows created in a solution. 
-- You can’t add an instant flow into a solution when the following are true:
-   - The flow was created outside of a solution.
-   - The flow trigger is set to manual.
-- Flows triggered from Microsoft 365 applications such as Excel are not available in solutions.
-- Flows in solutions don't support delegated authentication. For example, access to a flow is not automatically granted based on having access to the SharePoint list the flow was created from.
+- Flows in solutions don't support delegated authentication. For example, access to a flow cannot be automatically granted based on having access to the SharePoint list the flow was created from.
 - Custom connectors created outside solutions cannot be added to solutions at this time.
 - Canvas apps shared with 'Everyone' that go through environment backup and environment restore operations aren't shared with 'Everyone' in the restored environment. Notice that, the canvas app can be shared with a security group and the app in the restored environment will be shared with that security group.  
-- Flows using [connectors](/connectors/connector-reference/) that are 'indexed' cannot be added into solutions. Indexing enables the quick retrieval of those flows to display in a menu or list. Indexed connectors include Power Automate instant (button) flows, Power Apps, Teams, SharePoint, Dynamics 365 Customer Voice, Microsoft Forms, legacy Dataverse connector, Dynamics 365, Excel Online, Microsoft Project, Azure IOT Central V2, and Project Online. To work around this behavior choose one of two options: 
-   - Create a new flow in a solution. 
-   - Change the flow to remove the indexed connector usage, add it into a solution, and then change it back.
-
+- Flows using [connectors](/connectors/connector-reference/) that are 'indexed' cannot be added into solutions. Indexing isn't supported for solution cloud flows yet. Indexing enables the quick retrieval of those flows to display in a menu or list. Indexed connectors include Power Automate instant (button) flows, Power Apps, Teams, SharePoint, Dynamics 365 Customer Voice, Microsoft Forms, legacy Dataverse connector, Dynamics 365, Excel Online, Microsoft Project, Azure IOT Central V2, and Project Online. 
+   - Workarounds for this limitation: 
+      - Edit the flow to remove the indexed connector triggers/actions, add it into a solution, and then change it back.
+      - Create a new flow in a solution. 
+- Flows triggered from Microsoft 365 applications such as Excel cannot see/show cloud flows in solutions since they use indexing.
+      
 For details about customizing the individual components in a solution, see the following topics:  
   
 -   For table, table relationships, column and message customizations, see [Metadata](create-edit-metadata.md).  
diff --git a/powerapps-docs/maker/data-platform/types-of-fields.md b/powerapps-docs/maker/data-platform/types-of-fields.md
@@ -70,7 +70,7 @@ There are some columns used by the system that you cannot add using the designer
 
 |Type|Description|
 |--|--|
-|**Big Integer** or **Time Stamp**|Used by the system to capture a version number manage updates to a table.|
+|**Time Stamp**| A Big Integer type used by the system to capture a version number for managing updates to a table.|
 |**Customer**|A lookup column that you can use to specify a customer, which can be an account or contact.<br />**Note**: This attribute can be added using solution explorer designer.|
 |**Owner**|A system lookup column that references the user or team that is assigned a user or team owned table row.|
 |**Status Reason**|A system column that has options that provide additional detail about the Status column. Each option is associated with one of the available Status options. You can add and edit the options. <br /><br /> You can also include custom state transitions to control which status options are available for certain tables. More information: [Define status reason transitions for custom tables](define-status-reason-transitions.md)|
@@ -132,6 +132,11 @@ Decimal numbers are stored in the database exactly as specified. Floating point
 Use decimals when you need to provide reports that require very accurate calculations, or if you typically use queries that look for values that are equal or not equal to another value.  
   
 Use floating point numbers when you store data that represents fractions or values that you will typically query comparing to another value using greater than or less than operators. In most cases, the difference between decimal and float isn’t noticeable. Unless you require the most accurate possible calculations, floating point numbers should work for you.  
+
+Big Integers (or BigInt) are large numbers with a max value of 9,223,372,036,854,775,807. It is used to store very large numbers that exceed the capabilities of Whole Number and Decimal.  Some uses for this include storage of time stamp values and as unique IDs, as well as numbers larger than 100 billion.
+  
+[NOTE!] BigInt is currently only available for use through API. This includes column creation, data creation and data management. Maker portal support for BigInt column creation will be available soon. The ability to view and use BigInt columns within apps is a future feature. 
+
   
 <a name="BKMK_UsingCurrencyFields"></a>
  
diff --git a/powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md b/powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md
@@ -682,7 +682,7 @@ The default RTE webresource is available with the display name RTEGlobalConfigur
  
     "showPreview": false,
  
-    "showPreviewHeaderWarning": false}
+    "showPreviewHeaderWarning": false
 }
 ``` 
 ## Find the current setting for a rich text editor configuration
diff --git a/powerapps-docs/teams/overview-data-platform.md b/powerapps-docs/teams/overview-data-platform.md
@@ -2,9 +2,7 @@
 title: Microsoft Dataverse for Teams overview | Microsoft Docs
 description: Provides the benefits of Dataverse for Teams.
 author: NHelgren
-
 ms.topic: overview
-
 ms.date: 09/22/2020
 ms.subservice: teams
 ms.author: nhelgren
@@ -34,7 +32,7 @@ Some of the benefits of Dataverse for Teams include:
 
 - Storage of 2 GB per team, and support for up to 1 million rows.
 
-- Support for up to 500 teams.
+- Support for 5 teams plus 1 additional team for every 20 licensed users.
 
 - The capability to be upgraded to Dataverse.
 
@@ -69,4 +67,4 @@ You can administer and manage Dataverse for Teams environment using the Power Pl
 [Dataverse for Teams FAQs](data-platform-faqs.md)
 
 
-[!INCLUDE[footer-include](../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../includes/footer-banner.md)]

Original file line number	Diff line number	Diff line change
`@@ -19,3 +19,4 @@ applies_to:`
`19`	`19`	`---`
`20`	`20`
`21`	`21`	`Retrieve record's associated commands.`
	`22`	`+If there are multiple datasets in the manifest, retrieveRecordCommand returns the commands for the first dataset.`