Merge branch 'main' into EDITING-TASK-18472-New

Author: tapanm-MSFT

.openpublishing.redirection.json

@@ -8754,6 +8754,11 @@
       "source_path": "powerapps-docs/maker/data-platform/azure-synapse-link-troubleshooting-guide.md",
       "redirect_url": "/power-apps/maker/data-platform/export-data-lake-faq",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/canvas-apps/slow-performance-sources.md",
+      "redirect_url": "/power-apps/maker/canvas-apps/create-performant-apps-overview",
+      "redirect_document_id": false
     }
   ]
 }

CODEOWNERS

@@ -1,16 +1,19 @@
 # Lines starting with '#' are comments.
 # Each line is a file pattern followed by one or more owners.
 
-/powerapps-docs/                                    @KumarVivek
-/powerapps-docs/administrator/                      @jimholtz @KumarVivek
-/powerapps-docs/developer/                          @PHecke @KumarVivek @JimDaly
-/powerapps-docs/developer/data-platform/cli         @JimDaly @KumarVivek
-/powerapps-docs/developer/data-platform/cli         @JimDaly @KumarVivek
-/powerapps-docs/developer/model-driven-apps         @JimDaly @KumarVivek
-/powerapps-docs/maker/canvas-apps                   @tapanm-msft @KumarVivek
-/powerapps-docs/maker/data-platform                 @Mattp123 @KumarVivek
-/powerapps-docs/maker/model-driven-apps             @Mattp123 @KumarVivek
-/powerapps-docs/maker/common                        @Mattp123 @tapanm-msft @KumarVivek
-/powerapps-docs/maker/portals                       @nickdoelman @KumarVivek
-/powerapps-docs/user/                               @mduelae @KumarVivek
-/powerapps-docs/teams/                              @tapanm-msft @KumarVivek
+/powerapps-docs/                                    @tapanm-msft
+/powerapps-docs/cards                               @tapanm-msft @mduelae
+/powerapps-docs/developer/                          @PHecke @leeclontz @JimDaly
+/powerapps-docs/developer/data-platform/cli         @JimDaly @leeclontz
+/powerapps-docs/developer/data-platform/cli         @JimDaly @leeclontz
+/powerapps-docs/developer/model-driven-apps         @JimDaly @leeclontz
+/powerapps-docs/guidance                            @tapanm-msft @mduelae @Mattp123
+/powerapps-docs/maker/canvas-apps                   @tapanm-msft @mduelae
+/powerapps-docs/maker/data-platform                 @Mattp123 @tapanm-msft
+/powerapps-docs/maker/model-driven-apps             @Mattp123 @tapanm-msft
+/powerapps-docs/maker/common                        @Mattp123 @tapanm-msft @mduelae
+/powerapps-docs/maker/portals                       @professorkendrick @tapanm-msft
+/powerapps-docs/mobile                              @tapanm-msft @sericks007
+/powerapps-docs/sample-apps                         @tapanm-msft @mduelae
+/powerapps-docs/user                                @sericks007 @tapanm-msft
+/powerapps-docs/teams                               @tapanm-msft @mduelae

powerapps-docs/developer/data-platform/define-alternate-keys-entity.md

@@ -126,7 +126,7 @@ If the alternate key is deleted while an index creation job is still pending or
 
  [Use an alternate key to reference a record](use-alternate-key-reference-record.md)<br />
  [Use change tracking to synchronize data with external systems](use-change-tracking-synchronize-data-external-systems.md)<br />
- [Use Upsert to insert or update a record](use-upsert-insert-update-record.md)
+ [Use Upsert to insert or update a record](use-upsert-insert-update-record.md)<br />
  [Define alternate keys to reference records](../../maker/data-platform/define-alternate-keys-reference-records.md)
 
 

powerapps-docs/developer/data-platform/media/plugin-base-class-diagram.png

@@ -1,7 +1,7 @@
 ---
 title: "Generate early-bound classes for the SDK for .NET"
 description: "Learn how to use the Power Platform CLI pac modelbuilder build command to generate early-bound classes for use with the Microsoft Dataverse SDK for .NET. This tool generates early-bound .NET classes that represent the Entity Data Model used by Dataverse."
