Merge branch 'master' into canvas-portals-2022837

Author: tapanm-MSFT

powerapps-docs/developer/common-data-service/api-limits.md

@@ -333,7 +333,7 @@ If your application is currently using the low-level <xref:Microsoft.Xrm.Sdk.Cli
 
 More information:
 
-- [Build Windows client applications using the XRM tools](/xrm-tooling/build-windows-client-applications-xrm-tools).
+- [Build Windows client applications using the XRM tools](xrm-tooling/build-windows-client-applications-xrm-tools.md).
 - [Deprecation of Office365 authentication type and OrganizationServiceProxy class for connecting to Common Data Service](/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-common-data-service)
 
 ### Use Task Parallel Library with CrmServiceClient

powerapps-docs/developer/common-data-service/xrm-tooling/use-connection-strings-xrm-tooling-connect.md

@@ -70,6 +70,7 @@ CrmServiceClient svc = new CrmServiceClient(ConnectionString);
 |`StoreName` or `CertificateStoreName`|Specifies the store name where the certificate identified by thumbprint can be found. When set, Thumbprint is required.|
 |`Thumbprint` or `CertThumbprint`| Specifies the thumbprint of the certificate to be utilized during an S2S connection. When set, AppID is required and UserID and Password values are ignored.|
 |`SkipDiscovery`|Specifies whether to call instance discovery to determine the connection uri for a given instance. As of NuGet release Microsoft.CrmSdk.XrmTooling.CoreAssembly Version 9.0.2.7, default = true. Older versions default to false. <br/> Note: If set to true, it is important that the user provide the correct and accurate URI for the target instance.|
+|`Integrated Security`|Specifies to use current windows credentials to attempt to create a token for the instances. As of NuGet release Microsoft.CrmSdk.XrmTooling.CoreAssembly Version 9.1.0.21|
 
 > [!NOTE]
 > <b>When using the `OAuth` AuthType\AuthenticationType</b><br/>

powerapps-docs/developer/component-framework/media/code-components.gif

@@ -50,10 +50,11 @@ Dashboards are one of the different types of forms in model-driven apps. You can
 ## Dashboard components and FormXML elements  
  The dashboard components are displayed in model-driven apps based on the values specified in the FormXML. The following image shows an example of a dashboard. Each dashboard can include multiple tabs. Tabs are a vertical stack separating the body of the dashboard, and can be expanded or collapsed. A tab can contain multiple sections. Sections enable for grouping and layout of dashboard components. 
 
- <!-- TODO: image not found ![Dashboard components layout](../media/crm-v5s-dashboards-components.png "Dashboard components layout")   -->
+ ![Dashboard components layout](media/crm-v5s-dashboards-components.png "Dashboard components layout") 
 
 <a name="SupportedFormXMLElements"></a>   
 ## FormXML elements supported for dashboards  
+
  Although dashboards are a type of forms, not all FormXML elements and attributes are supported by dashboards. The following table provides information about the FormXML elements, child elements, and attributes supported by dashboards.
 
  For sample FormXML for different types of dashboards, see [Sample Dashboards](sample-dashboards.md).  

powerapps-docs/developer/model-driven-apps/understand-dashboards-dashboard-components-formxml.md

@@ -47,10 +47,6 @@
       items:
       - name: Basic navigation
         href: ../user/navigation.md
-      - name: Use grid filters
-        href: ../user/grid-filters.md
-      - name: Create personal views with advanced grid filters
-        href: ../user/grid-filters-advanced.md
       - name: View your profile
         href: ../user/view-your-user-profile.md
       - name: Find your admin or support person
@@ -82,11 +78,23 @@
       - name: Add a connection role
         href: ../user/add-connection-role.md
       - name: Deactivate accounts or contacts
-        href: ../user/deactivate-activate-account-contact.md
+        href: ../user/deactivate-activate-account-contact.md   
+    - name: Work with grid filters
+      items:
+      - name: Use grid filters
+        href: ../user/grid-filters.md
+      - name: Create personal views with advanced grid filters
+        href: ../user/grid-filters-advanced.md      
+    - name: Charts and dashboards
+      items:
       - name: Track your progress with dashboards and charts
         href: ../user/track-your-progress-with-dashboard-and-charts.md
+      - name: View charts on a page or in a record
+        href: ../user/chart_on_form.md
+      - name: Use interactive dashboards to filter data
+        href: ../user/interactive-dashboards.md
       - name: Add Power BI dashboards
-        href: ../user/add-powerbi-dashboards.md
+        href: ../user/add-powerbi-dashboards.md      
     - name: Work with email
       items:
       - name: View and create email through the activities grid
@@ -1707,6 +1715,8 @@
           href: ./common-data-service/view-component-dependencies.md   
         - name: Use environment variables
           href: ./common-data-service/EnvironmentVariables.md
+        - name: Create a connection reference
+          href: ./common-data-service/create-connection-reference.md  
         - name: Translate customized component text
           items: 
           - name: Overview

