Merge branch 'master' into v-shrutibahl-cusomize-inspections

Author: tapanm-MSFT

.gitignore

@@ -19,3 +19,5 @@ powerapps-docs/.vs/ProjectSettings.json
 powerapps-docs/.vs/slnx.sqlite
 powerapps-docs/.vs/VSWorkspaceState.json
 /.vs/slnx.sqlite-journal
+powerapps-docs/teams/media/how-to-architecture/Thumbs.db
+powerapps-docs/teams/media/milestones-broad-distribution/Thumbs.db

.openpublishing.redirection.json

@@ -6279,6 +6279,11 @@
       "source_path": "powerapps-docs/developer/data-platform/developer-resources-page.md",
       "redirect_url": "/powerapps/developer/data-platform/view-download-developer-resources",
       "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/maker/data-platform/business-events.md",
+      "redirect_url": "/powerapps/developer/data-platform/business-events",
+      "redirect_document_id": "false"
     }
   ]
 }

powerapps-docs/chatbots.md

@@ -13,7 +13,7 @@ ms.reviewer: mvakoc
 
 Power Virtual Agents allows you to quickly create and maintain intelligent chatbots using a no-code interface. App makers can create and manage their chatbots directly from [Power Apps](https://make.powerapps.com). 
 
-![Chatbots from Power Apps](media/chatbots.png "Chatbots from Power Apps")
+![Chatbots from Power Apps.](media/chatbots.png "Chatbots from Power Apps")
 
 You can create and manage your chatbots using the **Chatbots** option in the left navigation pane.
 

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

@@ -19,7 +19,7 @@ Code components let you transform columns that traditionally contain text into v
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 
    > [!div class="mx-imgBorder"] 
-   > ![Custom slider control](../../maker/model-driven-apps/media/slider-control.PNG "Custom slider control ")
+   > ![Custom slider control.](../../maker/model-driven-apps/media/slider-control.PNG "Custom slider control ")
 
 ## Add a code component to a column
 
@@ -36,7 +36,7 @@ Following the steps below will change the default label and text box column of t
 5. On the Add Control page, select the component that you want, such as the **Linear Slider** component, and then select **Add**.
 
    > [!div class="mx-imgBorder"] 
-   > ![Add linear slider control](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
+   > ![Add linear slider control.](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
 
 6. Choose the client where you want the component to appear.
 
@@ -47,12 +47,12 @@ Following the steps below will change the default label and text box column of t
    - **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") 
+   > ![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") 
 
 7. Select the pencil icon next to **Min**, **Max**, and **Step**, set the property option, and then select **OK**.  
 
    > [!div class="mx-imgBorder"] 
-   > ![Add custom control properties](../../maker/model-driven-apps/media/ccf-add-properties.png "Add custom control properties")
+   > ![Add custom control properties.](../../maker/model-driven-apps/media/ccf-add-properties.png "Add custom control properties")
 
    - **Min**. Set the minimum accepted value. You can bind a static value that you enter or bind the value to an existing column. In this example **Bind to static value** is **Currency** and the minimum value that can be entered is *zero*.  
 
@@ -88,7 +88,7 @@ To add a code component like dataset component or simple table component to a gr
  Open a record that includes the column with the code component, such as the Opportunity form from the previous example, and view how the column is changed. The column is now rendered as a slider component instead of the text column.  
 
 > [!div class="mx-imgBorder"] 
-> ![Slider control rendered on form](../../maker/model-driven-apps/media/slider-control.PNG "Slider control rendered on form")  
+> ![Slider control rendered on form.](../../maker/model-driven-apps/media/slider-control.PNG "Slider control rendered on form")  
 
 ### See also
 

powerapps-docs/developer/component-framework/code-components-alm.md

@@ -31,10 +31,10 @@ The [create your first code component](implementing-controls-using-typescript.md
 To add code components to a column or a table in model-driven apps, see [Add code components to model-driven apps](add-custom-controls-to-a-field-or-entity.md).
 
 > [!div class="mx-imgBorder"] 
-> ![Add linear slider control](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
+> ![Add linear slider control.](../../maker/model-driven-apps/media/add-slider.PNG "Add linear slider control")
 
 > [!div class="mx-imgBorder"]
-> ![Data Set Grid component](media/add-dataset-component.png "Data Set Grid component")
+> ![Data Set Grid component.](media/add-dataset-component.png "Data Set Grid component")
 
 ## Update existing code components
 

powerapps-docs/developer/component-framework/code-components-best-practices.md

@@ -14,8 +14,6 @@ ms.topic: "article"
 
 # Community resources for Power Apps component framework
 
-[!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
-
 The following is a list of some community resources created by the Power Apps community that you can use to create code components in model-driven and canvas apps using Power Apps component framework and Microsoft Power Platform CLI. 
 
 > [!NOTE]            
@@ -31,7 +29,7 @@ Make sure that you review the licensing terms and the source code before you dow
 > Code component run in the context of the end user who is using the component and can perform any action that may include accessing, capturing, and modifying the data. 
 
 > [!div class="mx-imgBorder"]
-> ![Component gallery](media/pcf-gallery.PNG "Components gallery")
+> ![Component gallery.](media/pcf-gallery.PNG "Components gallery")
 
 ## Videos        
 
@@ -76,7 +74,21 @@ The following is the list of blogs created by Power Apps community.
 
 ## Tools
 
-The [Code component builder](https://www.xrmtoolbox.com/plugins/Maverick.PCF.Builder/) is a tool from XrmToolBox that lets you create code components in visual manner using Microsoft Power Platform CLI.
+The [code component builder](https://www.xrmtoolbox.com/plugins/Maverick.PCF.Builder/) is a tool that enables you to build code components with ease where you do not need to write the CLI commands but still use the [Microsoft Power Platform CLI](/powerapps/developer/data-platform/powerapps-cli) under the hood. Most of the commands are consolidated, making it easier to build components. 
+
+There are two versions of the code component builder. Both of them are called **PCF Builder** and are listed below:
+1. [PCF Builder](https://www.xrmtoolbox.com/plugins/Maverick.PCF.Builder/) for XrmToolBox.
+2. [PCF Builder](https://marketplace.visualstudio.com/items?itemName=danish-naglekar.pcf-builder) for Visual Studio Code.
+
+[PCF Builder for XrmToolBox](https://www.xrmtoolbox.com/plugins/Maverick.PCF.Builder/) provides a graphical user interface that lets you create code components in visual manner using Microsoft Power Platform CLI.
+
+> [!div class="mx-imgBorder"]
+> ![Component Builder in XrmToolBox.](media/pcf-builder-xrmtoolbox.png "Component Builder in XrmToolBox")
+
+[PCF Builder extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=danish-naglekar.pcf-builder) provides a guided experience that not only lets  you create code components but you can preview code component inside of Visual Studio Code.
+
+> [!div class="mx-imgBorder"]
+> ![Component Builder in VS Code.](media/pcf-builder-vscode.png "Component Builder in Visual Studio Code")
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]