Merge pull request MicrosoftDocs#1962 from MicrosoftDocs/Nava_pcf

Changing custom to code components

Author: phecke

powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md

@@ -14,21 +14,21 @@ ms.topic: "article"
 
 # Add code components to a field or entity in model-driven apps
 
-code components let you transform fields that traditionally contain text into visualizations. Similarly, you can use code components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. code components can appear as visualizations on forms, dashboards, views, and homepage grids. 
+Code components let you transform fields that traditionally contain text into visualizations. Similarly, you can use code components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. code components can appear as visualizations on forms, dashboards, views, and homepage grids. 
 
 
    > [!div class="mx-imgBorder"] 
    > ![Custom slider control](../../maker/model-driven-apps/media/slider-control.PNG "Slider control for a field")
 
-## Add a custom component to a field
+## Add a code 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.
+Following the steps in this procedure will change the default label and text box field of the **Budget Amount** field to the slider code component on the Opportunity entity. You can use similar steps to replace an existing field with a code component or configure a code 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.
+3. In the form editor, double-click the field where you want to add a code 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**.
 
@@ -39,11 +39,11 @@ Following the steps in this procedure will change the default label and text box
 
 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.
+   - **Web**. To make the code 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.
+   - **Phone**. To make the code 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.
+   - **Tablet**. To make the code component available on tablet devices running Dynamics 365 for tablets, select the Tablet option next to the component.
 
    > [!div class="mx-imgBorder"] 
    > ![Choose the client apps to view the custom control](../../maker/model-driven-apps/media/choose-client.png "Choose the client apps to view the custom control") 
@@ -63,28 +63,28 @@ Following the steps in this procedure will change the default label and text box
 
    - **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.   
+   - **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 code 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
+## Add code 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:
+To add a code 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 arrow next to **Entities** tab a select the entity you want to add the code 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  
+## See the code 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.  
+ Open a record that includes the field with the code 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.  
 
 > [!div class="mx-imgBorder"] 
 > ![Slider control rendered on form](../../maker/model-driven-apps/media/slider-control.PNG "Slider control rendered on form")  

powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md

@@ -23,7 +23,7 @@ PowerApps component framework enables app makers to create code components to us
 In this experimental preview, PowerApps component framework enables app makers to create code components, debug, import and add them to canvas apps using the PowerApps CLI tooling. Only certain APIs are supported in this experimental preview. It is recommened to check each individual API whether it supports canvas apps or not. 
 
 > [!WARNING]
-> Code components contain code that may not be generated by Microsoft and can potentially access security tokens and data. When adding code components to an app, make sure that the custom component solutions are from trusted source.
+> Code components contain code that may not be generated by Microsoft and can potentially access security tokens and data. When adding code components to an app, make sure that the code component solutions are from trusted source.
 
 ## Prerequisites
 
@@ -73,7 +73,7 @@ To add code components to a canvas app:
 > To add code components to a field or an entity for model-driven apps, see [Add code components to model-driven apps](add-custom-controls-to-a-field-or-entity.md)
 
 1. Navigate to PowerApps Studio.
-2. Create a new canvas app or edit an existing app that you want to add the custom component to.
+2. Create a new canvas app or edit an existing app that you want to add the code component to.
 
    > [!IMPORTANT]
    > Make sure the code components solution zip file is already [imported](https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/import-update-export-solutions) into Common Data Service before you go onto the next step.

powerapps-docs/developer/component-framework/control-implementation-library.md

@@ -13,7 +13,7 @@ ms.topic: "article"
 ms.assetid: 5d100dc3-bd82-4b45-964c-d90eaebc0735
 ---
 
-Implementing the component library is one of the key step when you are developing code 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. 
+Implementing the component library is one of the key step when you are developing code components using PowerApps component framework. Developers can implement component library using TypeScript. Each code component must have a library that includes the definition of a function which returns an object that implements the methods described in the code component interface. 
 
 The object implements the following methods:
 
@@ -22,5 +22,5 @@ The object implements the following methods:
 - [getOutputs](reference/control/getoutputs.md) (Optional)
 - [destroy](reference/control/destroy.md) (Required)
 
-These methods controls the lifecycle of the custom component.
+These methods controls the lifecycle of the code component.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Create and build a custom component| Microsoft Docs
+title: Create and build a code component| Microsoft Docs
 description: Start creating a component using the PowerApps component framework Tooling
 keywords: PowerApps component framework, code components, Component Framework
 ms.author: nabuthuk
@@ -13,7 +13,7 @@ ms.topic: "article"
 ms.assetid: d2cbf58a-9112-45c2-b823-2c07a310714c
 ---
 
