Live publish

Author: buck1ey

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

@@ -81,7 +81,16 @@ To add code components to a canvas app:
 
 ## Delete a code component 
 
-To delete a code component from a canvas app, select the code component that you want to delete and then select the **Delete** button on the menu. When the code component is deleted from the app, all the code component elements get deleted from the app and the app package.
+To delete a code component from a canvas app:
+
+1. Open the app where you have added the code component. 
+1. Select the **Tree view** icon from the left pane and select the screen where you have added the code component. 
+1. Select **ellipse (...)** next to the code component and select **Delete**.
+
+   > [!div class="mx-imgBorder"]
+   > ![Delete code component](media/delete-code-component.png "Delete code component")
+
+1. Save the app to see the changes. 
 
 ## Update existing code components
 

powerapps-docs/developer/component-framework/media/delete-code-component.png

@@ -22,6 +22,9 @@ search.app:
 
 If there is an active instance of the process, the entity record is loaded with the process instance ID. If there is no active instance of the process, a new process instance is created and the entity record is loaded with the process instance ID. If there are multiple instances of the current process, the record is loaded with the first instance of the active process as per the defaulting logic, that is the most recently used process instance per user.
 
+> [!NOTE]
+> The `setActiveProcess` method should be used while creating or editing a record. Use the `setActiveProcess` method to set the active process for a business process flow instead of `processId` and `porocessInstanceId` with `Xrm.Navigation.openForm` method . 
+
 ## Syntax
 
 `formContext.data.process.setActiveProcess(processId, callbackFunction);`

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-data-process/activeprocess/setActiveProcess.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 05/29/2020
+ms.date: 09/22/2020
 ms.author: ropur
 search.audienceType: 
   - maker
@@ -69,7 +69,7 @@ Let's look at the steps required to use the Power Apps visual in your Power BI r
 The following limitations apply to the Power Apps visual:
 
 - Power Apps visual isn't supported for [guest users](share-app.md#share-with-guests).
-- Power Apps visual isn't supported in sovereign clouds.
+- Power Apps visual doesn't support multi-level embedding of Power Apps in Sovereign clouds. For example, embedding a Power BI report with Power Apps visual to a SharePoint page, or further embedding that SharePoint page to a Teams channel isn't supported on sovereign clouds.
 - If you change the data fields associated with the visual, you must edit the app from within the Power BI service by selecting the ellipsis (...) and then selecting **Edit**. Otherwise, the changes won't be propagated to Power Apps, and the app will behave in unexpected ways.
 - The Power Apps visual can't trigger a refresh of Power BI reports and Power BI data sources from within Power BI Desktop. If you write back data from the app to the same data source as the report, your changes won't be reflected immediately in Power BI Desktop. Changes are reflected on the next scheduled refresh.
 - The Power Apps visual can't filter the data or send any data back to the report.

powerapps-docs/maker/canvas-apps/powerapps-custom-visual.md

@@ -5,7 +5,7 @@ author: neerajnandwana-msft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 07/20/2020
+ms.date: 09/22/2020
 ms.author: nenandw
 ms.reviewer: tapanm
 ---
@@ -72,17 +72,17 @@ Once you add sections to your page, you can add portal components inside the sec
 
 6.    In the properties pane on the right side of the screen, enter or select the following information:
 
-    - **Min Height**: Enter the minimum height of the section. If you add a component that occupies more space than the specified height, the section expands to accommodate the component. By default, the minimum height is 100 px. You can also enter the height in points (pt) and percentage (%).
+       - **Min Height**: Enter the minimum height of the section. If you add a component that occupies more space than the specified height, the section expands to accommodate the component. By default, the minimum height is 100 px. You can also enter the height in points (pt) and percentage (%).
 
         > [!div class=mx-imgBorder]
-        > ![Alignment in the section](media/section-props-height.png "Alignment in the section")  
+        > ![Min Height](media/section-props-height.png "Min Height")  
 
-    - **Alignment**: Select whether the component in the section must be left, center, or right aligned.
+        - **Alignment**: Select whether the component in the section must be left, center, or right aligned.
 
         > [!div class=mx-imgBorder]
         > ![Alignment in the section](media/section-props-align.png "Alignment in the section")  
 
-    - **Background**: Select if you'd like to have color or an image as the section background.
+        - **Background**: Select if you'd like to have color or an image as the section background.
 
         - **Fill**: Select a color for the background.
 
@@ -405,14 +405,14 @@ To add a Power BI component to a web page:
 
         ![Apply roles](media/apply-roles-powerbi.png "Apply roles")
 