powerapps-docs/maker/TOC.yml

@@ -1,5 +1,5 @@
 ---
-title: "Preview: Use environment variables in solutions | MicrosoftDocs"
+title: "Use environment variables in solutions | MicrosoftDocs"
 description: "Use environment variables to migrate application configuration data in solutions."
 Keywords: environment variables, variables, model-driven app, configuration data
 author: caburk
@@ -15,15 +15,14 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Preview: Environment variables overview 
-
-[!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# Environment variables overview 
 
 Apps and flows often require different configuration settings across environments. Environment variables as configurable input parameters allow management of data separately compared to hard-coding values within your customization or using additional tools. Because they're solution components, performance is much better than importing configuration data as record data.
 
 Benefits of using environment variables:
 - No need to manually edit configurable values in a production environment.
 - Configure one or more variables in one place and reference like a parameter across multiple solution components.
+- Enter different values while importing solutions to other environments. 
 - Update values without a code change.
 - Granular level security managed by [Common Data Service](https://docs.microsoft.com/powerapps/maker/common-data-service/data-platform-intro).
 - Unlimited number of variables (max solution size is 29 MB).
@@ -32,9 +31,6 @@ Benefits of using environment variables:
 - Support for localization.
 - Can be used to control feature flags and other application settings.
 
-> [!IMPORTANT]
-> - This is a preview feature.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
 
 ## How do they work?
 Environment variables can be created and managed through the modern solution interface or by [using code](https://docs.microsoft.com/powerapps/developer/common-data-service/work-with-data-cds). A separate JSON file is created within your solution package for the values, which can also be managed in source control and modified in a build pipeline. Export to and import from Excel is supported. After creating environment variables, you can use them as inputs within plug-ins, flows, and other components. 
@@ -55,7 +51,15 @@ Environment variables can be created and managed through the modern solution int
       > ![New environment variable](media/new-environment-variable.png)
 
       >[!NOTE]
-      > A value can't exist without a definition. The interface only allows creation of one value per definition. 
+      > A value can't exist without a definition. The interface only allows creation of one value per definition.
+
+## Enter new values while importing solutions
+
+The modern solution import interface includes the ability to enter values for environment variables. This sets the value property on the `environmentvariablevalue` entity.
+
+You will not be prompted if the environment variables already have either a default value or value present; whether values are part of your solution or are already present in Common Data Service.
+   >[!NOTE]
+   > You may remove the value from your solution before exporting the solution. This ensures the existing value will remain in your development environment, but not get exported in the solution. This approach allows a new value to be set while importing the solution into other environments.  
 
 ## Notifications
 A notification is displayed when the environment variables do not have any values. This is a reminder to set the values so that components dependent on variables do not fail. It also allows partners to ship variables without values and the customer is prompted to input the values.

powerapps-docs/maker/common-data-service/EnvironmentVariables.md

@@ -0,0 +1,49 @@
+---
+title: "Connection references in solutions | MicrosoftDocs"
+description: "Create a connection reference in Power Apps"
+ms.custom: ""
+ms.date: 08/27/2020
+ms.reviewer: "matp"
+ms.service: powerapps
+ms.topic: "article"
+author: "caburk"
+caps.latest.revision: 57
+ms.author: "caburk"
+manager: "kvivek"
+search.audienceType: 
+  - maker
+search.app: 
+  - PowerApps
+  - D365CE
+---
+# Create a connection reference from a solution
+
+[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+
+A connection  is a proxy or a wrapper around an API that allows the underlying service to talk to Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. It provides a way for users to connect their accounts and use a set of pre-built actions and triggers to build their apps and workflows.
+
+A connection reference is a solution component that contains information about a connector. Both canvas app and operations within a Power Automate flow bind to a connection reference. You can import your connection reference into a target environment with no further configuration needed after the import completes. To change a specific connection associated with a canvas app or flow, you edit the connection reference component within the solution.
+
+> [!NOTE]
+>
+> - Canvas apps and flows handle connections differently. Flows use connection references for all connectors, whereas canvas apps only use them for implicitly shared connections, such as SQL Server. More information: [Security and types of authentication](../canvas-apps/connections-list.md#security-and-types-of-authentication)
+> - A connection reference is automatically created when you create new connections from the flow and canvas app designers.
+
+1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), and on the left pane select **Solutions**. 
+2. Create a new or open an existing solution.
+3. On the command bar select **New**, and then in the list of components select Connection Reference. 
+4. On the **New Connection Reference** pane, enter the following information. Required fields a denoted with an asterisk (*).
+   - **Display name**: Enter a friendly name to help differentiate this connection reference from others.
+   - **Description**: Enter text that describes the connection.
+   - **Connector**: Choose from the following options:
+       - Select an existing connector from the list.
+       - Select **New** to create a new connection to use for this connection reference. Once your finished creating the connection, select **Refresh** to select your new connection from the list.  
+5. Select **Create**.
+
+## Limits
+
+During the preview, the same connection reference can be used a maximum of 16 times in flows.
+
+### See also
+
+[Connectors](/connectors/connectors)

powerapps-docs/maker/common-data-service/create-connection-reference.md

@@ -2,7 +2,7 @@
 title: "Import solutions | MicrosoftDocs"
 description: "Learn how to import a solution in Power Apps"
 ms.custom: ""
-ms.date: 08/06/2020
+ms.date: 08/27/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
@@ -17,12 +17,14 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Import solutions 
+# Import solutions
 
-You can manually import solutions using the steps in this article. You must import only those solutions that you've obtained from a trusted source. Customizations might include code that can send data to external sources.   
+[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+
+You can manually import solutions using the steps in this article. You must import only those solutions that you've obtained from a trusted source.
 
 > [!NOTE]
-> - To import a solution that includes a plug-in assembly, the **Create** privilege on the **Plug-In Assembly** entity is required. By default, the System Administrator security role has this privilege, but the System Customizer security role doesn’t. 
+> - The create privilege is required to import a component. Although, the System Customer security role has create privilege on most components that are commonly imported, by default it doesn't have create privilege on the **Plug-In Assembly** entity. The System Administrator security role has this privilege.
 > - When you import a managed solution, all component changes will be brought into the environment in a published state. However, when you import an unmanaged solution, the changes are imported in a draft state so you must publish them to make them active. 
 > - To implement healthy application lifecycle management (ALM) in your organization, consider using a source control system to store and collaborate on your solutions, and automate the solution import process. More information: [ALM basics](/power-platform/alm/basics-alm) in the Power Platform ALM guide.
 
@@ -32,29 +34,38 @@ When you import an **unmanaged** solution:
 
 To import a solution:
 
-1.  Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select **Solutions** from the left navigation.  
+1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select **Solutions** from the left navigation.  
 
-2.  On the command bar, select **Import**.  
+1. On the command bar, select **Import**.  
 
     > [!div class="mx-imgBorder"]  
     > ![Import solution](media/solution-import.png "Import solution") 
   
-3.  On the **Select Solution Package** page, select **Browse** to locate the compressed (.zip or .cab) file that contains the solution you want to import. 
-  
-4.  Select **Next**.  
-  
-5.  Information about the solution is displayed. Select **Import**.  
-  
-6. You may need to wait a few moments while the import completes. View the results and then select **Close**.  
-  
- If you have imported any changes that require publishing, you must publish customizations before they are available. 
+1. On the **Import a solution** page, select **Browse** to locate the compressed (.zip or .cab) file that contains the solution you want to import.
+
+1. Select **Next**.  
 
- If the import isn’t successful, you will see a report showing any errors or warnings that were captured. Select **Download Log File** to capture details about what caused the import to fail. The most common cause for an import to fail is that the solution did not contain some required components.  
+1. Information about the solution is displayed. By default, in the **Advanced settings** section, if SDK messages and flows exist in the solution, they will be imported. Clear the **Enable SDK messages and flows included in the solution** option if you want them to import in an inactive state. 
+
+1. If your solution contains [connection references](create-connection-reference.md), you’ll be prompted to select the connections you want. If a connection does not already exist, create a new one. Click **Next**.
+
+1. If your solution contains [environment variables](EnvironmentVariables.md), you will be prompted to enter values. You will not see this screen if value(s) are already present in your solution or the target environment. 
+
+1. Select **Import**.
+
+Your solution imports in the background and may take a few moments.  
 
- When you download the log file, you will find an XML file that you can open using Office Excel to view the contents.  
+ If you have imported any changes that require publishing, you must publish customizations before they are available.
 
+ If the import isn’t successful, you will see a notification on the solutions page showing any errors or warnings that were captured. Select **Download Log File** to capture details about what caused the import to fail. The most common cause for an import to fail is that the solution did not contain some required components.  
+
+When you download the log file, you will find an XML file that you can open using Office Excel to view the contents.
+
 > [!NOTE]
-> You can’t edit an active routing rule set. Therefore, if you’re importing a solution that includes an active routing rule set into an environment where the rule already exists with the same ID, the import will fail. More information: [Create rules to automatically route cases](https://docs.microsoft.com/dynamics365/customer-engagement/customer-service/create-rules-automatically-route-cases)  
+> You can view the details of all solution operations including solution import with the [solution history](solution-history.md) feature. To view these operations, select **See history** on the solutions page.
+  
+<!-- 
+> You can’t edit an active routing rule set. Therefore, if you’re importing a solution that includes an active routing rule set into an environment where the rule already exists with the same ID, the import will fail. More information: [Create rules to automatically route cases](https://docs.microsoft.com/dynamics365/customer-engagement/customer-service/create-rules-automatically-route-cases)  -->
 
 ## Troubleshooting solution import