Merge pull request #922 from MicrosoftDocs/master

AFTOwen · web-flow · commit 9dea9c1610d1 · 2018-11-02T13:54:04.000-07:00
Publish: limitations to PDF viewer, etc.
diff --git a/powerapps-docs/developer/common-data-service/xrm-tooling/toc.yml b/powerapps-docs/developer/common-data-service/xrm-tooling/toc.yml
@@ -20,8 +20,6 @@
       href: use-xrm-tooling-delete-data.md
     - name: Use messages with the ExecuteCrmOrganizationRequest method
       href: use-messages-executecrmorganizationrequest-method.md
-    - name: Use XRM tooling to execute web request against Web API
-      href: use-xrm-tooling-to-execute-web-request.md
   - name: Use XRM tooling with classes generated using the code-generation tool
     href: use-xrm-tooling-classes-generated-code-generation-tool.md
   - name: Use the XRM tooling common login control in your client applications
diff --git a/powerapps-docs/developer/common-data-service/xrm-tooling/use-crmserviceclient-constructors-connect.md b/powerapps-docs/developer/common-data-service/xrm-tooling/use-crmserviceclient-constructors-connect.md
@@ -158,8 +158,8 @@ CrmServiceClient crmSvc = new CrmServiceClient(new System.Net.NetworkCredential(
 
 [Use connection strings in XRM tooling to connect to CDS for Apps](use-connection-strings-xrm-tooling-connect.md)<br />
 [Use XRM Tooling Windows PowerShell Cmdlets to connect to CDS for Apps](use-powershell-cmdlets-xrm-tooling-connect.md)<br />
-[Use XRM Tooling API to execute actions in CDS for Apps](use-xrm-tooling-execute-actions.md)<br />
-<!-- TODO:
-[Sample: Quick Start for CDS for Apps](../sample-quick-start.md)<br /> -->
+[Use XRM Tooling API to execute actions in CDS for Apps](use-xrm-tooling-execute-actions.md)
 <xref:Microsoft.Xrm.Tooling.Connector.AuthenticationType><br />
 [Build windows client applications using the XRM tools](build-windows-client-applications-xrm-tools.md)
+<!-- TODO:[Sample: Quick Start for CDS for Apps](../sample-quick-start.md)-->
+
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/clientapi-form-context.md b/powerapps-docs/developer/model-driven-apps/clientapi/clientapi-form-context.md
@@ -109,10 +109,8 @@ reference)](reference/collections.md).
   
 ### Related topics
 
-[getFormContext method](reference/executioncontext/getFormContext.md)
-
-[getGlobalContext method](reference/xrm-utility/getGlobalContext.md)
-
+[getFormContext method](reference/executioncontext/getFormContext.md)<br/>
+[getGlobalContext method](reference/xrm-utility/getGlobalContext.md)<br/>
 [Execution context methods](reference/execution-context.md) 
 
  
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/clientapi-grid-context.md b/powerapps-docs/developer/model-driven-apps/clientapi/clientapi-grid-context.md
@@ -17,47 +17,28 @@ search.app:
 ---
 # Client API grid context
 
+Grids present data in a tabular format. Grids can span the entire form or can be one of the items on a form; the latter are called **subgrids**.
 
-
-The grid context object provides a reference to the grid or a subgrid on a form against which the current code is executed.
-
-Depending on where your JavaScript code is executed, you get the **gridContext** object in one of the following ways:
-
-- **Executing code on a form event**: Use the [formContext](clientapi-form-context.md) object to get an instance of the form where the code is executed, and then retrieve the subgrid control on the form. For example, when you know the name of a subgrid control (say **Contacts** subgrid in the default account form), you can access it using the following code:
-
-    ```JavaScript
-    function doSomething(executionContext) {
-       var formContext = executionContext.getFormContext(); // get the form Context
-       var gridContext = formContext.getControl("Contacts"); // get the grid context
-
-       // Perform operations on the subgrid
-    }
-    ```
-
-- **Executing code on a grid event**: Use the [getFormContext](reference/executioncontext/getFormContext.md) method of the passed in execution context object to directly return reference to the grid where the code is executed. The grid events include [OnChange](reference/events/grid-onchange.md), [OnRecordSelect](reference/events/grid-onrecordselect.md), and [OnSave](reference/events/grid-onsave.md).
-
-    ```JavaScript
-    function doSomething(executionContext) {
-        var gridContext = executionContext.getFormContext(); // get the grid context
-
-        // Perform operations on the grid
-    }
-    ```
-
-For more information about working with methods and events available for grids and subgrids, see [Grids and subgrids](reference/grids.md).
+The Client API grid context object provides reference to a subgrid on a form against which the current code is executed. 
 
 > [!NOTE]