-ms.date: 10/18/2023
+ms.date: 01/26/2024
 author: kkanakas
 ms.author: kartikka
 ms.reviewer: pehecke
@@ -63,8 +63,7 @@ Use the following steps to get started:
    "entitynamesfilter-comment": "Filters the list of entities are retrieved when reading data from Dataverse.",
    "entityNamesFilter": [
       "account",
-      "contact",
-      "sample_*"
+      "contact"
    ],
    "entitytypesfolder-comment": "Folder name that contains entities.",
    "entityTypesFolder": "Entities",
@@ -149,7 +148,9 @@ Generation Complete - 00:00:01.815
 PS C:\projects\exampleproject\model>
 ```
 
-When you inspect the output, notice that it only generates classes for the tables specified by `entityNamesFilter` and only the messages specified in the `messageNamesFilter`. You should specify which tables (entities) and messages you use in your project. Otherwise, classes for all tables and messages are generated. You can use `*` as a wildcard character in these values. This is useful when items in your solution share a common customization prefix.
+When you inspect the output, notice that it only generates classes for the tables specified by `entityNamesFilter` and only the messages specified in the `messageNamesFilter`. You should specify which tables (entities) and messages you use in your project. Otherwise, classes for all tables and messages are generated. 
+
+For `messageNamesFilter`, you can use `*` as a wildcard character in these values. This is useful when messages in your solution share a common customization prefix.
 
 `pac modelbuilder build` writes the files into folders with names you can control in the settings file:
 
@@ -180,7 +181,7 @@ Here's an example showing how to generate files with the same settings as the ex
 ```powershell
 PS C:\>pac modelbuilder build `
    --outdirectory C:\projects\exampleproject\model `