-# Create and build a custom component
+# Create and build a code component
 
 [!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
@@ -33,14 +33,14 @@ To get started, open a new Developer Command Prompt for VS 2017 after installing
    > Currently, PowerApps CLI supports two types of components: **field** and **dataset**.  For canvas apps, only field type is supported for experimental preview.
 
 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_Component\<component name>`) in any developer environment of your choice and get started with your custom component development.
+5. Open your project folder (`C:\Users\<your name>\Documents\My_PCF_Component\<component name>`) in any developer environment of your choice and get started with your code component development.
 
 ## Build your component
 
 To build the component project, open the project folder in Visual Studio Code and use the (Ctrl-Shift-B) command, then select the build options. Alternatively, you can also build the component quickly using the `npm run build` command in the Developer Command Prompt for VS 2017 window.
 
 > [!TIP]
-> To debug the component during or after the build operation, see [Debug a custom component](debugging-custom-controls.md).
+> To debug the component during or after the build operation, see [Debug a code component](debugging-custom-controls.md).
 
 ## Known Configuration issues and Workarounds
 
@@ -77,7 +77,7 @@ To build the component project, open the project folder in Visual Studio Code an
 ### See also
 
 [Debug code components](debugging-custom-controls.md)<br/>
-[Package a custom component](import-custom-controls.md)<br/>
+[Package a code component](import-custom-controls.md)<br/>
 [Add code components to a field or entity](add-custom-controls-to-a-field-or-entity.md)<br/>
 [Updating existing code components](updating-existing-controls.md)<br/>
 [PowerApps component framework API Reference](reference/index.md)<br/>

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

@@ -63,7 +63,7 @@ controlObj.init(context,notifyOutputChanged,state,container);
 |Parameter|Description|
 |---|---|
 |context| Contains all the information about how the component is configured and all the parameters that can be used within the component along with the [framework APIs](reference/index.md). For example, the `context.parameters.["property name from manifest"]` can be used to access the input property.|
-|notifyOutputChanged |Alerts the framework whenever the custom component has new outputs ready to be retrieved asynchronously.|
+|notifyOutputChanged |Alerts the framework whenever the code component has new outputs ready to be retrieved asynchronously.|
 |state|Contains component data from the previous page load in the current session if component explicitly stored it earlier using `setControlState API`.|
 |container|An HTML div element to which you can append the HTML elements for the UI that defines your component. To display the value in the UI, you must get the data from `context.parameters.controlValue object`.|
 
@@ -77,13 +77,13 @@ If the platform changes the data, it calls out the [updateView](reference/contro
 
 ### Page close
 
-Whenever a user goes away from the page, custom component loses the scope and all the memory allocated in that page for the objects in the component will be cleared. However, some methods based on the browser implementation mechanism might stay and consume memory. Typically, these are event handlers. If the user wants to store the information, they should implement the `setControlState` method so that the information is given next time within the same session.
+Whenever a user goes away from the page, code component loses the scope and all the memory allocated in that page for the objects in the component will be cleared. However, some methods based on the browser implementation mechanism might stay and consume memory. Typically, these are event handlers. If the user wants to store the information, they should implement the `setControlState` method so that the information is given next time within the same session.
 
 Developers should implement the [destroy](reference/control/destroy.md) method which is called when the page closes, and use it to remove any cleanup code such as removing any event handlers.
 
 ## Resources
 
-Each custom component should have a resource file to construct its visualization. You can define a resource file in the manifest. The resource node in the manifest file refers to the resources that the component requires to implement its visualization. More information: [Resources](manifest-schema-reference/resources.md)
+Each code component should have a resource file to construct its visualization. You can define a resource file in the manifest. The resource node in the manifest file refers to the resources that the component requires to implement its visualization. More information: [Resources](manifest-schema-reference/resources.md)
 
 ### Related topics
 

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

@@ -1,6 +1,6 @@
 ---
 title: "Debug code components | MicrosoftDocs"
-description: "How to debug a custom component using Fiddler and Native debugging"
+description: "How to debug a code component using Fiddler and Native debugging"
 manager: kvivek
 ms.date: 04/23/2019
 ms.service: "powerapps"
@@ -11,14 +11,14 @@ author: Nkrb
 ---
 # Debug code components
 
-Once you're done implementing the custom component logic, get started with testing and debugging the custom component using the `npm start` command. This builds the custom component and opens it in the local test harness.
+Once you're done implementing the code component logic, get started with testing and debugging the code component using the `npm start` command. This builds the code component and opens it in the local test harness.
 
 > [!div class="mx-imgBorder"]
 > ![test harness 1](media/test-harness-1.png "test harness 1")
 
-As shown in the image above, the browser window opens with 4 sections. The custom component is rendered in the left pane while the right pane has **Context Inputs**, **Data Inputs** and **Outputs** sections.
+As shown in the image above, the browser window opens with 4 sections. The code component is rendered in the left pane while the right pane has **Context Inputs**, **Data Inputs** and **Outputs** sections.
 
-- **Context Inputs** provides a way to specify the form factor and test the custom component with each form factor (web, tablet, phone). This is especially helpful when the custom component is dependent on a particular form factor capability. In the coming release, you can have the ability to specify the height and width.
+- **Context Inputs** provides a way to specify the form factor and test the code component with each form factor (web, tablet, phone). This is especially helpful when the code component is dependent on a particular form factor capability. In the coming release, you can have the ability to specify the height and width.
 - **Data Inputs** is an interactive UI that displays all the properties and their types or type-groups defined in the manifest file. It allows you to key in the mock data for each property. 
 - **Outputs** renders the output whenever a component's `getOutputs` method gets called.  
 

powerapps-docs/developer/component-framework/get-powerapps-cli.md

@@ -45,7 +45,7 @@ To use Microsoft PowerApps CLI, do the following:
 
 
 > [!NOTE]
-> - To deploy your custom component using PowerApps CLI, you must have a Common Data Service environment with system administrator or system customizer privileges.
+> - To deploy your code component using PowerApps CLI, you must have a Common Data Service environment with system administrator or system customizer privileges.
 > - Currently, PowerApps CLI is supported only on Windows 10.
 
 ## Update Microsoft PowerApps CLI to the latest version