Merge branch 'master' into portals-copyedit-4-1844159

Author: tapanm-MSFT

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/maker/model-driven-apps/customize-power-bi-content-packs.md",
+      "redirect_url": "../common-data-service/use-powerbi-with-cds",
+      "redirect_document_id": "false"
+    }, 
     {
       "source_path": "powerapps-docs/maker/common-data-service/how-managed-solutions-merged.md",
       "redirect_url": "https://docs.microsoft.com/power-platform/alm/how-managed-solutions-merged",

README.md

@@ -4,10 +4,10 @@ This is the GitHub repository for the technical product documentation for **Powe
 
 ## How to contribute
 
-Thanks for your interest in contributing to [Docs.microsoft.com](https://docs.microsoft.com/), home of technical content for Microsoft products and services.
+Thanks for your interest in contributing to [docs.microsoft.com](https://docs.microsoft.com/), home of technical content for Microsoft products and services.
 
 To learn how to make contributions to the content in this repository, start with our [Docs contributor guide](https://docs.microsoft.com/contribute). If you are a Microsoft employee, please visit the [internal version](https://aka.ms/docsguidescontribute) of this guide.
 
 ## Code of conduct
 
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.

powerapps-docs/developer/common-data-service/cds-sql-query.md

@@ -2,7 +2,7 @@
 title: "Use SQL to query data (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to query Common Data Service entity data using SQL." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 05/05/2020
+ms.date: 05/26/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -25,7 +25,7 @@ A SQL data connection is available on the Common Data Service endpoint. The SQL
 > [!IMPORTANT]
 > - This is a preview feature, and isn't available in all regions.
 > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
-> - Instructions to enable the feature can be found here: [View entity data in Power BI Desktop](/powerapps/maker/common-data-service/view-entity-data-power-bi).
+> - Instructions to enable the feature can be found here: [View entity data in Power BI Desktop](/powerapps/maker/common-data-service/view-entity-data-power-bi), and [Manage feature settings](/power-platform/admin/settings-features) (see TDS endpoint setting).
 
 ## Applications support
 

powerapps-docs/developer/common-data-service/file-attributes.md

@@ -39,6 +39,9 @@ When a file attribute is added to an entity some additional attributes are creat
 ### MaxSizeInKB attribute
 
  This value represents the maximum size (in kilobytes) of the file data that the attribute can contain. Set this value to the smallest useable data size appropriate for your particular application. See the <xref:Microsoft.Xrm.Sdk.Metadata.FileAttributeMetadata.MaxSizeInKB> property for the allowable size limit and the default value.
+ 
+ > [!NOTE]
+ > MaxSizeInKB is set when the File attribute is added to an entity. This cannot be changed after it is set.
   
 <a name="BKMK_RetrievingFiles"></a>
 

powerapps-docs/developer/common-data-service/image-attributes.md

@@ -72,6 +72,9 @@ In addition to image attributes, custom entities support zero or more file attri
 ### MaxSizeInKB attribute
 
  This value represents the maximum size (in kilobytes) of the image data that the attribute can contain. Set this value to the smallest useable data size appropriate for your particular application. See the <xref:Microsoft.Xrm.Sdk.Metadata.ImageAttributeMetadata.MaxSizeInKB> property for the allowable size limit and the default value.
+ 
+ > [!NOTE]
+ > MaxSizeInKB is set when the Image attribute is added to an entity. This cannot be changed after it is set.
 
 ### CanStoreFullImage attribute
 

powerapps-docs/developer/common-data-service/powerapps-cli.md

@@ -49,7 +49,7 @@ This table lists some common commands used in the CLI:
 |Command|Description|Examples|
 |------|-----------|--------|
 |**pcf**|Commands for working with [Power Apps component framework](/powerapps/developer/component-framework/overview). It has the following parameters: <br/> - **init**: Initializes the code component project. It has the following parameters <br/> - *namespace*: Namespace of the code component. <br/> - *name*: Name of the code component. <br/> - *template*: Field or dataset <br/> - **push**: Pushes the code component to the Common Data Service instance with all the latest changes. It has the following parameter: <br/> - *publisher-prefix*: Publisher prefix of the organization.<br/> - **Version**: Updates the component manifest file with the specified patch version. It has the following parameters: <br/> - *patchversion*: Patch version of the code component. `patchversion` will only take value of the third part of the version tuple: `Major.Minor.Patch`.<br/> - *path*: Absolute or relative path of the component manifest file.<br/> - *allmanifests*: Updates the patch version for all the component manifest files.| `pac pcf init --namespace <specify your namespace here> --name <Name of the code component> --template <component type>` <br/> <br/> `pac pcf push --publisher-prefix <your publisher prefix>` <br/><br/> `pac pcf version --patchversion <number> --path <Absolute or relative path to component manifest file --allmanifests`|
-|**solution**|Commands for working with [Common Data Service solution projects](/powerapps/maker/common-data-service/solutions-overview). It has the following parameters: <br/> - **init**: Initializes the solution project. It has the following parameters:<br/>  - *publisher-name*: Publisher name of the organization. <br/>  - *publisher-prefix*: Publisher prefix of the organization. <br/> - **add-reference**: Sets the reference path to the component project folder by passing the `path` parameter.<br/> - **clone**: Creates a solution project based up on the existing solution project by passing the following parameters `name`, `version`, and `include`|`pac solution init --publisher-name <enter your publisher name> --publisher-prefix <enter your publisher prefix>` <br/><br/> `pac solution add-reference --path <path to your Power Apps component framework project>`<br/><br/> `pac solution clone –name<name of the solution to be exported> --version <version of your solution> --include <settings that should be included>`|
+|**solution**|Commands for working with [Common Data Service solution projects](/powerapps/maker/common-data-service/solutions-overview). It has the following parameters: <br/> - **init**: Initializes the solution project. It has the following parameters:<br/>  - *publisher-name*: Publisher name of the organization. <br/>  - *publisher-prefix*: Publisher prefix of the organization. <br/> - **add-reference**: Sets the reference path to the component project folder by passing the `path` parameter.<br/> - **clone**: Creates a solution project based up on the existing solution project by passing the following parameters:<br/> -*name*: The name of the solution to be exported.<br/> -*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.<br/> -**Export**: Exports a Common Data Service solution project from the current organization. It has the following parameters:<br/> -*path*: Place where the exported solution zip file will be saved.<br/> - *name*: Name oft he solution that needs to be exported.<br/> - *managed*: Defines whether the solution should be exported as a managed solution or not.<br/>-*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.|`pac solution init --publisher-name <enter your publisher name> --publisher-prefix <enter your publisher prefix>` <br/><br/> `pac solution add-reference --path <path to your Power Apps component framework project>`<br/><br/> `pac solution clone –name<name of the solution to be exported> --version <version of your solution> --include <settings that should be included>`|
 |**auth**|Commands to [authenticate to Common Data Service](/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment). It has the following parameters: <br/> - **create**: Creates the authentication profile for your organization by passing the `url` parameter. Pass the organization url for the `url` parameter. <br/> - **list**: Provides the list of authentication profiles. <br/> - **select**: Provides a way to switch between previously created authentication profiles by passing the `index` parameter.<br/>**delete**: Deletes the authentication profile created by passing  the `index` parameter.|`pac auth create --url <your Common Data Service org’s url>` <br/> <br/> `pac auth list` <br/><br/> `Pac auth select --index <index of the active profile>`|
 |**telemetry**|Manages the telemetry settings. It has the following parameters: <br/>- *enable*: Enables the telemetry option.<br/> - *disable*: Disables the telemetry option.<br/> - *status*: Returns whether the telemetry is enabled or disabled.|`pac telemetry enable` <br/><br/> `pac telemetry disable`|
 |**org**|Command to work with Common Data Service.|`pac org who`|

powerapps-docs/developer/component-framework/import-custom-controls.md

@@ -22,7 +22,7 @@ To create and import a solution file:
 2. Create a new solutions project using the following command. The solution project is used for bundling the code component into a solution zip file that is used for importing into Common Data Service.
 
    ```CLI
-   pac solution init --publisher-name <enter your publisher name> --publisher-prefix <enter your publisher prefix>
+   pac solution init --publisher-name developer --publisher-prefix dev
    ```
 
    > [!NOTE]
@@ -31,7 +31,7 @@ To create and import a solution file:
 3. Once the new solution project is created, refer the **Solutions** folder to the ___location where the created sample component is located. You can add the reference using the command shown below. This reference informs the solution project about which code components should be added during the build. You can add references to multiple components in a single solution project.
 
    ```CLI   
-    pac solution add-reference --path <path to your Power Apps component framework project>
+    pac solution add-reference --path c:\downloads\mysamplecomponent
    ```
 
 3. To generate a zip file from the solution project, go into your solution project directory and build the project using the following command. This command uses *MSBuild* to build the solution project by pulling down the *NuGet* dependencies as part of the restore. Use the `/restore` only for the first time when the solution project is built. For every build after that, you can run the command `msbuild`.
@@ -53,12 +53,12 @@ To create and import a solution file:
 
 You can deploy the code components directly from the Power Apps CLI by connecting to the Common Data Service environment and then pushing the updated components.
 
-Use the following steps to create the authentication profile, connect to Common Data Service, and push the updated components. 
+Follow the steps below to create the authentication profile, connect to Common Data Service, and push the updated components. 
 
 1. Create your authentication profile using the command: 
 
     ```CLI
-    pac auth create --url <https://xyz.crm.dynamics.com> 
+    pac auth create --url https://xyz.crm.dynamics.com 
     ```
  
 2. If you have previously created an authentication profile, you can view all the existing profiles using the command: 
@@ -84,7 +84,11 @@ Use the following steps to create the authentication profile, connect to Common
 
 ## Deploying code components 
 
-After you have successfully created an authentication profile, you can start pushing the code components to the Common Data Service instance with all the latest changes. The `push` capability speeds up the inner-developer cycle development because it bypasses the code component versioning requirements and does not require that you build your solution (cdsproj) to import the code component. To use the `push` capability, do the following:
+After you have successfully created an authentication profile, you can start pushing the code components to the Common Data Service instance with all the latest changes. 
+
+The `push` capability speeds up the inner-developer cycle development because it bypasses the code component versioning requirements and does not require that you build your solution (cdsproj) to import the code component. 
+
+To use the `push` capability, do the following:
 
 1. Ensure that you have a valid authentication profile created.
 2. Navigate to the root directory where the code component project is created.
@@ -105,9 +109,12 @@ To create a solution project based on an existing solution in Common Data Servic
 2. Run the command 
 
    ```CLI
-   pac solution clone –name(-n) <name of the solution to be exported> --version(-v) <version of your solution> --include(-i) <settings that should be included>
+   pac solution clone –-name(-n) <name of the solution to be exported> --targetversion(-v) <version of your solution> --include(-i) <settings that should be included>
    ```
 
+   > [!NOTE]
+   > Settings Values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales.
+
 More information: [Settings options](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.exportsolutionrequest?view=dynamics-general-ce-9)
 
 ## Create a plug-in project and add a reference to it in your solution 
@@ -116,30 +123,30 @@ More information: [Settings options](https://docs.microsoft.com/dotnet/api/micro
 > The plugin command is in public preview and 
 Power Apps CLI now supports creating a plug-in project and packaging it in a solution by adding a reference to the plug-in project. The `pac plugin init` command creates the template files (csproj, Plugin.cs & ServiceHelper.cs) in the directory. To do so: 
 
-1.    Ensure that you have a valid authentication profile created.
-2.    Navigate to the root directory where you want the project to be created.
-3.    Run the command 
+1. Ensure that you have a valid authentication profile created.
+2. Navigate to the root directory where you want the project to be created.
+3. Run the command 
 
-     ```CLI
-     pac auth create –url <https://xyz.crm.dynamics.com>
-     ```
-4.    Run the command to create the plug-in project
+   ```CLI
+   pac auth create –url <https://xyz.crm.dynamics.com>
+   ```
+4. Run the command to create the plug-in project
 
-    ```CLI
-    pac plugin init
-    ```
+   ```CLI
+   pac plugin init
+   ```
 
-5.    Add a reference to your solution project  using the following command so that the plug-in project gets built when the solution is built.
+5. Add a reference to your solution project  using the following command so that the plug-in project gets built when the solution is built.
 
-    ```CLI
-    pac solution add-reference –path <path to your plugin project>
-    ```
+   ```CLI
+   pac solution add-reference –path <path to your plugin project>
+   ```
 
-6.    Run the command to build the solution and the referenced plug-in.
+6. Run the command to build the solution and the referenced plug-in.
 
-    ```CLI
-    msbuild
-    ```
+   ```CLI
+   msbuild
+   ```
 
 ## Remove components from a solution
 

powerapps-docs/includes/pn-powerapps.md

@@ -1 +1 @@
-PowerApps
+Power Apps

powerapps-docs/index.md

@@ -406,7 +406,7 @@ ms.custom:
                                     <h3 style="font-size: 1.15rem">Environment and security</h3>
                                     <hr/>
                                     <p><a class="barLink" style="font-size: 0.95rem" href="/power-platform/admin/environments-overview">Environments overview</a></p>
-                                    <p><a class="barLink" style="font-size: 0.95rem" href="/power-platform/admin/trial-environments">Trial environements</a></p>
+                                    <p><a class="barLink" style="font-size: 0.95rem" href="/power-platform/admin/trial-environments">Trial environments</a></p>
                                     <p><a class="barLink" style="font-size: 0.95rem" href="/power-platform/admin/database-security">Environment security</a></p>
                                  </div>
                               </div>