Merge pull request #1528 from MicrosoftDocs/master

information about new error code

Author: KumarVivek

powerapps-docs/developer/common-data-service/troubleshoot-plug-in.md

@@ -70,3 +70,20 @@ You can register the plug-in to run in the context of a user known to have the c
 <!-- But if you prefer that the logic in your plug-in adapt to the privileges that the calling user has, you really need to verify the user's privileges in your code.
 
 TODO: Add content that shows how to do this -->
+
+## Error: Message size exceeded when sending context to Sandbox
+
+<!-- This is the error code for an unexpected error we should be providing a specific error code -->
+Error Code: `-2147220970`<br />
+Error Message: `Message size exceeded when sending context to Sandbox. Message size: ### Mb`
+
+This error occurs when a message payload is greater than 116.85 MB **AND** a plug-in is registered for the message. The error message will include the size of the payload that caused this error.
+ 
+The limit will help ensure that users running applications cannot interfere with each other based on resource constraints. The limit will help provide a level of protection from unusually large message payloads that threaten the availability and performance characteristics of the Common Data Service platform.
+ 
+116.85 MB is large enough that it should be rare to encounter this case. The most likely situation where this case might occur is when you retrieve a record with multiple related records which include large binary files.
+ 
+If you encounter this error you can:
+
+1.	Remove the plug-in for the message. If there are no plug-ins registered for the message, the operation will complete without an error.
+2.	If the error is occurring in a custom client, you can modify your code so that it doesn't attempt to perform the work in a single operation. Instead, write code to retrieve the data in smaller parts.

powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md

@@ -59,7 +59,7 @@ To get started, open a new Developer Command Prompt for VS 2017 after installing
    > Today we offer two types of components **field** and **dataset**.
 
 4. To retrieve all the required project dependencies, run the command `npm install`.
-5. Open your project folder (`C:\Users\<your name>\Documents\My_PCF_Control\<component name>`) in any developer environment of your choice and get started with your custom component development. If you would like a to follow a step-by-step tutorial please scroll down see how a sample linear component is implemented.
+5. Open your project folder (`C:\Users\<your name>\Documents\My_PCF_Control\<component name>`) in any developer environment of your choice and get started with your custom component development. If you would like to follow a step-by-step tutorial, see [Implementing components in TypeScript](implementing-controls-using-typescript.md).
 
 ## Building your components
 
@@ -114,11 +114,11 @@ You can also interact with the component locally in real time and observe elemen
 
 ## Deploying your PowerApps component framework components
 
-Once the debugging and development is finished, you just have one step remaining - to deploy your new component.  
+Once the debugging and development is finished, you just have one step remaining to deploy your new component.  
 
 Follow the steps below to create and import a [solution](https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/solutions-overview) file:
 
-1. Create a new directory and go to it 'cd <new directory name>'
+1. Create a new directory and go to it `cd <new directory name>`
 2. Create a new solution project in the directory of your choice by using the command 
  `pac solution init --publisherName <enter your publisher name> --customizationPrefix <enter your publisher name>` after `cd <your new folder>`.
 

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

@@ -24,6 +24,7 @@ To create a new project, follow the steps below:
 3. `cd` into the new directory and run the command `cd LinearControl` 
 4. Create the component project using the command `pac pcf init --namespace SampleNamespace --name TSLinearInputControl --template field` 
 5. Install the project build tools using the command `npm install` 
+6. Open your project in any developer environment of your choice and start implementing your custom component.
 
 ## Implementing Manifest
 

powerapps-docs/developer/component-framework/overview.md

@@ -26,7 +26,6 @@ Use PowerApps component framework to create custom components in model-driven ap
 > [!IMPORTANT]
 > - PowerApps component framework is a preview feature.
 > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - [!INCLUDE[cc_preview_features_no_MS_support](../../includes/cc-preview-features-no-ms-support.md)]
 
 > [!NOTE]
 > Custom components are supported only on Unified Interface for [model-driven apps](/powerapps/maker/model-driven-apps/model-driven-app-overview) version 9.1.0.3842 or later.