-   --entitynamesfilter 'account;contact;sample_*' `
+   --entitynamesfilter 'account;contact' `
    --generatesdkmessages `
    --messagenamesfilter 'searchautocomplete;searchquery;sample_*' `
    --namespace ExampleProject `
@@ -207,8 +208,7 @@ This doesn't include all the settings because it uses the default options. If yo
   "optionSetsTypesFolder": "OptionSets",
   "entityNamesFilter": [
     "account",
-    "contact",
-    "sample_*"
+    "contact"
   ],
   "messageNamesFilter": [
     "searchautocomplete",

powerapps-docs/developer/data-platform/org-service/generate-early-bound-classes.md

@@ -2,7 +2,7 @@
 title: "Use plug-ins to extend business processes (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how plug-ins execute in response to a data processing event to augment or modify the default behavior of the platform." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.collection: get-started
-ms.date: 02/14/2023
+ms.date: 01/24/2024
 ms.reviewer: "phecke"
 ms.topic: "article"
 author: "divkamath" # GitHub ID
@@ -34,36 +34,37 @@ Any classes in an assembly that are to be registered on an event framework (pipe
 - Pass information to another 'downstream' plug-in registered in the same pipeline
 - More...
 
-Plug-ins can be registered to execute synchronously or asynchronously. A synchronous plug-in will cause the data operation to wait until the code in the plug-in completes. This has an impact on end-user perceived performance of the system, which is why synchronous plug-ins must execute and complete quickly. Asynchronous plug-in execution is queued and later executed after the data operation has completed.
+Plug-ins can be registered to execute synchronously or asynchronously. A synchronous plug-in causes the data operation to wait until the code in the plug-in completes. This delay has an impact on end-user perceived performance of the system, which is why synchronous plug-ins must execute and complete quickly. Asynchronous plug-in execution is queued and later executed after the data operation has completed.
 
 ## When to use plug-ins
 
-People frequently compare workflows and plug-ins as the choices to apply custom business logic. There is significant overlap in the capabilities of workflows and plug-ins. Plug-ins can do everything workflows can do but the inverse is not true. But this doesn't mean you should just use plug-ins for anything that can't be done with a workflow. There are other capabilities to achieve requirements without using plug-ins.
+People frequently compare custom workflow activities and plug-ins as the choices to apply custom business logic. There is significant overlap in the capabilities of workflow activities and plug-ins. Plug-ins can do everything workflow activities can do but the inverse is not true. This fact doesn't mean you should just use plug-ins for anything that can't be done with a workflow. There are other capabilities to achieve requirements without using plug-ins.
 
-- Workflows can use custom workflow extensions (workflow activities) which allow you to create re-usable conditions and actions with code that can be used within multiple workflows.
+- Workflows can use custom workflow activities which allow you to create re-usable conditions and actions with code that can be used within multiple workflows.
 
 - Calculated and rollup fields provide capabilities that could previously only be done using workflows.
 
 - Custom Actions are a type of process similar to workflows that allow for creating re-usable messages that can be called from other workflows or from the web service endpoints.
 
-- Azure Service Bus integration and Webhooks can be used to push data to external systems where logic can be applied using many different resources.
+- Azure Service Bus integration and webhooks can be used to push data to external systems where logic can be applied using many different resources.
 
 - Power Automate provides many capabilities that previously were performed using plug-ins.
 
-You have many options available to you. You should evaluate each of them to understand the best way to meet your requirements.
+You should evaluate each of these options to understand the best way to meet your requirements.
 
 ### Advantages of plug-ins
 
 These are the main advantages of plug-ins:
 
 - Plug-ins perform well. A well written plug-in provides the most performant way to apply custom business logic.
-- Plug-ins are powerful. Many developers would prefer to use the skills and knowledge they possess to define logic and use the capabilities to work directly with the organization web service or external services in code. An experienced plug-in developer can be very productive.
+- Plug-ins are powerful. Many developers would prefer to use the skills and knowledge they possess to define logic and use the capabilities to work directly with the Dataverse web service or external services in code. An experienced plug-in developer can be very productive.
 - Plug-ins extend the capability of Dataverse when an out-of-box business solution does not exist.
 
 ### Disadvantages of plug-ins
 
 - Plug-ins require the special skills of a software developer to create and maintain the plug-in code. Smaller businesses may not have access to a developer with the needed skills. Business processes can change rapidly and providing options to enable change without requiring a developer can allow the system to adapt more rapidly.
-- Plug-ins can be abused. A poorly written plug-in can cause significant impact on the performance of the data processing pipeline and ultimately the environment. The great power of plug-ins needs to be applied with some restraint and consideration for the impact it has on the system as a whole.
+- Plug-ins can be abused. A poorly written plug-in can cause significant impact on the perceived performance of the data processing pipeline and ultimately the end-user interactive environment. The great power of plug-ins needs to be applied with some restraint and consideration for the impact it has on the system as a whole.
+- Plug-ins have only a short period of time (a hard limit) to complete their work.
 
 ## Next Steps
 
@@ -84,8 +85,7 @@ These topics provide additional details common to plug-in development.
 - [Handle exceptions](handle-exceptions.md)
 - [Register a plug-in](register-plug-in.md)
 - [Debug Plug-ins](debug-plug-in.md), and [Tracing and logging](logging-tracing.md)
-- [Troubleshoot plug-ins](troubleshoot-plug-in.md)
-- [Dependent Assembly plug-ins](dependent-assembly-plugins.md)
+- [Troubleshoot plug-ins](/troubleshoot/power-platform/power-apps/dataverse/dataverse-plug-ins-errors)
 
 Once you have read and understand the plug-in concepts listed above, consider exploring these additional plug-in related capabilities and technologies.
 

powerapps-docs/developer/data-platform/plug-ins.md

@@ -46,8 +46,8 @@ This will open the **Profiler Settings** dialog which will provide the following
 
 |Field|Description|
 |--|--|
-|**Workflow**|Select the Workflow or Custom action that contains the workflow activity you want to debug.|
-|**Steps**|Select the specific steps within that workflow or custom action that you want to debug.|
+|**Workflow**|Select the Workflow that contains the workflow activity you want to debug.|
+|**Steps**|Select the specific steps within that workflow that you want to debug.|
 |**Specify profile storage**|We recommend that you choose **Persist to Entity**.|
 |**Set profiler settings**|If your are working with a system where the workflow is being executed frequently, you can reduce performance impact by choosing to limit the number of profiles that are captured.|
 |**Include secure configuration**|This provides the option to avoid seeing potentially sensitive data that may be passed as secure configuration.|