Merge branch 'master' into scm-customer-portal

Author: tapanm-MSFT

.openpublishing.publish.config.json

@@ -108,7 +108,11 @@
     "master": [
       "Publish",
       "PDF"
-    ]
+    ],
+   "alm-guide": [
+      "Publish",
+      "PDF"
+    ] 
   },
   "need_generate_pdf_url_template": true,
   "Targets": {

.openpublishing.redirection.json

@@ -1448,7 +1448,7 @@
     },
     {
       "source_path": "powerapps-docs/webinars-listing.md",
-      "redirect_url": "/powerapps/maker/canvas-apps/webinars-listing",
+      "redirect_url": "https://powerusers.microsoft.com/t5/Samples-Learning-and-Videos/ct-p/PA_Comm_Galleries",
       "redirect_document_id": true
     },
     {
@@ -1635,6 +1635,16 @@
       "source_path": "powerapps-docs/maker/common-data-service/view-download-developer-resources.md",
       "redirect_url": "https://docs.microsoft.com/powerapps/developer/common-data-service/view-download-developer-resources",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "powerapps-docs/developer/common-data-service/use-web-services.md",
+      "redirect_url": "https://docs.microsoft.com/powerapps/developer/common-data-service/work-with-data-cds",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "powerapps-docs/maker/maker/canvas-apps/webinars-listing.md",
+      "redirect_url": "https://powerusers.microsoft.com/t5/Samples-Learning-and-Videos/ct-p/PA_Comm_Galleries",
+      "redirect_document_id": true
     }
   ]
 }

powerapps-docs/developer/common-data-service/TOC.yml

@@ -387,7 +387,7 @@
       href: isv-app-management-tenantpage.md
     - name: AppSource checker
       href: isv-app-management-appsource-checker.md
-    - name: Connector certification portal
+    - name: Connector Certification 
       href: isv-app-management-certification.md
 - name: Create client applications
   href: connect-cds.md

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

@@ -2,7 +2,7 @@
 title: "File attributes (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about File attributes that store file data within the application, supporting attributes, retrieving data, and uploading file data." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/04/2019
+ms.date: 04/27/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -26,7 +26,9 @@ FileAttributeMetadata | <xref:Microsoft.Xrm.Sdk.Metadata.FileAttributeMetadata>
 For information about types of files that are not allowed, see [System Settings General tab](/power-platform/admin/system-settings-dialog-box-general-tab) under the **Set blocked file extensions for attachments** setting.
 
 > [!IMPORTANT]
-> Some restrictions do apply when using the File and enhanced Image data-types of the Common Data Service. If Customer Managed Keys (CMK) is enabled on the tenant, then File, Image, and IoT data-types are not available to the tenant's organizations. Solutions that contain excluded data-types will not install. Customers must opt-out of CMK in order to make use of these data-types.
+> Some restrictions do apply when using the File and enhanced Image data-types of the Common Data Service. If Customer Managed Keys (CMK) is enabled on the tenant, then File, Image, and IoT data-types are not available to the tenant's organizations. Solutions that contain excluded data-types will not install. Customers must opt-out of CMK in order to make use of these data-types.<p/>
+> File attributes are supported in <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy.SdkClientVersion> 9.0.45.329 or greater and Web API version 9.1 or greater.
+
 
 <!--File data is not passed to plug-ins for performance reasons. You must retrieve the file data in plug-in code using an explicit retrieve call. -->
 

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

@@ -2,7 +2,7 @@
 title: "Image attributes (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about image attributes that store image data, supporting attributes, retrieving image data, and Uploading image data." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 02/11/2020
+ms.date: 04/27/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -19,7 +19,7 @@ search.app:
 
 Certain system entities and all custom entities support images. Those entities that do support images can contain both a thumbnail and a full-size primary image. The thumbnail image can be seen in the web application when viewing the entity's form data. There can be multiple image attributes in an entity instance but there can be only one primary image. However, you can change the primary image from one image to another by setting [IsPrimaryImage](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.metadata.imageattributemetadata.isprimaryimage?view=dynamics-general-ce-9#Microsoft_Xrm_Sdk_Metadata_ImageAttributeMetadata_IsPrimaryImage) for that attribute to `true`. Each full-sized image attribute is limited to 30 MB in size. The <xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata.SchemaName> of the entity image attribute is `EntityImage`. More information: [Entity images](/dynamics365/customer-engagement/developer/introduction-entities#entity-images).
 
-Thumbail images and image metadata are stored in Common Data Service, which includes the information needed to retrieve the full image. Full images are stored in file storage on the Azure blob to reduce data storage consumption.
+Thumbnail images and image metadata are stored in Common Data Service, which includes the information needed to retrieve the full image. Full images are stored in file storage on the Azure blob to reduce data storage consumption.
 
 Web API (REST) | .NET API (SOAP) 
 ------- | -------