-> Getting the **gridContext** object for JavaScript functions for ribbon actions is different from how you get it in form scripting. More information: [Form and grid context in ribbon actions](../pass-data-page-parameter-ribbon-actions.md#form-and-grid-context-in-ribbon-actions)
+> Getting the context of a grid (spanning the entire form) is only supported in ribbon commands. More information: [Form and grid context in ribbon actions](/powerapps/developer/model-driven-apps/pass-data-page-parameter-ribbon-actions#form-and-grid-context-in-ribbon-actions)
 
-## Related topics
+Use the [formContext](clientapi-form-context.md) object to get an instance of the form where the code is executed, and then retrieve the subgrid control on the form. For example, when you know the name of a subgrid control (say **Contacts** subgrid in the default account form), you can access it using the following code:
 
-[Client API form context](clientapi-form-context.md)
+```JavaScript
+function doSomething(executionContext) {
+   var formContext = executionContext.getFormContext(); // get the form Context
+   var gridContext = formContext.getControl("Contacts"); // get the grid context
 
-[Client API execution context](clientapi-execution-context.md)
+   // Perform operations on the subgrid
+}
+```
 
-[Understand the Client API object model](understand-clientapi-object-model.md)
+## Related topics
 
+[Client API form context](clientapi-form-context.md)<br/>
+[Client API execution context](clientapi-execution-context.md)<br/>
+[Understand the Client API object model](understand-clientapi-object-model.md)<br/>
 [Grids and subgrids](reference/grids.md)
 
- 
-
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/clientapi-xrm.md b/powerapps-docs/developer/model-driven-apps/clientapi/clientapi-xrm.md
@@ -51,6 +51,5 @@ To access the global context information in a standalone HTML Web resource, you
 
 ### Related topics
 
-[Understand the Client API object model](understand-clientapi-object-model.md)
-
-[Deprecated client APIs](/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#some-client-apis-are-deprecated)
+[Understand the Client API object model](understand-clientapi-object-model.md)<br/>
+[Deprecated client APIs](/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#some-client-apis-are-deprecated)
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/events-forms-grids.md b/powerapps-docs/developer/model-driven-apps/clientapi/events-forms-grids.md
@@ -53,9 +53,7 @@ Use the [setSharedVariable](reference/executioncontext/setSharedVariable.md) and
 
 ### Related topics
 
-[Understand the Client API object model](understand-clientapi-object-model.md)
-
-[Client API execution context](clientapi-execution-context.md)
-
-[Events (Client API reference)](reference/events.md)
+[Understand the Client API object model](understand-clientapi-object-model.md)<br/>
+[Client API execution context](clientapi-execution-context.md)<br/>
+[Events (Client API reference)](reference/events.md)<br/>
 
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/reference.md b/powerapps-docs/developer/model-driven-apps/clientapi/reference.md
@@ -34,8 +34,6 @@ The topics under this section are organized as follows:
 
 ### Related topics
 
-[Apply business logic using client scripting in model-driven apps](../client-scripting.md)
-
-[Understand the Client API object model](understand-clientapi-object-model.md)
-
-[Model-driven apps Developer Overview](../overview.md)
+[Apply business logic using client scripting in model-driven apps](../client-scripting.md)<br/>
+[Understand the Client API object model](understand-clientapi-object-model.md)<br/>
+[Model-driven apps Developer Overview](../overview.md)
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-WebApi/execute.md b/powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-WebApi/execute.md
@@ -1,5 +1,5 @@
 ---
-title: "execute (Client API reference) in model-driven apps| MicrosoftDocs"
+title: "Xrm.WebApi.online.execute (Client API reference) in model-driven apps| MicrosoftDocs"
 ms.date: 10/31/2018
 ms.service: "crm-online"
 ms.topic: "reference"
@@ -14,14 +14,14 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# execute (Client API reference)
+# Xrm.WebApi.online.execute (Client API reference)
 
 
 
 [!INCLUDE[./includes/execute-description.md](./includes/execute-description.md)]
 
 > [!NOTE]
-> This method isn't supported for [Unified Interface](/dynamics365/get-started/whats-new/customer-engagement/new-in-version-9#unified-interface-framework-for-new-apps). Also, this method is supported only for the online mode, which implies that you must use the [Xrm.WebApi.online](online.md) object to execute the method. Otherwise, it will fail.
+> This method is supported only for the online mode ([Xrm.WebApi.online](online.md)).
 
 ## Syntax
 
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-WebApi/executeMultiple.md b/powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-WebApi/executeMultiple.md
@@ -1,27 +1,24 @@
 ---
-title: "executeMultiple (Client API reference) in model-driven apps| MicrosoftDocs"
+title: "Xrm.WebApi.online.executeMultiple (Client API reference) in model-driven apps| MicrosoftDocs"
 ms.date: 10/31/2018
-ms.service: "crm-online"
+ms.service: "powerapps"
 ms.topic: "reference"
-applies_to: "Dynamics 365 (online)"
 ms.assetid: d4e92999-3b79-4783-8cac-f656fc5f7fda
 author: "KumarVivek"
 ms.author: "kvivek"
-manager: "amyla"
+manager: "annbe"
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
 ---
-# executeMultiple (Client API reference)
-
-
+# Xrm.WebApi.online.executeMultiple (Client API reference)
 
 [!INCLUDE[./includes/executeMultiple-description.md](./includes/executeMultiple-description.md)]
 
 > [!NOTE]
-> This method isn't supported for [Unified Interface](/dynamics365/get-started/whats-new/customer-engagement/new-in-version-9#unified-interface-framework-for-new-apps). Also, this method is supported only for the online mode, which implies that you must use the [Xrm.WebApi.online](online.md) object to execute the method. Otherwise, it will fail. 
+> This method is supported only for the online mode ([Xrm.WebApi.online](online.md)). 
 
 If you want to execute multiple requests in a transaction, you must pass in a change set as a parameter to this method. [Change sets](../../../../common-data-service/webapi/execute-batch-operations-using-web-api.md#change-sets) represent a collection of operations that are executed in a transaction. You can also pass in individual requests and change sets together as parameters to this method.
 
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/understand-clientapi-object-model.md b/powerapps-docs/developer/model-driven-apps/clientapi/understand-clientapi-object-model.md
@@ -42,8 +42,7 @@ At the root of the Client API object model are the following contexts and the Xr
 
 ### Related topics
 
-[Client API global context](clientapi-xrm.md#client-api-global-context)
-
+[Client API global context](clientapi-xrm.md#client-api-global-context)<br/>
 [Client API reference](reference.md)
 
 
diff --git a/powerapps-docs/maker/canvas-apps/controls/control-pdf-viewer.md b/powerapps-docs/maker/canvas-apps/controls/control-pdf-viewer.md
@@ -21,10 +21,17 @@ An experimental control that shows the content of a PDF file.
 Show text, graphics, and other content in a PDF file by adding this type of control and setting its **Document** property to the URL, enclosed in double quotation marks, of the file that you want to show.
 
 ## Limitations
-Note that due to the security architecture of PowerApps, PDF Viewer only supports HTTPS links and not HTTP.  
-If the PDF document resides on a server with restrictive CORS settings, you may not be able to view it within your app.  To resolve this issue, the server that hosts PDF documents needs to permit cross origin requests (CORS) coming from powerapps.com.
+1. The security architecture of PowerApps requires the PDF Viewer to support only HTTPS links, not HTTP.  
 
-In case the document cannot be opened in PowerApps, the option to open the document in an external browser is presented to the end user.  This option is also available in the control menu for all external documents.
+2. The **Document** property must link directly to the PDF file. Server redirects or HTML views of the document aren't supported.
+
+3. The server that hosts the document must not require authentication.
+
+4. You may not be able to view a PDF document in your app if the document resides on a server that has restrictive cross-origin resource sharing (CORS) settings. To resolve this issue, the server that hosts PDF documents must permit cross-origin requests from powerapps.com.
+
+App users can work around these limitations by opening PDF documents in an external browser, as prompted if the control can't open a document. This option is also available in the control menu for all external documents.
+
+App makers can work around these limitations by including PDF documents as media resources in the app. That way, the PDF Viewer control can always show the document.
 
 ## Key properties
 **Document** – The URL, enclosed in double-quotation marks, of a PDF file.
diff --git a/powerapps-docs/maker/common-data-service/data-platform-create-entity.md b/powerapps-docs/maker/common-data-service/data-platform-create-entity.md
@@ -40,6 +40,9 @@ Sign in to PowerApps at [https://web.powerapps.com](https://web.powerapps.com/?u
 
     * **Plural display name** - This field is autopopulated when you enter a display name, but you can change it if needed. The plural display name is the name of the entity in the Common Data Service WebAPI and is used when interacting with this entity from PowerApps or Flow.
     * **Name** - This field is also autopopulated when you enter a display name. The prefix was set up when the environment was created and ensures that the entities you create can be exported and imported into other environments without conflicting with other entity names. You can change this prefix by updating the prefix on your Publisher for the Common Data Service Default Solution. To keep existing apps from breaking, you cannot change the name after saving the entity.
+
+       > [!NOTE]
+       > In order for the entity name to work with [Dynamics 365 for Customer Service embedded knowledge search](/dynamics365/customer-engagement/customer-service/set-up-knowledge-management-embedded-knowledge-search), the maximum entity name length including the publisher prefix can’t exceed 24 characters.
      
     ![New Entity](./media/data-platform-cds-create-entity/newentitypanel.png "New entity panel")
 
