Merge branch 'live' into patch-1

Author: jlattimer

powerapps-docs/developer/.vs/VSWorkspaceState.json

@@ -0,0 +1,12 @@
+{
+  "ExpandedNodes": [
+    "",
+    "\\control-framework",
+    "\\control-framework\\manifest-schema-reference",
+    "\\control-framework\\manifest-schema-reference\\includes",
+    "\\control-framework\\reference",
+    "\\control-framework\\reference\\client"
+  ],
+  "SelectedNode": "\\control-framework\\reference\\client\\getclient.md",
+  "PreviewInSolutionExplorer": false
+}

powerapps-docs/developer/.vs/developer/v15/.suo

@@ -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/.vs/slnx.sqlite

@@ -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/common-data-service/.vs/slnx.sqlite

@@ -0,0 +1,78 @@
+---
+title: Add Custom Components to a field or entity | Microsoft Docs
+description: Process to import custom components
+keywords:
+ms.author: nabuthuk
+manager: kvivek
+ms.date: 04/23/2019
+ms.service: "powerapps"
+ms.suite: ""
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+---
+
+# Add custom components to a field or entity
+
+Custom components let you transform fields that traditionally contain text into visualizations. Similarly, you can use custom components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. Custom components can appear as visualizations on forms, dashboards, views, and homepage grids. 
+
+## Add a custom component to a field
+
+Following the steps in this procedure will change the default label and text box field of the **Budget Amount** field to the slider custom component on the Opportunity entity. You can use similar steps to replace an existing field with a custom component or configure a custom component for a custom field.
+
+1. Open solution explorer.
+
+2. Expand **Entities**, expand the entity that you want, such as the **Opportunity** entity, select **Forms**, and then open a form such as the **Main** form.
+
+3. In the form editor, double-click the field where you want to add a custom component, such as the **Budget Amount** field on the opportunity main form. Alternatively, you can create a custom field.
+
+4. On the **Field Properties** page, select the **Controls** tab, and then select **Add Control**.
+
+5. On the Add Control page, select the component that you want, such as the **Linear Slider** component, and then select **Add**.
+
+6. Choose the client where you want the component to appear.
+
+   - **Web**. To make the custom component available from any web browser, select the Web option next to the component. Notice that setting the Web option includes rendering the component in web browsers on PCs, Macs, and mobile devices.
+
+   - **Phone**. To make the custom component available on phones running Dynamics 365 for phones, select the Phone option next to the component.
+
+   - **Tablet**. To make the custom component available on tablet devices running Dynamics 365 for tablets, select the Tablet option next to the component.
+7. Select the pencil icon next to **Min**, **Max**, and **Step**, set the property option, and then select **OK**.  
+  
+   - **Min**. Set the minimum accepted value. You can bind a static value that you enter or bind the value to an existing field. In this example **Bind to static value** is **Currency** and the minimum value that can be entered is *zero*.  
+  
+       - **Bind to a static value**. Select the data type, such as a whole number (Whole.None), currency, floating point (FP), or decimal. Next, enter a number that represents the minimum accepted value for the field.  
+  
+       - **Bind to values on a field**. Select a field from the list that will be used as the minimum accepted value.  
+  
+   - **Max**. Set the maximum accepted value for the field. Similar to the Min value, you can bind a static value that you enter or bind the value to an existing field as described earlier. In this example, **Bind to static value** is **Currency** and the maximum value that can be entered is **1 billion**.  
+  
+   - **Step**. This represents the unit to increment or decrement when adding to or subtracting from  the current value. For example, for budget amount you can select 100 dollar increments\decrements.  
+  
+   - **Hide Default Control**. Selecting this option hides the component so neither the component or the data is displayed in any of the clients that don't support the custom component.   
+  
+8. Select **OK**, to close the Field Properties page.  
+  
+9. To activate the customization, on the entity form select **Save**, and then select **Publish**.  
+  
+10. Select **Save and Close** to close the form editor.  
+  
+## Add custom component to an entity
+
+To add a custom component like data-set component or simple table component to a grid or view, follow the steps below:
+
+  - Navigate to **Settings > Customizations** and click on **Customize the System**.
+  - Click on the arrow next to **Entities** tab a select the entity you want to add the custom component. 
+  - Click on the **Controls** tab and click on **Add a control**.
+  - On the Add Control page, select the component that you want, such as Simple Table component and then select **Add**.
+  - Choose the client where you want the component to appear.
+
+
+## See the custom component in action  
+
+ Open a record that includes the field with the custom component, such as the Opportunity form from the previous example, and view how the field is changed. The field is now rendered as a slider component instead of the text field.  
+
+### See also
+
+[Implementing components in TypeScript](implementing-controls-using-typescript.md)<br/>
+[PowerApps component framework API Reference](reference/index.md)<br/>
+[PowerApps component framework Overview](overview.md)

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

@@ -0,0 +1,25 @@
+---
+title: Component implementation library | Microsoft Docs
+description: Create custom components using JavaScript or TypeScript
+keywords:
+ms.author: nabuthuk
+manager: kvivek
+ms.date: 04/23/2019
+ms.service: "powerapps"
+ms.suite: ""
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+ms.assetid: 5d100dc3-bd82-4b45-964c-d90eaebc0735
+---
+
+Implementing the component library is one of the key step when you are developing custom components using PowerApps component framework. Developers can implement component library using TypeScript. Each custom component must have a library that includes the definition of a function which returns an object that implements the methods described in the custom component interface. 
+
+The object implements the following methods:
+
+- [init](reference/control/init.md) (Required)
+- [updateView](reference/control/updateview.md) (Required)
+- [getOutputs](reference/control/getoutputs.md) (Optional)
+- [destroy](reference/control/destroy.md) (Required)
+
+These methods controls the lifecycle of the custom component.
+