-        - You can enter multiple roles separated by a comma (for example, ```role_1,role_2```). For more information on defining roles in Power BI, go to [Row-level security (RLS) with Power BI](https://docs.microsoft.com/power-bi/service-admin-rls). <br>
+        - You can enter multiple roles separated by a comma (for example, `role_1,role_2`). For more information on defining roles in Power BI, go to [Row-level security (RLS) with Power BI](https://docs.microsoft.com/power-bi/service-admin-rls). <br>
         - Only available for access type **Embed for your customer**.
 
     1. **Apply filter**: Allows user to load the report with pre-filtered values. User can provide filter condition in the field. 
 
         ![Apply filter](media/apply-filter-powerbi.png "Apply filter")
 
-        - Filter parameter must be without ```?filter=``` prefix. For example, ```Table/Field eq 'value'```.
+        - Filter parameter must be without `?filter=''` prefix. For example, `Table/Field eq 'value'`.
         <br> For more information, go to [filter parameter details](https://docs.microsoft.com/power-bi/service-url-filters).
         - Only available for **Reports** with access types **Embed for your customer** and **Embed for your organization**.
 
@@ -469,4 +469,5 @@ Embedding multiple Power BI workspaces may need additional considerations. Refer
 
 ### See also
 
-[Microsoft Learn: Integration with Power BI](https://docs.microsoft.com/learn/modules/portals-integration/3-power-bi)
+- [Create and manage web pages](create-manage-webpages.md)
+- [Microsoft Learn: Integration with Power BI](https://docs.microsoft.com/learn/modules/portals-integration/3-power-bi)

powerapps-docs/maker/portals/compose-page.md

@@ -1,28 +1,32 @@
 ---
-title: "Add a chart to a webpage in a portal | MicrosoftDocs"
+title: "Add a chart created in a model-driven app to a webpage in portal"
 description: "Instructions to add a chart created in a model-driven app to a webpage in the portal."
 author: sandhangitmsft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 01/29/2020
+ms.date: 09/22/2020
 ms.author: sandhan
 ms.reviewer: tapanm
 ---
 
 # Add a chart created in a model-driven app to a webpage in portal
 
-You add a chart to a webpage by using a Liquid tag named [Chart](../liquid/portals-entity-tags.md#chart). You can add the chart Liquid tag in the **Copy** field on a webpage or in the **Source** field on a [Web template](../liquid/store-content-web-templates.md).
+You add a chart to a webpage by using a Liquid tag named [Chart](../liquid/portals-entity-tags.md#chart). You can add the chart Liquid tag in:
+
+- The **Copy** field on a webpage.
+- In the **Source** field on a [Web template](../liquid/store-content-web-templates.md).
 
-For example, {% chart id:EE3C733D-5693-DE11-97D4-00155DA3B01E %}
+For example, `{% chart id:EE3C733D-5693-DE11-97D4-00155DA3B01E %}`
 
 ![Chart example](../media/dynamics365-chart-example.png "Chart example")
 
 You can also specify the ID of a view (saved query) to filter the query. For example:
 
+```
 <!—Leads by Source – Open Leads -->
-
 {% chart id:"EE3C733D-5693-DE11-97D4-00155DA3B01E" viewid:"00000000-0000-0000-00AA-000010001006" %}
+```
 
 ## Get the ID of a chart
 
@@ -34,13 +38,13 @@ You can also specify the ID of a view (saved query) to filter the query. For exa
     ![Export a chart](../media/export-dynamics365-chart.png "Export a chart")
 
 5. Open the XML file of the exported chart in a text editor.
-6. Copy the value of the \<visualizationid\> tag.
+6. Copy the value of the `<visualizationid>` tag.
 
     ![Get chartid for a chart](../media/dynamics365-chart-chartid.png "Get the chart ID for a chart")
 
-7. Paste the visualizationid value into your Liquid chart tag declaration for the chart ID parameter, for example:
+7. Paste the `visualizationid` value into your Liquid chart tag declaration for the chart ID parameter, for example:
 
-    {% chart id:EE3C733D-5693-DE11-97D4-00155DA3B01E %}.
+    `{% chart id:EE3C733D-5693-DE11-97D4-00155DA3B01E %}`
 
 ## Get the ID of a view
 
@@ -65,11 +69,39 @@ You must open the view editor to get the view ID to be used with the Liquid char
 
 Read privilege is asserted for the target entity being queried in the chart. For anonymous or authenticated users to be able to view the chart, you must ensure that the appropriate [Entity Permission](assign-entity-permissions.md) records are created and assigned to applicable [web roles](create-web-roles.md). 
  
-If permission is not granted, the user will see an access denied message.
+If permission isn't granted, the user will see an access denied message.
+
+## Supported charts and chart types
+
+The following chart types are supported in portals:
+
+- Column
+- Bar
+- Area
+- Pie
+- Line
+- Funnel
+
+Supported configuration for Legend Entries (Series):
+
+- Single Series
+- Multiple Series
+- Aggregates Types - Sum, Counts, Min, Max, Avg in Single or Multiple Series
+- Top X / Bottom X Rules
+
+Supported configuration for Horizontal (Category) Axis Labels:
+
+- Categories on attributes of an entity or linked entity (on attribute data types supported by portals).
+- Multiple categories (X-Axis).
+- *Group by* and *Order by* on attributes.
+- Date Grouping Types – Day, Month, Year on Primary Entity and First Level Linked Entity.
+    - Date Grouping by Week, Fiscal Year, Fiscal Period, and Quarter are **not supported**.
+    - Date Grouping on Linked Entity attributes is supported only until the first level of Link.
 
 ## Unsupported charts and chart types
 
 The following chart types are currently not supported in portals:
+
 - Doughnut
 - Tag
 
@@ -95,6 +127,13 @@ The following table lists the charts that are currently not supported in portals
 | By Subject                              | bcd3f9a5-913b-e511-80d1-00155db10d2b | knowledgearticle | 
 | | |
 
+## Other considerations
+
+- Long labels on Horizontal (Category) Axis Label can get overlapped when using a high number of data points on the chart.
+- Hovering over currency data types formatting shows values with spaces instead of separators.
+- Numeric fields are currently shown in decimal format.
+- Horizontal Axis values can show only up-to 15 Labels.
+
 ### See also
 
 [Microsoft Learn: Model-driven charts in portals](https://docs.microsoft.com/learn/modules/portals-integration/4-model-driven-charts)