@@ -28,6 +28,9 @@ IsPrimaryImage, MaxHeight, MaxWidth | [IsPrimaryImage](https://docs.microsoft.co
 
 In addition to image attributes, custom entities support zero or more file attributes that can contain any file data. These file attributes can contain a much larger amount of data than image attributes. For more information see [File attributes](file-attributes.md).
 
+> [!NOTE]
+> The ability to store more than one image attribute in an entity instance, storage of image data in an Azure blob, a maximum image size of 30MB, and file attributes are supported in <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy.SdkClientVersion> 9.0.45.329 or greater and Web API version 9.1 or greater.
+
 <a name="BKMK_SupportingAttributes"></a>   
 ## Supporting attributes  
  When an image attribute is added to an entity some additional attributes are created to support it.  

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

@@ -2,7 +2,7 @@
 title: "Impersonate another user (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Use impersonation to execute business logic on behalf of another Common Data Service user to provide a desired feature or service using the appropriate role and object-based security of that impersonated user." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 04/07/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -46,7 +46,7 @@ More information: [Build web applications using Server-to-Server (S2S) authentic
 
 ## Impersonate another user using the Web API
 
-To impersonate a user, add a request header named `MSCRMCallerID` with a GUID value equal to the impersonated user’s `systemuserid` before sending the request to the web service. 
+To impersonate a user, add a request header named `CallerObjectId` with a GUID value equal to the impersonated user's Azure Active Directory (AAD) object id before sending the request to the web service. The user's AAD object id is included in the [SystemUser.AzureActiveDirectoryObjectId](reference/entities/systemuser.md#BKMK_AzureActiveDirectoryObjectId).
 
 More information: [Impersonate another user using the Web API](webapi/impersonate-another-user-web-api.md).
 
@@ -70,3 +70,4 @@ More information: [Impersonate a user](impersonate-a-user.md).
 [Build web applications using Server-to-Server (S2S) authentication](build-web-applications-server-server-s2s-authentication.md)<br />
 [Impersonate another user using the Web API](webapi/impersonate-another-user-web-api.md)<br />
 [Write a plug-in](write-plug-in.md)
+ 

powerapps-docs/developer/common-data-service/impersonate-another-user.md

@@ -82,7 +82,7 @@ When hovering over any item of the graph, the following information is shown:
 ### See also
 
 [Introduction to ISV Studio for the Power Platform](isv-app-management.md)  
-[Home page](isv-app-management-homepage.md)  
-[Tenant page](isv-app-management-tenantpage.md)
-[AppSource checker](isv-app-management-appsource-checker.md)
-[Connector certification portal](https://docs.microsoft.com/connectors/custom-connectors/submit-certification)
+[Home page](isv-app-management-homepage.md)<br/>
+[Tenant page](isv-app-management-tenantpage.md)<br/>
+[AppSource checker](isv-app-management-appsource-checker.md)<br/>
+[Connector Certification](isv-app-management-certification.md)

powerapps-docs/developer/common-data-service/isv-app-management-apppage.md

@@ -1,6 +1,6 @@
 ---
 title: Introduction to the AppSource checker | Microsoft Docs
-description: Learn how to use app source checker.
+description: Learn how to use AppSource checker
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -25,38 +25,41 @@ search.app:
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
-AppSource checker allows an ISV to check the certification criteria of their app prior to [AppSource](https://appsource.microsoft.com/) submission. The checker will let you know if your solution file has errors that need to be corrected or if AppSource certification criteria have not been met. 
+You can use the AppSource checker to verify whether your app has met certification criteria before you submit it to [AppSource](https://appsource.microsoft.com/). The checker lets you know whether your solution file has errors that need to be corrected and verifies whether AppSource certification criteria have been met. 
 
-In ISV Studio, an ISV can either upload a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s) and be notified of any issues that need to be remediated. To do that:
+In ISV Studio, you can upload either a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s). You'll be notified whether any issues need to be remediated.
 
-1. In ISV Studio, select **AppSource checker** tab in the left and then select **Validate your app**.
+**To run AppSource checker**
+
+1. In ISV Studio, select **AppSource checker** in the leftmost pane, and then select **Validate your app**.
 
     > [!div class="mx-imgBorder"]
-    > ![AppSource checker](media/appsource-checker.png)
+    > ![AppSource checker](media/appsource-checker.png "AppSource checker")
 
-2. Click on **Browse** to upload a solution file from your local machine and select **Run Check** to validate.
+2. Select **Browse** to upload a solution file from your local machine, and then select **Run Check**.
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-browse-solution-files.png)
+   > ![Run check command](media/appsource-browse-solution-files.png "Run check command")
  
    > [!NOTE]
-   > If a user has previously uploaded a solution for validation then you will see a history of submissions instead of the screenshot above.
+   > If you've previously uploaded a solution for validation, you'll see a history of submissions instead of the screenshot above.
 
-3. Once the solution checker completes validating, a summary of results will be displayed along with the number of issues present (if any). Double-click on the solution file to see the issues in detail.
+3. After the validation check is complete, a summary of results is displayed with the number of issues found (if any). Double-click to select the solution file to see the issues in detail.
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-results-page.png)
+   > ![Summary of AppSource checker results](media/appsource-results-page.png "Summary of AppSource checker results")
 
-4. If the submission has no errors, you will see the following message:
+4. If the submission has no errors, you'll see the following message:
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-no-error-page.png)
+   > ![AppSource checker success message](media/appsource-no-error-page.png "AppSource checker success message")
    
-5. An ISV can download the validation report for their app and include it with their AppSource submission. 
+Now you can download the validation report for your app and include it with your AppSource submission. 
 
-## See Also
+### See also
 
 [Home page](isv-app-management-homepage.md)<br/>
 [App page](isv-app-management-apppage.md)<br/>
-[Tenant page](isv-app-management-tenantpage.md)
+[Tenant page](isv-app-management-tenantpage.md)<br/>
+[Connector certification](isv-app-management-certification.md)
 

powerapps-docs/developer/common-data-service/isv-app-management-appsource-checker.md

@@ -1,6 +1,6 @@
 ---
 title: Connector certification from ISV Studio | Microsoft Docs
-description: Learn how to submit a custom connector for certification using ISV Studio.
+description: Learn how to submit a custom connector for certification by using ISV Studio.
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -21,41 +21,43 @@ search.app:
   - D365CE
 ---
 
-# Connector Certification Portal
+# Connector certification
 
-If you own a service, API, or built a custom connector that you want to connect to Power Apps, Power Automate, Azure Logic Apps, or Power Query, you need to submit your connector to Microsoft for certification. 
+If you own a service or API—or you've built a custom connector that you want to connect to Power Apps, Power Automate, Azure Logic Apps, or Power Query—you need to submit your connector to Microsoft for certification. 
 
-The Connector certification portal is now in ISV Studio allowing the users to manage and track their connector certification submission. More information: [Get your connector certified](https://docs.microsoft.com/connectors/custom-connectors/submit-certification).
+Connector certification is now included in ISV Studio, so you can use it to manage and track your connector certification submission. More information: [Submit your connector for Microsoft certification](https://docs.microsoft.com/connectors/custom-connectors/submit-certification)
 
-Before you start submitting your connector for certification, see the [Instructions on submitting your connector](https://docs.microsoft.com/connectors/custom-connectors/certification-submission) article for submission requirements.
+> [!NOTE]
+> Before you start submitting your connector for certification, see [Instructions on submitting your connector](https://docs.microsoft.com/connectors/custom-connectors/certification-submission) for submission requirements.
 
-To certify your custom connector through ISV Studio:
+**To certify your custom connector through ISV Studio**
 
-1. In ISV Studio, select **Connector certification** tab in the left pane.
-2. Select the type of connector to certify and click on **Submit**.
+1. In ISV Studio, select **Connector certification** in the leftmost pane.
+
+2. Select the type of connector to certify, and then select **Submit**.
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification](media/connector-certification-submit.png)
+   > ![Connector certification](media/connector-certification-submit.png "Connector certification")
 
-3. In the **Connector submission** page, read the agreement details and check the **Accept terms** and click on **Next**.
+3. On the **Connector submission** page, read the agreement details, select the **Accept terms** check box, and then select **Next**.
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification Consent form](media/connector-certification-consent-form.png)
+   > ![Consent form](media/connector-certification-consent-form.png "Consent form")
 
 4. Select **Choose a file** to upload the custom connector from your local machine. 
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification choose file](media/connector-certification-choose-file.png)
+   > ![Choose file](media/connector-certification-choose-file.png "Choose file")
 
-5. Enter the required details and click on **Submit for review**. 
+5. Enter the required details, and then select **Submit for review**. 
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification choose file](media/connector-certification-submit-for-review.png)
+   > ![Submit for review](media/connector-certification-submit-for-review.png "Submit for review")
 
-6. After you submit your connector for review, you'll receive an email from Microsoft.
+After you submit your connector for review, you'll receive an email from Microsoft.
 
-## See Also
+### See also
 
 [Home page](isv-app-management-homepage.md)<br/>
 [App page](isv-app-management-apppage.md)<br/>
-[Tenant page](isv-app-management-tenantpage.md)
+[Tenant page](isv-app-management-tenantpage.md)