Merge pull request #1508 from MicrosoftDocs/master

Pushing changes live

Author: KumarVivek

powerapps-docs/developer/common-data-service/org-service/early-bound-programming.md

@@ -136,7 +136,26 @@ Which style you choose to use is up to you. The following table provides the adv
 
 Because all the generated classes inherit from the <xref:Microsoft.Xrm.Sdk.Entity> class used with late-bound programming, you can work with entities, attributes, and relationships not defined within classes.
 
-### Example
+### Examples
+
+The following example shows one way to mix early and late binding methods using <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceContext>.  
+  
+```csharp  
+// Create an organization service context object  
+AWCServiceContext context = new AWCServiceContext(_serviceProxy);  
+  
+// Instantiate an account object using the Entity class.  
+Entity testaccount = new Entity("account");  
+  
+// Set several attributes. For account, only the name is required.   
+testaccount["name"] = "Fourth Coffee";  
+testaccount["emailaddress1"] = "[email protected]";  
+  
+// Save the entity using the organization service context object.  
+context.AddToAccountSet(testaccount);  
+context.SaveChanges();  
+  
+```  
 
 If a custom attribute was not included in the generated classes, you can still use it.
 
@@ -154,6 +173,17 @@ var account = new Account();
 Guid accountid = svc.Create(account);
 ```
 
+#### Assign an early bound instance to a late bound instance  
+ The following sample shows how to assign an early bound instance to a late bound instance.  
+  
+```csharp
+Entity incident = ((Entity)context.InputParameters[ParameterName.Target]).ToEntity<Incident>();  
+Task relatedEntity = new Task() { Id = this.TaskId };  
+  
+incident.RelatedEntities[new Relationship("Incident_Tasks")] =   
+new EntityCollection(new Entity[] { relatedEntity.ToEntity<Entity>() });  
+```
+
 ### See also
 
 [Entity Operations using the Organization service](entity-operations.md)<br />

powerapps-docs/developer/common-data-service/org-service/organizationservicecontext.md

@@ -85,7 +85,17 @@ if (pam != null)
     Task firstTask = pam.Contact_Tasks.FirstOrDefault();  
 }  
 ```  
+### Use the AddLink method  
+ You can use the <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceContext.AddLink(Microsoft.Xrm.Sdk.Entity,Microsoft.Xrm.Sdk.Relationship,Microsoft.Xrm.Sdk.Entity)> method to create associations. You must call the <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceContext.SaveChanges> method before the server is updated with the new link information.  
 
+ The following code example shows how to create an association between a contact and an account.  
+  
+```csharp  
+Relationship relationship = new Relationship("account_primary_contact");  
+context.AddLink(contact, relationship, account);  
+context.SaveChanges();  
+```  
+
 <a name="save_changes"></a>
 
 ## Save changes

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

@@ -18,10 +18,16 @@ ms.assetid: d2cbf58a-9112-45c2-b823-2c07a310714c
 
 Use PowerApps Command Line Interface (CLI) to create, debug and deploy custom PowerApps component framework components. PowerApps CLI will enable developers to quickly create PowerApps component framework components and will in the future be expanded to include support for additional development and Application Lifecycle Management (ALM) experiences. 
 
-## What is Microsoft PowerApps CLI 
+## What is Microsoft PowerApps CLI? 
 
 Microsoft PowerApps CLI is a simple, single-stop developer command line interface enabling you to create custom component. PowerApps CLI is also the first step towards a comprehensive ALM story where enterprise developers and ISVs can create, build, debug and publish their PowerApps and Dynamics 365 for Customer Engagement apps extensions and customizations quickly and efficiently.  
 
+> [!IMPORTANT]
+> - Microsoft PowerApps CLI tools are a pre-release version and may be different from the commercially released version.
+> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
+> - If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose. 
+> - Microsoft doesn't provide support for this preview feature. Microsoft Technical Support won’t be able to help you with issues or questions.
+
 ## Prerequisites to use PowerApps CLI
 
 To use PowerApps CLI you will need the following:
@@ -32,11 +38,7 @@ To use PowerApps CLI you will need the following:
    - Option 2: Install .NET Core 2.2 SDK and install Visual Studio Code
 - Install Microsoft PowerApps CLI from [here](http://download.microsoft.com/download/D/B/E/DBE69906-B4DA-471C-8960-092AB955C681/powerapps-cli-0.1.51.msi)
 
-> [!IMPORTANT]
-> - Microsoft PowerApps CLI tools are a pre-release version and may be different from the commercially released version.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose. 
-> - Microsoft doesn't provide support for this preview feature. Microsoft Technical Support won’t be able to help you with issues or questions.
+
 
 > [!NOTE]
 > To deploy your custom component, you will need Common Data Service environment with System administrator or System customizer privileges.

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

@@ -17,11 +17,6 @@ Custom components are a type of solution component, which means they can be incl
 
 You add custom components by including them in a solution and then importing it into the system. Once they are in the system, admin and system customizers can configure form fields, sub-grids, views, and dashboard sub-grids to use them in place of default component.
 
-> [!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)]
-
 Custom components are comprised into three components:
 
 1. Manifest

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

@@ -17,11 +17,6 @@ ms.author: "nabuthuk"
 
 It is not possible to define multiple components in a single manifest file. 
 
-> [!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)]
-
 ## Calling Processes/Actions
 
 This is not supported. As of today, you can only call dialog boxes using the [Navigation](reference/navigation.md) method.

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

@@ -15,12 +15,6 @@ ms.author: "nabuthuk"
 
 This tutorial will walk you through creating a new custom component in Typescript. The sample component is a linear input component.  The linear input component enables users to enter numeric values using a visual slider instead of directly keying in values. 
 
-> [!IMPORTANT]
-> - Microsoft PowerApps CLI tools are a pre-release version and may be different from the commercially released version.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose. 
-> - Microsoft doesn't provide support for this preview feature. Microsoft Technical Support won’t be able to help you with issues or questions.
-
 ## Creating a new component project
 
 To create a new project, follow the steps below:

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

@@ -16,11 +16,6 @@ ms.author: "nabuthuk"
 
 With the release of PowerApps component framework, you can now create your own custom components to improve the user experience in model-driven apps. Even though you can create your own components, there are some limitations that restrict developers implementing some features in the custom components. Below are some of the limitations:
 
-> [!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)]
-
 ## Support for external libraries
 
 For public preview, components should bundle all code including external library content into the primary code bundle. To see an example of how the PowerApps command line interface can help with bundling your external library content into a component-specific bundle, see [Angular flip component](sample-controls/angular-flip-control.md) example.
@@ -31,4 +26,4 @@ For public preview, components should bundle all code including external library
 ## Related topics
 
 [PowerApps component framework API Reference](reference/index.md)<br/>
-[PowerApps component framework Overview](overview.md)
+[PowerApps component framework Overview](overview.md)

powerapps-docs/developer/component-framework/updating-existing-controls.md

@@ -17,12 +17,6 @@ ms.assetid: d2cbf58a-9112-45c2-b823-2c07a310714c
 
 If you are a PowerApps component framework Private Preview participant and have already built custom components, you will need to make some minor updates to make it compatible with the new ALM-centric project structures. To use the new PowerApps component framework build tools with your existing PowerApps component framework custom component source, a few changes are required.
 
-> [!IMPORTANT]
-> - Microsoft PowerApps CLI tools are a pre-release version and may be different from the commercially released version.
-> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)] 
-> - If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose. 
-> - Microsoft doesn't provide support for this preview feature. Microsoft Technical Support won’t be able to help you with issues or questions.
-
 ## Creating an empty project
 
 Use PowerApps CLI to create a new empty project for your custom component. More information [Create components using tooling](create-custom-controls-using-pcf.md).