Merge branch 'live' into patch-1

Author: Nkrb

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/maker/data-platform/change-solution-publisher-prefix.md",
+      "redirect_url": "create-solution#solution-publisher",
+      "redirect_document_id": "false"
+    },
     {
       "source_path": "powerapps-docs/maker/canvas-apps/monitor.md",
       "redirect_url": "../monitor-canvasapps",
@@ -1874,7 +1879,7 @@
       "source_path": "powerapps-docs/maker/maker/canvas-apps/webinars-listing.md",
       "redirect_url": "https://powerusers.microsoft.com/t5/Samples-Learning-and-Videos/ct-p/PA_Comm_Galleries",
       "redirect_document_id": "false"
-    },    
+    },
     {
       "source_path": "powerapps-docs/developer/common-data-service/org-service/index.md",
       "redirect_url": "/powerapps/developer/common-data-service/org-service/overview",
@@ -6099,7 +6104,7 @@
       "source_path": "powerapps-docs/developer/data-platform/webapi/index.md",
       "redirect_url": "/powerapps/developer/data-platform/webapi/overview",
       "redirect_document_id": "false"
-    },    
+    },
     {
       "source_path": "powerapps-docs/developer/data-platform/org-service/index.md",
       "redirect_url": "/powerapps/developer/data-platform/org-service/overview",

powerapps-docs/maker/TOC.yml

@@ -1954,6 +1954,8 @@
       href: ./data-platform/export-to-data-lake-data-adf.md
     - name: Analyze exported data with Power BI
       href: ./data-platform/export-to-data-lake-data-powerbi.md
+    - name: Export to data lake FAQ
+      href: ./data-platform/export-data-lake-faq.yml
   - name: Security in Dataverse
     href: /power-platform/admin/wp-security
   - name: Privileges for customization

powerapps-docs/maker/data-platform/change-solution-publisher-prefix.md

@@ -62,7 +62,7 @@ Like real-time workflow processes, actions have the following properties in the
 
   This property establishes that this is an action process. You can’t change this after you save the process.  
 
-- **table**  
+- **Entity**  
 
   With action processes, you can select a table to provide context for the real-time workflow just like other types of processes, but you also have the option to choose **None (global)**. Use this if your action doesn’t require the context of a specific table. You can’t change this after you save the process.  
 
@@ -93,16 +93,13 @@ When editing an action, you have the following options:
   
 - **Enable rollback**  
 
-
-<!-- from editor: The third sentence below is confusing. Can you take another pass at it? -->
-
-
-  Generally, processes that support transactions will “undo” (or roll back) the entire operation if any part of them fails. There are exceptions to this. Some actions developers might do in code initiated by the action might not support transactions. An example would be when the code perform actions in other systems that are beyond the scope of the transaction. Those can’t be rolled back by the action running in an app. Some messages in the platform don’t support transactions. But everything you can do just with the user interface of the action will support transactions. All the actions that are part of a real-time workflow are considered in transaction, but with actions you have the option to opt out of this.  
+  Generally, processes that support transactions will “undo” (or roll back) the entire operation if any part of them fails. There are exceptions to this. Actions executed in code by a developer initiated by the action might not support transactions. An example would be when the code perform actions in other systems that are beyond the scope of the transaction. Those can’t be rolled back by the action running in an app. Some messages in the platform don’t support transactions. But everything you can do just with the user interface of the action will support transactions. All the actions that are part of a real-time workflow are considered in transaction, but with actions you have the option to opt out of this.  
 
   You should consult with the developer who will use this message to determine whether it must be in transaction or not. Generally, an action should be in transaction if the actions performed by the business process don’t make sense unless all of them are completed successfully. The classic example is transferring funds between two bank accounts. If you withdraw funds from one account you must deposit them in the other. If either fails, both must fail.  
 
   > [!NOTE]
-  > You can’t enable rollback if a custom action is invoked directly from within a workflow. You can enable rollback if an action is triggered by a Power Apps web services message.  
+  > - You can’t enable rollback if a custom action is invoked directly from within a workflow. You can enable rollback if an action is triggered by a Power Apps web services message.  
+  > - If the action defined does not change data, but only retrieves data, there are certain situations where performance can be improved by disabling **Enable rollback.**
   
 - **Activate As**  
 
@@ -114,11 +111,6 @@ When editing an action, you have the following options:
 
 - **Add Stages, Conditions and Actions**  
 
-
-
-<!-- from editor: The following link opens a section titled "Add stages and steps". Do you want to change this to match? -->
-
-
   Like other processes, you specify what actions to perform and when to perform them. More information: [Add stages, conditions and actions](configure-actions.md#BKMK_AddStagesConditionsAndActions)
 
 <a name="BKMK_DefineProcessArgs"></a>   

powerapps-docs/maker/data-platform/configure-actions.md

@@ -0,0 +1,46 @@
+### YamlMime:FAQ
+metadata:
+  title: Frequently asked questions about exporting Dataverse table data to Azure data lake
+  description: Get answers to frequently asked questions about Power Apps export to data lake.
+  author: sabinn-msft
+  ms.service: powerapps
+  ms.search.keywords: 
+  ms.date: 02/10/2021
+  ms.author: sabinn
+  ms.reviewer: matp
+title: Power Apps component framework FAQs
+summary: This article provides information on frequently asked questions about exporting Dataverse table data to the Azure data lake.
+sections:
+- name: General
+  questions:
+   - question: When should I use a yearly or monthly partition strategy?
+     answer: |
+        For Dataverse tables where data volume is high within a year,we recommend you use monthly partitions. Doing so results in smaller files and better performance. Additionally, if the rows in Dataverse tables are updated frequently, splitting into multiple smaller files help improve performance in the case of in-place update scenarios.
+   - question: When do I use Append only mode for a historical view of changes?
+     answer: |
+         Append only mode is the recommended option for writing Dataverse table data to the lake, especially when the data volumes are high within a partition with frequently changing data. Again, this is a commonly used and highly recommended option for enterprise customers. Additionally, you can choose to use this mode for scenarios where the intent is to incrementally review changes from Dataverse and process the changes for ETL, AI, and ML scenarios. Append only mode provides a history of changes, instead of the latest change or in place update, and enables several time series from AI scenarios, such as prediction or forecasting analytics based on historical values. 
+   - question: What happens when I add a column?
+     answer: |
+        When you add a new column to a table in the source, it is also added at the end of the file in the destination in the corresponding file partition. While the rows that existed prior to the addition of the column won't show the new column, new or updated rows will show the newly added column.
+   - question: What happens when I delete a column?
+     answer: |
+        When you delete a column from a table in the source, the column is not dropped from the destination. Instead, the rows are no longer updated and are marked as null while preserving the previous rows.
+   - question: What happens when I delete a row?
+     answer: |
+        Deleting a row is handled differently based on which data write options you choose:
+        - In-place update: This is the default mode and when you delete a table row in this mode, the row is also deleted from the corresponding data partition in the Azure data lake. In other words, data is hard deleted from the destination. 
+        - Append-only: In this mode, when a Dataverse table row is deleted, it is not hard deleted from the destination. Instead, a row is added and set as isDeleted=True to the file in the corresponding data partition in Azure data lake.
+   - question: What happens when I add a new table to sync to the data lake?
+     answer: |
+        It is important to note that export to data lake simultaneously processes a fixed set of tables for initial sync at any given time. When a new table is added to the export to data lake profile, the incremental or delta sync for the existing tables are paused. While the delta messages for existing tables continue to queue, export to data lake won't process any messages from the delta queue until the initial sync for the newly added table is complete. This is true whether you create a new linked lake, a new export to data lake profile, or add a table to an existing profile. For new or existing profiles, we recommend that you add no more than 5 tables to sync to the data lake at a time. Adding more tables won't expedite the sync process. While initial sync for the newly added tables in ongoing, it will queue any delta changes on those tables into a single queue. Export to data lake won't process these deltas change until the initial sync for all previously added tables is complete.
+   - question: Does adding multiple Dataverse tables simultaneously to the lake impact performance?
+     answer: |
+        Adding multiple tables to export to data lake will impact performance in following scenarios: 
+        - Initial sync: When the tables are first added, there is a fixed set of tables which are synched for initial data at a time. We recommend adding no more than 5 tables at a time to new or existing linked lake or export to data lake profile. Adding more than the recommend number of tables doesn't expedite the sync since only the fixed set of tables are processed at a given time.  
+        - Delta sync: After the initial sync of tables are completed, any change on Dataverse for selected tables is added to a common queue in export to data lake. The queue is processed with a fixed set of parallel listeners. If you add more tables to the queue, export to data lake will process the messages, but if number of messages are higher, it will add latency for data to sync to the data lake. 
+
+additionalContent: |
+
+  ## See also
+
+  [Export table data to Azure Data Lake Storage Gen2](export-to-data-lake.md)