diff --git a/.acrolinx-config.edn b/.acrolinx-config.edn
index 6f4aef56fb..6c746bf002 100644
--- a/.acrolinx-config.edn
+++ b/.acrolinx-config.edn
@@ -28,7 +28,7 @@
**A minimum total score of 80 is required. The total score is an average of the subscores.**
Select **Total score** to review the Acrolinx scorecard for your article. Try to increase your individual scores, ex. Correctness. Your article will be clearer and more consistent with Microsoft standards.
-| Article | **Total score** **Required: 80** | Word and phrases (Brand, terms) Preferred: 100 | Correctness (Spelling, grammar) Preferred: 100 | Clarity (Readability) Preferred: 80 |
+| Article | Total score (Required: 80) | Terminology | Spelling and grammar | Clarity (Readability) |
|---------|:------------------------------------:|:--------------------------------------------------------:|:--------------------------------------------------------:|:---------------------------------------------:|
"
diff --git a/.gitignore b/.gitignore
index c279f87b56..4862a2e5e5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -19,5 +19,3 @@ 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
diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1
deleted file mode 100644
index aadef76202..0000000000
--- a/.openpublishing.build.ps1
+++ /dev/null
@@ -1,17 +0,0 @@
-param(
- [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1",
- [string]$parameters
-)
-# Main
-$errorActionPreference = 'Stop'
-
-# Step-1: Download buildcore script to local
-echo "download build core script to local with source url: $buildCorePowershellUrl"
-$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition
-$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1"
-Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination"
-
-# Step-2: Run build core
-echo "run build core script with parameters: $parameters"
-& "$buildCorePowershellDestination" "$parameters"
-exit $LASTEXITCODE
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index bc3d9db024..38600d7ba7 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -1,51 +1,101 @@
{
"redirections": [
{
- "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md",
- "redirect_url": "query/overview",
+ "source_path": "powerapps-docs/developer/data-platform/org-service/samples/enable-field-security-entity.md",
+ "redirect_url": "column-level-security",
"redirect_document_id": "false"
},
{
- "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#select-columns",
- "redirect_url": "query/select-columns",
+ "source_path": "powerapps-docs/developer/data-platform/org-service/samples/retrieve-field-permissions.md",
+ "redirect_url": "column-level-security",
"redirect_document_id": "false"
},
{
- "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#join-tables",
- "redirect_url": "query/join-tables",
+ "source_path": "powerapps-docs/developer/data-platform/org-service/samples/retrieve-field-sharing-records.md",
+ "redirect_url": "column-level-security",
"redirect_document_id": "false"
},
{
- "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#order-rows",
- "redirect_url": "query/order-rows",
+ "source_path": "powerapps-docs/developer/data-platform/field-security-entities.md",
+ "redirect_url": "column-level-security",
"redirect_document_id": "false"
},
{
+ "source_path": "powerapps-docs/developer/data-platform/calculated-rollup-attributes.md",
+ "redirect_url": "specialized-columns.md",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/deletemultiple.md",
+ "redirect_url": "bulk-operations#deletemultiple",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/test-engine/overview.md",
+ "redirect_url": "/power-platform/test-engine/overview",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/test-engine/powerfx.md",
+ "redirect_url": "/power-platform/test-engine/powerfx",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/test-engine/yaml.md",
+ "redirect_url": "/power-platform/test-engine/yaml",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/quick-start-register-configure-simplespa-application-msal-js.md",
+ "redirect_url": "webapi/quick-start-js-spa",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md",
+ "redirect_url": "query/overview",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#select-columns",
+ "redirect_url": "query/select-columns",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#join-tables",
+ "redirect_url": "query/join-tables",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#order-rows",
+ "redirect_url": "query/order-rows",
+ "redirect_document_id": "false"
+ },
+ {
"source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#filter-rows",
"redirect_url": "query/filter-rows",
"redirect_document_id": "false"
- },
- {
+ },
+ {
"source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#page-results",
"redirect_url": "query/page-results",
"redirect_document_id": "false"
- },
- {
+ },
+ {
"source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#aggregate-data",
"redirect_url": "query/aggregate-data",
"redirect_document_id": "false"
- },
- {
+ },
+ {
"source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#count-number-of-rows",
"redirect_url": "query/count-rows",
"redirect_document_id": "false"
- },
- {
+ },
+ {
"source_path": "powerapps-docs/developer/data-platform/bypass-custom-business-logic.md#bypass-power-automate-flows",
"redirect_url": "bypass-power-automate-flows",
"redirect_document_id": "false"
},
- {
+ {
"source_path": "powerapps-docs/developer/data-platform/bypass-custom-business-logic-preview.md",
"redirect_url": "bypass-custom-business-logic",
"redirect_document_id": "false"
@@ -4102,7 +4152,7 @@
},
{
"source_path": "powerapps-docs/developer/common-data-service/field-security-entities.md",
- "redirect_url": "../data-platform/field-security-entities",
+ "redirect_url": "../data-platform/column-level-security",
"redirect_document_id": false
},
{
@@ -5022,7 +5072,12 @@
},
{
"source_path": "powerapps-docs/developer/common-data-service/org-service/samples/assign-record-to-new-owner.md",
- "redirect_url": "../../../data-platform/org-service/samples/assign-record-to-new-owner",
+ "redirect_url": "../../../data-platform/org-service/samples/assign-records-to-team",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/developer/data-platform/org-service/samples/assign-record-to-new-owner.md",
+ "redirect_url": "./assign-records-to-team",
"redirect_document_id": false
},
{
@@ -8932,7 +8987,7 @@
},
{
"source_path": "powerapps-docs/maker/canvas-apps/working-with-dynamic-schema.md",
- "redirect_url": "/power-apps/maker/canvas-apps/untyped-and-dynamic-objects#converting-formulas-that-return-untyped-objects-that-previously-returned-boolean",
+ "redirect_url": "/power-apps/maker/canvas-apps/untyped-and-dynamic-objects#converting-formulas-that-return-dynamic-values-that-previously-returned-boolean",
"redirect_document_id": false
},
{
@@ -9145,6 +9200,16 @@
"redirect_url": "/power-platform/responsible-ai-overview",
"redirect_document_id": "false"
},
+ {
+ "source_path": "powerapps-docs/user/cs-template-options.md",
+ "redirect_url": "/power-apps/user/email-template-create",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/user/cs-email-template-builder.md",
+ "redirect_url": "/power-apps/user/email-template-create",
+ "redirect_document_id": "false"
+ },
{
"source_path": "powerapps-docs/maker/portals/control-portal-creation.md",
"redirect_url": "/power-pages/admin/control-site-creation",
@@ -9194,16 +9259,381 @@
"source_path": "powerapps-docs/maker/model-driven-apps/overview-model-driven-samples.md",
"redirect_url": "/power-apps/maker/model-driven-apps/",
"redirect_document_id": "false"
- },
- {
- "source_path": "powerapps-docs/maker/data-platform/relationships-overview.md",
- "redirect_url": "/power-apps/maker/data-platform/create-edit-entity-relationships",
- "redirect_document_id": "false"
- },
- {
- "source_path": "powerapps-docs/maker/model-driven-apps/create-a-model-driven-app.md",
- "redirect_url": "/power-apps/maker/model-driven-apps/build-first-model-driven-app",
- "redirect_document_id": "false"
- }
+ },
+ {
+ "source_path": "powerapps-docs/maker/data-platform/relationships-overview.md",
+ "redirect_url": "/power-apps/maker/data-platform/create-edit-entity-relationships",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/data-platform/create-edit-global-option-sets-solution-explorer.md",
+ "redirect_url": "/power-apps/maker/data-platform/custom-picklists",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/model-driven-apps/create-a-model-driven-app.md",
+ "redirect_url": "/power-apps/maker/model-driven-apps/build-first-model-driven-app",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/portals/configure/azure-ad-b2c.md",
+ "redirect_url": "/power-pages/configure/azure-ad-b2c",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/portals/configure/create-custom-portal-management-app.md",
+ "redirect_url": "/power-pages/configure/portal-management-app",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/portals/configure/list-odata-feeds.md",
+ "redirect_url": "/power-pages/configure/web-api-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/portals/configure/configure-azure-ad-b2c-provider-manual.md",
+ "redirect_url": "/power-pages/security/authentication/azure-ad-b2c-provider",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/connections/connection-azure-sqldatabase.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/connections/sql-connection-overview",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/administrator.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/app-maker.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/bdm.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/developer.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/functional-consultant.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/learning-catalog.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/learning-catalog/solution-architect.md",
+ "redirect_url": "/training/browse/?expanded=power-platform&products=power-apps",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/model-driven-apps/power-bi-content-management-power-apps-solutions.md",
+ "redirect_url": "/power-apps/maker/model-driven-apps/create-edit-powerbi-embedded-page",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/model-driven-apps/create-edit-powerbi-report-dataset-components.md",
+ "redirect_url": "power-apps/maker/model-driven-apps/create-edit-powerbi-embedded-page",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/model-driven-apps/customize-manage-powerbi-components.md",
+ "redirect_url": "/power-apps/maker/model-driven-apps/create-edit-powerbi-embedded-page",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/user/find-admin.md",
+ "redirect_url": "/power-apps/user/navigation",
+ "redirect_document_id": "false"
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/expense-report-install.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/get-started-test-drive",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/help-desk-install.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/get-started-test-drive",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/open-and-run-a-sample-app.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/get-started-test-drive",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/customize-list-form.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-alerts-flow.md",
+ "redirect_url": "/power-bi/collaborate-share/service-flow-integration",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-approval-flow.md",
+ "redirect_url": "/power-automate/create-approval-response-options",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-build-app.md",
+ "redirect_url": "/powerapps-docs/maker/index",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-build-report.md",
+ "redirect_url": "/power-bi/create-reports/service-quick-create-sharepoint-list",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-embed-report.md",
+ "redirect_url": "/power-bi/collaborate-share/service-embed-report-spo",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-generate-app.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-intro.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-publish-report.md",
+ "redirect_url": "/power-bi/paginated-reports/paginated-reports-save-to-power-bi-service",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-setup.md",
+ "redirect_url": "/powerapps-docs/maker/canvas-apps/app-from-sharepoint",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint-scenario-summary.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint/scenarios-choice-to-lookup.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint/scenarios-customize-view-based-on-column-status.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint/scenarios-filter-search-list.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint/scenarios-intro.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint/scenarios-lookup-list-permissions.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sharepoint/scenarios-sharepoint-form-from-scratch.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/sharepoint-list-integration-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/webinars.md",
+ "redirect_url": "/power-apps/",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/model-driven-apps/powerbi-control.md",
+ "redirect_url": "/power-apps/maker/model-driven-apps/create-edit-powerbi-embedded-page",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/common/maker-matching.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/ai-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/data-platform-create-app.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/get-started-create-from-blank",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/get-started-create-from-data.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/get-started-create-from-blank",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/connections/connection-excel.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/get-started-create-from-blank",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/how-to-excel-tips.md",
+ "redirect_url": "https://support.microsoft.com/en-us/office/create-and-format-tables-e81aa349-b006-4f8a-9806-5af9df0ac664",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/sample-crisis-communication-app.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/emergency-response/overview.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/emergency-response/use.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/emergency-response/configure-data-reporting.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/emergency-response/deploy-configure.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/emergency-response-data-transfer.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/regional-emergency-response/deploy.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/regional-emergency-response/upgrade.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/regional-emergency-response/overview.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/regional-emergency-response/configure.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/regional-emergency-response/portals-admin-reporting.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/regional-emergency-response/portals-user.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/crisis-financial-impact-tracker/deploy-solution.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/crisis-financial-impact-tracker/overview.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/crisis-financial-impact-tracker/configure-dashboards.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/crisis-financial-impact-tracker/use-mobile-app.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/sample-apps/crisis-financial-impact-tracker/configure-data.md",
+ "redirect_url": "https://learn.microsoft.com",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/transform-infopath.md",
+ "redirect_url": "/power-apps/maker/canvas-apps",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/chatbots.md",
+ "redirect_url": "/microsoft-copilot-studio/authoring-first-bot",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/common/virtual-agent.md",
+ "redirect_url": "/power-apps/maker/canvas-apps/ai-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/power-apps-ideas-train-examples.md",
+ "redirect_url": "../../../power-apps/maker/canvas-apps/power-apps-ideas-transform",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/common/build-ai-plugin-for-copilot.md",
+ "redirect_url": "../../../microsoft-copilot-studio/microsoft-copilot-extend-action-connector",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/common/ai-plugin.md",
+ "redirect_url": "../../../microsoft-copilot-studio/microsoft-copilot-extend-action-connector",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/use-ai-builder.md",
+ "redirect_url": "../ai-builder/overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/user/smartGrid.md",
+ "redirect_url": "../../power-apps/maker/model-driven-apps/power-apps-grid-control",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/user/well-written-input-text-copilot.md",
+ "redirect_url": "/power-apps/",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/common/faq-draft-with-copilot.md",
+ "redirect_url": "/power-apps/",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/canvas-apps/common-performance-issue-resolutions.md",
+ "redirect_url": "../../../power-apps/maker/canvas-apps/create-performant-apps-overview",
+ "redirect_document_id": false
+ },
+ {
+ "source_path": "powerapps-docs/maker/model-driven-apps/build-app-three-steps.md",
+ "redirect_url": "../../../power-apps/maker/model-driven-apps/build-first-model-driven-app",
+ "redirect_document_id": false
+ }
]
-}
+}
\ No newline at end of file
diff --git a/powerapps-docs/cards/card-requirements.md b/powerapps-docs/cards/card-requirements.md
index 95e4ecd4ab..0725a840b4 100644
--- a/powerapps-docs/cards/card-requirements.md
+++ b/powerapps-docs/cards/card-requirements.md
@@ -13,6 +13,8 @@ ms.collection:
# Requirements for cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
This article contains information about requirements for cards to show up and work as expected.
## Environment requirements
diff --git a/powerapps-docs/cards/controls/button-set.md b/powerapps-docs/cards/controls/button-set.md
index 10e680407b..eaa0b7a4e6 100644
--- a/powerapps-docs/cards/controls/button-set.md
+++ b/powerapps-docs/cards/controls/button-set.md
@@ -16,6 +16,8 @@ contributors:
# Button set control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A container for a set of [button](button.md) elements.
The button set control can be used to add buttons in places other than the bottom of the card as well as to group buttons together.
diff --git a/powerapps-docs/cards/controls/button.md b/powerapps-docs/cards/controls/button.md
index eb344db505..9a417822b8 100644
--- a/powerapps-docs/cards/controls/button.md
+++ b/powerapps-docs/cards/controls/button.md
@@ -16,6 +16,8 @@ contributors:
# Button control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A button control that executes Power Fx, opens a URL, shows a screen, or toggles visibility on select. Learn more about [how to use the button control](../make-a-card/ui-elements/use-buttons.md).
Buttons are added under the **actions** section of the tree view at the bottom of the card by default. This button can be placed elsewhere in the card and grouped with other buttons using a [button set control](button-set.md).
diff --git a/powerapps-docs/cards/controls/check-box.md b/powerapps-docs/cards/controls/check-box.md
index 9a84026645..0e243e860a 100644
--- a/powerapps-docs/cards/controls/check-box.md
+++ b/powerapps-docs/cards/controls/check-box.md
@@ -16,6 +16,8 @@ contributors:
# Check box control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A checkbox that lets users choose between two options by selecting or clearing.
## Properties
diff --git a/powerapps-docs/cards/controls/column-set.md b/powerapps-docs/cards/controls/column-set.md
index 44bf027b62..4407650e23 100644
--- a/powerapps-docs/cards/controls/column-set.md
+++ b/powerapps-docs/cards/controls/column-set.md
@@ -16,6 +16,8 @@ contributors:
# Column set control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A collection of columns, each column is a container. These columns allow controls to sit side-by-side.
Column set is useful for showing a row of data. You can add a column for the different UI elements you want within the column set, then drag and drop those elements into the column within the card canvas. You can also [data bind](../make-a-card/ui-elements/data-binding.md) a column set to a collection or data source to repeat the column set for each row, resulting in a list of data.
diff --git a/powerapps-docs/cards/controls/column.md b/powerapps-docs/cards/controls/column.md
index 288cf23f11..f384fcbfde 100644
--- a/powerapps-docs/cards/controls/column.md
+++ b/powerapps-docs/cards/controls/column.md
@@ -16,6 +16,8 @@ contributors:
# Column control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
An individual column which acts as a container for other elements. This column can be arranged side-by-side with other columns using the [column set control](column-set.md).
Add to a column set to create dividers on the page. Empty columns aren't visible. You'll need to put another control (like a text input control) into a column to make it visible. You can drag and drop controls into a column within the card canvas.
diff --git a/powerapps-docs/cards/controls/container.md b/powerapps-docs/cards/controls/container.md
index c694ff74de..aa882aff29 100644
--- a/powerapps-docs/cards/controls/container.md
+++ b/powerapps-docs/cards/controls/container.md
@@ -16,6 +16,8 @@ contributors:
# Container control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A standard container, useable with almost any control.
A container takes on the properties of the first control placed inside it. Only controls of the same type can be added to a container.
diff --git a/powerapps-docs/cards/controls/control-reference.md b/powerapps-docs/cards/controls/control-reference.md
index 15e6f7f131..f8aae27598 100644
--- a/powerapps-docs/cards/controls/control-reference.md
+++ b/powerapps-docs/cards/controls/control-reference.md
@@ -16,6 +16,8 @@ contributors:
# Controls and properties in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Configure the appearance and behavior of a control by setting one of its properties. Each type of control has a different set of properties. Some properties, such as **Height** and **Width**, are common to almost every type of control, but other properties, such as **OnSelect**, are specific to one type of control.
## Controls
diff --git a/powerapps-docs/cards/controls/date-picker.md b/powerapps-docs/cards/controls/date-picker.md
index dca9c27e36..c98cde577e 100644
--- a/powerapps-docs/cards/controls/date-picker.md
+++ b/powerapps-docs/cards/controls/date-picker.md
@@ -16,6 +16,8 @@ contributors:
# Date picker control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Allows the user to enter a date in mm/dd/yyyy format or select a date on the calendar. The value is stored as a date.
## Properties
diff --git a/powerapps-docs/cards/controls/drop-down.md b/powerapps-docs/cards/controls/drop-down.md
index ce086ab547..65030dd833 100644
--- a/powerapps-docs/cards/controls/drop-down.md
+++ b/powerapps-docs/cards/controls/drop-down.md
@@ -16,6 +16,8 @@ contributors:
# Drop down control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A menu that lets users choose one item from an expandable list of items. The default is two choices, but more can be added.
## Properties
diff --git a/powerapps-docs/cards/controls/fact-set.md b/powerapps-docs/cards/controls/fact-set.md
index 7febfb56fe..f71fff28d2 100644
--- a/powerapps-docs/cards/controls/fact-set.md
+++ b/powerapps-docs/cards/controls/fact-set.md
@@ -16,6 +16,8 @@ contributors:
# Fact set control for cards in Power Apps
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Displays a series of facts (i.e. name/value pairs) in a tabular form.
## Properties
diff --git a/powerapps-docs/cards/controls/image-set.md b/powerapps-docs/cards/controls/image-set.md
index 576860b1d7..7bec43585e 100644
--- a/powerapps-docs/cards/controls/image-set.md
+++ b/powerapps-docs/cards/controls/image-set.md
@@ -16,6 +16,8 @@ contributors:
# Image set control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A container of images that acts as a photo gallery.
## Properties
diff --git a/powerapps-docs/cards/controls/image.md b/powerapps-docs/cards/controls/image.md
index 924a8ed432..47dd81eb7a 100644
--- a/powerapps-docs/cards/controls/image.md
+++ b/powerapps-docs/cards/controls/image.md
@@ -16,6 +16,8 @@ contributors:
# Image control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
An image with properties to control what the image looks like. Supports publicly accessible and CORS-compliant URLs as well as base64 encoded images.
Use the [media control](media.md) for video and audio files.
diff --git a/powerapps-docs/cards/controls/media.md b/powerapps-docs/cards/controls/media.md
index 8df169e102..95efcfdb5c 100644
--- a/powerapps-docs/cards/controls/media.md
+++ b/powerapps-docs/cards/controls/media.md
@@ -16,6 +16,8 @@ contributors:
# Media control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Displays a media player for audio or video content. A video or audio file is specified by its Url and MimeType in the Sources tab. The media control supports publicly accessible and CORS-compliant URLs. On Web and Desktop versions of Teams, share links to any OneDrive or SharePoint backed video or audio link are also supported.
Use the [image control](image.md) for pictures.
diff --git a/powerapps-docs/cards/controls/number-input.md b/powerapps-docs/cards/controls/number-input.md
index 73d046c432..3c8cdb164b 100644
--- a/powerapps-docs/cards/controls/number-input.md
+++ b/powerapps-docs/cards/controls/number-input.md
@@ -16,6 +16,8 @@ contributors:
# Number input control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Allows a user to enter a number.
## Properties
diff --git a/powerapps-docs/cards/controls/table.md b/powerapps-docs/cards/controls/table.md
index bd9d705146..e9b2e020be 100644
--- a/powerapps-docs/cards/controls/table.md
+++ b/powerapps-docs/cards/controls/table.md
@@ -15,6 +15,8 @@ contributors:
# Table control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Use the Table control to present tabular data or any structured information that is best laid out in rows and columns. Tables are made up of three separate card elements:
- Tables
- Table Rows
diff --git a/powerapps-docs/cards/controls/text-input.md b/powerapps-docs/cards/controls/text-input.md
index b7c0ab5194..f32df585e2 100644
--- a/powerapps-docs/cards/controls/text-input.md
+++ b/powerapps-docs/cards/controls/text-input.md
@@ -16,6 +16,8 @@ contributors:
# Text input control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A field for users to type text.
## Properties
diff --git a/powerapps-docs/cards/controls/text-label.md b/powerapps-docs/cards/controls/text-label.md
index 3fe4eb29b2..a36558b8c1 100644
--- a/powerapps-docs/cards/controls/text-label.md
+++ b/powerapps-docs/cards/controls/text-label.md
@@ -16,6 +16,8 @@ contributors:
# Text label control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Displays text, allowing control over font sizes, weight, and color.
## Properties
diff --git a/powerapps-docs/cards/controls/time-picker.md b/powerapps-docs/cards/controls/time-picker.md
index 7d9c2ed495..4807b50b97 100644
--- a/powerapps-docs/cards/controls/time-picker.md
+++ b/powerapps-docs/cards/controls/time-picker.md
@@ -16,6 +16,8 @@ contributors:
# Time picker control in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
A field for users to select a time.
## Properties
diff --git a/powerapps-docs/cards/make-a-card/connectors/connector-intro.md b/powerapps-docs/cards/make-a-card/connectors/connector-intro.md
index eeaa61859e..6b9cab97c7 100644
--- a/powerapps-docs/cards/make-a-card/connectors/connector-intro.md
+++ b/powerapps-docs/cards/make-a-card/connectors/connector-intro.md
@@ -12,6 +12,8 @@ ms.collection:
# Add connectors to a card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Connectors allow your card to connect to other apps, data sources, and devices in the cloud. Insert, modify, and remove them in the [card designer](../designer-overview.md). [Learn more about connectors in Power Platform](/connectors/connectors).
## Prerequisites
diff --git a/powerapps-docs/cards/make-a-card/designer-overview.md b/powerapps-docs/cards/make-a-card/designer-overview.md
index e0b6e9ce1d..172d835bd1 100644
--- a/powerapps-docs/cards/make-a-card/designer-overview.md
+++ b/powerapps-docs/cards/make-a-card/designer-overview.md
@@ -13,6 +13,8 @@ ms.collection:
# Card designer overview
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
The Power Apps card designer is the drag-and-drop interface in which you build cards.
1. Sign in to [Power Apps](https://make.powerapps.com) and select your environment.
diff --git a/powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md b/powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md
index 772e6213be..84d3877bfa 100644
--- a/powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md
+++ b/powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md
@@ -13,6 +13,8 @@ ms.collection:
# Power Fx and cards overview
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
[Power Fx](/power-platform/power-fx/overview) is a low-code programming language available across the Power Platform, including in Power Apps cards. Cards can calculate values, perform tasks, and respond to user input using formulas expressed in Power Fx. Power Fx expressions can also update variables and data sources. Expressions can be combined to create complex formulas that can handle advanced business logic.
## Power Fx documentation
diff --git a/powerapps-docs/cards/make-a-card/screens/use-screens.md b/powerapps-docs/cards/make-a-card/screens/use-screens.md
index 3a336bc281..b99a7fdc3d 100644
--- a/powerapps-docs/cards/make-a-card/screens/use-screens.md
+++ b/powerapps-docs/cards/make-a-card/screens/use-screens.md
@@ -12,6 +12,8 @@ ms.collection:
# Add screens to a card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Cards can have multiple screens, each presenting a different interface for a specific scenario or purpose. For example, a polling card might have a screen to collect user responses and a screen to show the current aggregated poll results. Use buttons to let users switch between screens or use Power Fx formulas for more complex scenarios. Insert, modify, and remove them in the [card designer](../designer-overview.md).
## Prerequisites
diff --git a/powerapps-docs/cards/make-a-card/testing/debugging-cards.md b/powerapps-docs/cards/make-a-card/testing/debugging-cards.md
index 4fa333953c..73373bc64d 100644
--- a/powerapps-docs/cards/make-a-card/testing/debugging-cards.md
+++ b/powerapps-docs/cards/make-a-card/testing/debugging-cards.md
@@ -12,6 +12,8 @@ ms.collection:
# Test and debug cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Use the **Play** page to preview your cards before sending them out to users. The **Play** page has tools to test your card and help you debug any issues. Get to the **Play** page in the [card designer](../designer-overview.md).
Card instances that you preview in the **Play** page expire 48 hours after you create the preview. After 48 hours, select **Play** in the card designer to create a fresh instance of the card.
diff --git a/powerapps-docs/cards/make-a-card/ui-elements/controls.md b/powerapps-docs/cards/make-a-card/ui-elements/controls.md
index ba46fd39cf..f7803fd55c 100644
--- a/powerapps-docs/cards/make-a-card/ui-elements/controls.md
+++ b/powerapps-docs/cards/make-a-card/ui-elements/controls.md
@@ -12,6 +12,8 @@ ms.collection:
# Add controls to a card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Controls are the building blocks of your card's interface and functionality. They add text, images, and other elements to create a rich cards experience. Insert, modify, and remove them in the [card designer](../designer-overview.md).
There are three categories of controls that you can add to your card:
diff --git a/powerapps-docs/cards/make-a-card/ui-elements/data-binding.md b/powerapps-docs/cards/make-a-card/ui-elements/data-binding.md
index a7a84f93c4..2a5e54741f 100644
--- a/powerapps-docs/cards/make-a-card/ui-elements/data-binding.md
+++ b/powerapps-docs/cards/make-a-card/ui-elements/data-binding.md
@@ -3,7 +3,7 @@ title: Work with repeating controls in cards
description: Learn how to make controls repeat in a table in cards for Microsoft Power Apps.
keywords: "Card Designer, Power Apps, cards, controls"
ms.date: 09/20/2022
-ms.topic: conceptual
+ms.topic: article
author: iaanw
ms.author: iawilt
ms.reviewer:
@@ -13,6 +13,8 @@ ms.collection:
# Work with repeating controls in cards
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Data binding is used to repeat controls for a table variable using the **Repeat for every** advanced property.
For example, if you have a table named `fruits` bound to the array `["apples", "oranges", "pears"]`, you can add a Text label control and set its **Repeat for every** property to `fruits` and its **Text** property to `ThisItem.Value`. When it's opened, the card shows three text labels with each of the strings in the table.
diff --git a/powerapps-docs/cards/make-a-card/ui-elements/use-buttons.md b/powerapps-docs/cards/make-a-card/ui-elements/use-buttons.md
index d2f427c6b8..36245d6aab 100644
--- a/powerapps-docs/cards/make-a-card/ui-elements/use-buttons.md
+++ b/powerapps-docs/cards/make-a-card/ui-elements/use-buttons.md
@@ -12,6 +12,8 @@ ms.collection:
# Add buttons to a card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Buttons are a type of control that lets users perform actions in cards without entering any input aside from a click. Insert, modify, and remove them in the [card designer](../designer-overview.md).
Buttons can do one of four things:
diff --git a/powerapps-docs/cards/make-a-card/variables/variables.md b/powerapps-docs/cards/make-a-card/variables/variables.md
index 96657be86c..b53cb30f40 100644
--- a/powerapps-docs/cards/make-a-card/variables/variables.md
+++ b/powerapps-docs/cards/make-a-card/variables/variables.md
@@ -13,6 +13,8 @@ ms.collection:
# Add variables to a card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Variables store data for reuse. The data can be of different types, like collection, text, or a number. Variables have unique names, which is how you refer to them in [Power Fx formulas](../../make-a-card/power-fx/intro-to-pfx.md). Insert, modify, and remove them in the [card designer](../designer-overview.md).
The value of a variable can be temporary, reset for each card session, or permanent, shared across all sessions of a specific card instance. Temporary variables are different for each card session, even for a single user, meaning if you have the same card instance sent to you in a chat and a channel, a temporary variable could be different across those two sessions.
diff --git a/powerapps-docs/cards/manage-cards/data-loss-prevention.md b/powerapps-docs/cards/manage-cards/data-loss-prevention.md
index 8b91be806e..a3a24a81a6 100644
--- a/powerapps-docs/cards/manage-cards/data-loss-prevention.md
+++ b/powerapps-docs/cards/manage-cards/data-loss-prevention.md
@@ -13,6 +13,8 @@ ms.collection:
# Manage cards with DLP policies
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
The **Cards for Power Apps** connector is used to automatically send cards through Power Automate. However, there are specific rules enforced by [DLP policies](/power-platform/admin/wp-data-loss-prevention) that dictate which connectors can be used with one another.
Administrators can use DLP policies to determine which connectors can be used in flows that send cards. For example, if both the MSN Weather connector and Cards for Power Apps connector are classified as **Business**, then makers can send daily status cards with the weather.
diff --git a/powerapps-docs/cards/manage-cards/delete-cards.md b/powerapps-docs/cards/manage-cards/delete-cards.md
index a78e3eb958..af196e3390 100644
--- a/powerapps-docs/cards/manage-cards/delete-cards.md
+++ b/powerapps-docs/cards/manage-cards/delete-cards.md
@@ -13,6 +13,8 @@ ms.collection:
# Delete a card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
To delete a card, you need to be the app owner. An admin can't delete a card.
1. Sign in to [Power Apps](https://make.powerapps.com).
diff --git a/powerapps-docs/cards/manage-cards/manage-access.md b/powerapps-docs/cards/manage-cards/manage-access.md
index 868b200fb4..9749c81a00 100644
--- a/powerapps-docs/cards/manage-cards/manage-access.md
+++ b/powerapps-docs/cards/manage-cards/manage-access.md
@@ -13,6 +13,8 @@ ms.collection:
# Manage access
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
This article explains how to manage cards using security roles, and also provides guidance on deleting a record.
## Change who can create cards
diff --git a/powerapps-docs/cards/manage-cards/manage-cards.md b/powerapps-docs/cards/manage-cards/manage-cards.md
index d50321e940..d3366d72d7 100644
--- a/powerapps-docs/cards/manage-cards/manage-cards.md
+++ b/powerapps-docs/cards/manage-cards/manage-cards.md
@@ -13,6 +13,8 @@ ms.collection:
# Manage cards in solutions
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Create a card from within a solution if, for example, you want to deploy the card to a different environment. Solutions can contain not only cards but also customized tables, choices, and other components. You can quickly customize an environment in various ways by creating cards and other components from within a solution, exporting the solution, and then importing it into another environment. For more information, see [Solutions overview](../../maker/data-platform/solutions-overview.md).
diff --git a/powerapps-docs/cards/overview.md b/powerapps-docs/cards/overview.md
index c7af760064..9fbc2f70aa 100644
--- a/powerapps-docs/cards/overview.md
+++ b/powerapps-docs/cards/overview.md
@@ -1,7 +1,7 @@
---
title: Cards for Power Apps overview
description: Learn about cards for Microsoft Power Apps.
-ms.date: 2/22/2024
+ms.date: 3/3/2025
ms.topic: overview
author: iaanw
ms.author: iawilt
@@ -12,6 +12,8 @@ ms.collection:
# Cards for Power Apps overview
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Power Apps cards are micro-apps with enterprise data, workflows, and interactive, lightweight UI elements that other applications can use as content. Because cards are part of the Power Apps ecosystem, they can add business logic through Power Fx and integration with business data through Power Platform connectors. Using cards, you can quickly build and share rich, actionable apps without any coding or IT expertise.
## Get started with cards
diff --git a/powerapps-docs/cards/send-a-card/send-card-in-teams.md b/powerapps-docs/cards/send-a-card/send-card-in-teams.md
index b0a9f5a47a..d59a9afaa2 100644
--- a/powerapps-docs/cards/send-a-card/send-card-in-teams.md
+++ b/powerapps-docs/cards/send-a-card/send-card-in-teams.md
@@ -3,7 +3,7 @@ title: Share a card in Teams
description: Learn how to share a card with your teammates in Teams."
keywords: "Card Designer, Power Apps, cards, share a card, Teams, send a card"
ms.date: 09/20/2022
-ms.topic: article
+ms.topic: how-to
author: iaanw
ms.author: iawilt
ms.reviewer:
@@ -13,6 +13,8 @@ ms.collection:
# Share a card in Teams
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
An easy way to share your cards is to include a link to them in Microsoft Teams. The **Send** button on the **Play** page generates a link that you can copy and then paste into a chat, channel, or meeting. Power Apps must be installed in the Teams chat, channel, or meeting for the card to work and will be installed automatically unless the app is blocked in the organization.
:::image type="content" source="../media/send-a-card/card-in-teams.png" alt-text="Screenshot of a Power Apps card shared in a Teams chat.":::
diff --git a/powerapps-docs/cards/send-a-card/send-card-with-flow.md b/powerapps-docs/cards/send-a-card/send-card-with-flow.md
index 401c7e8af2..9f8f1af9b5 100644
--- a/powerapps-docs/cards/send-a-card/send-card-with-flow.md
+++ b/powerapps-docs/cards/send-a-card/send-card-with-flow.md
@@ -17,6 +17,8 @@ contributors:
# Send a card automatically with a flow
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
Use Power Automate to send cards for Power Apps from a flow. By setting up a flow that is triggered by an event, you can automate the process of sending cards in Teams. For instance, you can create a flow that requests the assigned individual to approve or reject an expense when a new record is added to Dataverse. Alternatively, you can create a flow that sends a daily status update in Teams every morning.
You can use **Send from a flow** option in **Send** menu on the card's **Play** page to launch a Power Automate flow template for sending cards in Teams. You can modify and save this template as a new flow to post your card in Teams chat or channel or send it to a specific Teams user.
@@ -40,7 +42,7 @@ The **Cards for Power Apps** connector is used to create instances of cards to s
## Send a card for Power Apps in Teams chat or channel
-Sending a card in Teams froma flow requires a card instance. To crearte a card instance, use the **Cards for Power Apps** connector actions. The **Create card instance** action has `Card` dynamic content that can be used with the **Teams** connector **Post card in a chat or channel** action.
+Sending a card in Teams from a flow requires a card instance. To create a card instance, use the **Cards for Power Apps** connector actions. The **Create card instance** action has `Card` dynamic content that can be used with the **Teams** connector **Post card in a chat or channel** action.
1. Create or modify an existing flow, or use **Send** > **Send from a flow** on cards for Power Apps **Play** page to start with a template.
1. Make sure the flow has a trigger. In the screenshot below, the trigger is when a new account record is created.
diff --git a/powerapps-docs/cards/tutorials/dataverse-card.md b/powerapps-docs/cards/tutorials/dataverse-card.md
index de5e8c69dc..f894e40e7d 100644
--- a/powerapps-docs/cards/tutorials/dataverse-card.md
+++ b/powerapps-docs/cards/tutorials/dataverse-card.md
@@ -3,7 +3,7 @@ title: Create a card with data from Dataverse
description: Learn how to use Dataverse connectors in a card.
keywords: "Card Designer, Power Apps, cards, tutorial, Dataverse, connectors"
ms.date: 09/20/2022
-ms.topic: article
+ms.topic: how-to
author: iaanw
ms.author: iawilt
ms.reviewer:
@@ -13,6 +13,8 @@ ms.collection:
# Create a card with data from Dataverse (preview)
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
In this tutorial, you'll create a card that uses the Microsoft Dataverse connector to display and update information about an account. You'll use the [card designer](../make-a-card/designer-overview.md), [variables](../make-a-card/variables/variables.md), [connectors](../make-a-card/connectors/connector-intro.md), and more complex [Power Fx expressions](../make-a-card/power-fx/intro-to-pfx.md).
We'll assume that you've honed your Power Apps card skills in the [Hello World tutorial](hello-world-card.md) and the [shopping list tutorial](simple-shopping-list.md) and are familiar with using the card designer. If you haven't explored those tutorials yet, we recommend that you do that first, and then return to this tutorial.
diff --git a/powerapps-docs/cards/tutorials/hello-world-card.md b/powerapps-docs/cards/tutorials/hello-world-card.md
index 9010c52d77..8aec15d492 100644
--- a/powerapps-docs/cards/tutorials/hello-world-card.md
+++ b/powerapps-docs/cards/tutorials/hello-world-card.md
@@ -12,6 +12,8 @@ ms.collection:
# Create a simple card (preview)
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
In this article, you create a card that asks the user to enter their name, and then shows the name in the title of the card. You use the [card designer](../make-a-card/designer-overview.md), [variables](../make-a-card/variables/variables.md), and [Power Fx](../make-a-card/power-fx/intro-to-pfx.md).
## Prerequisites
diff --git a/powerapps-docs/cards/tutorials/simple-shopping-list.md b/powerapps-docs/cards/tutorials/simple-shopping-list.md
index ac6b9bbe3e..210d113516 100644
--- a/powerapps-docs/cards/tutorials/simple-shopping-list.md
+++ b/powerapps-docs/cards/tutorials/simple-shopping-list.md
@@ -12,6 +12,8 @@ ms.collection:
# Create a shopping list card
+[!INCLUDE[cards-deprecation-banner](~/includes/cards-deprecation-notice.md)]
+
In this tutorial, you'll create a card that displays a shopping list and lets you add items. You'll use the [card designer](../make-a-card/designer-overview.md), [variables](../make-a-card/variables/variables.md), and [Power Fx](../make-a-card/power-fx/intro-to-pfx.md).
At the end of the tutorial, your shopping list card should look like the following example:
diff --git a/powerapps-docs/chatbots.md b/powerapps-docs/chatbots.md
deleted file mode 100644
index 137f0a12f8..0000000000
--- a/powerapps-docs/chatbots.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Create chatbots from Power Apps | Microsoft Docs
-description: Provides information about how to create chatbots from Power Apps.
-author: iaanw
-ms.subservice: common
-ms.topic: conceptual
-ms.custom:
-ms.date: 06/26/2020
-ms.author: iawilt
-ms.reviewer: mvakoc
-contributors:
- - iaanw
----
-# Create chatbots from Power Apps
-
-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).
-
-
-
-You can create and manage your chatbots using the **Chatbots** option in the left navigation pane.
-
-- To create a chatbot, select **Chatbots**, then **Create**, and then select **New chatbot**. This will take you directly to the Power Virtual Agents portal where you can create your chatbot. For more information, see [Create a bot in Power Virtual Agents](/power-virtual-agents/authoring-first-bot)
-
-- After you have chatbots in your environment, you'll be able to view them by selecting **Chatbots** and then **List**. You can navigate directly to the Power Virtual Agents portal to update your bot or view analytics.
-
-More information: [Power Virtual Agents docs](/power-virtual-agents)
-
-
-[!INCLUDE[footer-include](includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md b/powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md
index e21d133228..5d24a35599 100644
--- a/powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md
+++ b/powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md
@@ -1,11 +1,11 @@
---
title: Add code components to a column or table in model-driven apps | Microsoft Docs
description: Learn how to add code components to a column or table.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
diff --git a/powerapps-docs/developer/component-framework/bring-intelligence-using-agent-apis.md b/powerapps-docs/developer/component-framework/bring-intelligence-using-agent-apis.md
new file mode 100644
index 0000000000..27b9c5aabe
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/bring-intelligence-using-agent-apis.md
@@ -0,0 +1,49 @@
+---
+title: "Bring intelligence into your components using Agent APIs (preview)"
+description: "Learn about how you can integrate Copilot Studio topics into your custom components using Agent APIs"
+author: adrianorth
+ms.author: aorth
+ms.date: 07/07/2025
+ms.reviewer: jdaly
+ms.topic: conceptual
+ms.subservice: pcf
+search.audienceType:
+ - developer
+contributors:
+ - JimDaly
+---
+
+# Bring intelligence into your component using Agent APIs (preview)
+
+[!INCLUDE [preview-note-pp](~/../shared-content/shared/preview-includes/preview-note-pp.md)]
+
+Agent APIs are a set of interfaces introduced in Microsoft Power Apps that allow components to interact with topics created in Microsoft Copilot Studio. These APIs are available in two forms:
+
+- `Context.Copilot` methods used for PCF controls. This is the subject of this article.
+- [Xrm.Copilot namespace used for client scripts in model-driven apps.](../model-driven-apps/clientapi/bring-intelligence-using-agent-apis.md)
+
+These APIs are designed to enhance integration with Microsoft Copilot Studio, enabling more intelligent and responsive app experiences. The APIs use a single Copilot Studio agent that is either:
+- Interactive agent selected in the model app designer of custom apps. See more at [Working with an interactive agent](../../maker/model-driven-apps/add-agents-to-app.md#working-with-an-interactive-agent).
+- Model app containing lead or opportunity table, which implicitly uses the "Copilot in Dynamics 365 Sales" agent.
+
+|API|Description|
+|---------|---------|
+|[copilot.executeEvent](reference/copilot/executeevent.md)|[!INCLUDE [executeevent-description](reference/copilot/includes/executeevent-description.md)]|
+|[copilot.executePrompt](reference/copilot/executeprompt.md)|[!INCLUDE [executeprompt-description](reference/copilot/includes/executeprompt-description.md)]|
+
+## Accessibility
+
+When creating a code component, ensure the following best practices in [code component accessibility checks](code-components-best-practices.md#check-accessibility) are followed to have an accessible experience.
+
+### Related articles
+
+[FAQ for Agent APIs and Agent Response component](../../maker/common/faq-agent-api-component.md)
+[Copilot](reference/copilot.md)
+[executeEvent](reference/copilot/executeevent.md)
+[executePrompt](reference/copilot/executeprompt.md)
+[Working with an interactive agent](../../maker/model-driven-apps/add-agents-to-app.md#working-with-an-interactive-agent)
+[Power Apps component framework overview](overview.md)
+[Create your first code component](implementing-controls-using-typescript.md)
+[Learn Power Apps component framework](/training/paths/use-power-apps-component-framework)
+[Xrm.Copilot (Client API reference)](../model-driven-apps/clientapi/reference/xrm-copilot.md)
+[Add agent response with the form designer (preview)](../../maker/model-driven-apps/form-designer-add-configure-agent-response.md)
diff --git a/powerapps-docs/developer/component-framework/code-components-alm.md b/powerapps-docs/developer/component-framework/code-components-alm.md
index 0d27a2d2fb..caabc0c74d 100644
--- a/powerapps-docs/developer/component-framework/code-components-alm.md
+++ b/powerapps-docs/developer/component-framework/code-components-alm.md
@@ -1,11 +1,11 @@
---
title: "Code components application lifecycle management | MicrosoftDocs"
description: "Learn about the considerations and strategies for working with specific aspects of ALM from the perspective of code components in Microsoft Dataverse."
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
diff --git a/powerapps-docs/developer/component-framework/code-components-best-practices.md b/powerapps-docs/developer/component-framework/code-components-best-practices.md
index 45373bb078..4e2c2f0342 100644
--- a/powerapps-docs/developer/component-framework/code-components-best-practices.md
+++ b/powerapps-docs/developer/component-framework/code-components-best-practices.md
@@ -1,11 +1,11 @@
---
title: "Best practices for code components | Microsoft Docs"
description: "Learn best practices and get guidance on how to use code components created using Power Apps component framework."
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 03/25/2024
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: best-practice
ms.subservice: pcf
contributors:
- JimDaly
diff --git a/powerapps-docs/developer/component-framework/code-components-model-driven-apps.md b/powerapps-docs/developer/component-framework/code-components-model-driven-apps.md
index 5d7243b3c1..0f56baa618 100644
--- a/powerapps-docs/developer/component-framework/code-components-model-driven-apps.md
+++ b/powerapps-docs/developer/component-framework/code-components-model-driven-apps.md
@@ -1,8 +1,8 @@
---
title: Code components for model-driven apps | Microsoft Docs
description: Learn how to create code components using Power Apps component framework for model-driven apps
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: article
diff --git a/powerapps-docs/developer/component-framework/community-resources.md b/powerapps-docs/developer/component-framework/community-resources.md
index 4f9b991a05..64f6f6e252 100644
--- a/powerapps-docs/developer/component-framework/community-resources.md
+++ b/powerapps-docs/developer/component-framework/community-resources.md
@@ -1,8 +1,8 @@
---
title: Community resources (Power Apps Component Framework) | Microsoft Docs
description: Access to community resources
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: article
diff --git a/powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md b/powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md
index 5a684bf485..31e103254b 100644
--- a/powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md
+++ b/powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md
@@ -2,11 +2,11 @@
title: Code components for canvas apps | Microsoft Docs
description: Learn how to create code components using Power Apps component framework for canvas apps.
keywords:
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+author: anuitz
+ms.author: anuitz
+ms.date: 07/01/2025
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
@@ -14,7 +14,7 @@ contributors:
# Code components for canvas apps
-Professional developers can use Power Apps component framework to create code components that can be used in their canvas apps. More information: [Power Apps component framework overview](overview.md)
+Professional developers can use Power Apps component framework to create code components that can be used in their canvas apps. More information: [Power Apps component framework overview](overview.md).
App makers can use Power Apps component framework to create, import, and add code components to canvas apps by using [Microsoft Power Platform CLI](get-powerapps-cli.md). Certain APIs might not be available in canvas apps. We recommend that you check each API to determine where it's available.
@@ -23,7 +23,7 @@ App makers can use Power Apps component framework to create, import, and add cod
> [!WARNING]
> Code components contain code that may not be generated by Microsoft and can potentially access security tokens and data when rendered in Power Apps Studio. When adding code components to a canvas app, make sure that the code component solutions are from a trusted source. This vulnerability does not exist when playing the canvas app.
-When you open a canvas app that contains code components in Power Apps Studio, a warning message about potentially unsafe code appears. Code components in the Power Apps Studio environment have access to security tokens; hence only components from trusted sources should be opened. Administrators and system customizers should review and validate all code components before importing those components in an environment and making them available for makers to use in their apps. The `Default` publisher is shown when you import code components by using an unmanaged solution or when you have used [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push) to install your code component.
+When you open a canvas app that contains code components in Power Apps Studio, a warning message about potentially unsafe code appears. Code components in the Power Apps Studio environment have access to security tokens; hence only components from trusted sources should be opened. Administrators and system customizers should review and validate all code components before importing those components in an environment and making them available for makers to use in their apps. The `Default` publisher is shown when you import code components by using an unmanaged solution or when you have used [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push) to install your code component.

@@ -39,13 +39,13 @@ To add code components to an app, you need to enable the Power Apps component fr
1. Sign in to [Power Apps](https://powerapps.microsoft.com/).
2. Select **Settings** , and then select **Admin Center**.
-
+
> [!div class="mx-imgBorder"]
- > 
+ > 
3. On the left pane, select **Environments**, select the environment where you want to enable this feature, and then select **Settings**.
-4. Expand **Product**, and select **Features**.
+4. Expand **Product**, and select **Features**.
5. From the list of available features, turn on **Power Apps component framework for canvas apps**, and then select **Save**.
@@ -56,6 +56,8 @@ To add code components to an app, you need to enable the Power Apps component fr
After you enable the Power Apps component framework feature in your environment, you can start implementing the logic for code components. For a step-by-step tutorial, go to [Create your first code component](implementing-controls-using-typescript.md).
+We recommend that you check the [limitations](limitations.md) of code components in canvas apps before starting implementation.
+
## Add components to a canvas app
1. Go to Power Apps Studio.
@@ -65,8 +67,8 @@ After you enable the Power Apps component framework feature in your environment,
> [!IMPORTANT]
> Make sure the solution .zip file containing the code components has already been [imported](../../maker/data-platform/import-update-export-solutions.md) into Microsoft Dataverse before you proceed to the next step.
-3. On the left pane, select **Add** (**+**), and then select **Get more components**.
-
+3. On the left pane, select **Add** (**+**), and then select **Get more components**.
+
> [!div class="mx-imgBorder"]
> 
@@ -82,26 +84,26 @@ After you enable the Power Apps component framework feature in your environment,
> [!NOTE]
> You can also add components by selecting **Insert** > **Custom** > **Import component**. This option will be removed in a future release, so we suggest using the flow described above.
- >
+ >
-On the **Properties** tab, you'll notice the code component properties are displayed.
+On the **Properties** tab, you'll notice the code component properties are displayed.
> [!div class="mx-imgBorder"]
> 
> [!NOTE]
-> Existing code components can be re-imported by updating the code component's manifest version if you want the properties to be available in the default **Properties** tab. As before, the properties will continue to be available on the **Advanced** properties tab.
+> Existing code components can be re-imported by updating the code component's manifest version if you want the properties to be available in the default **Properties** tab. As before, the properties will continue to be available on the **Advanced** properties tab.
## Delete a code component from a canvas app
-1. Open the app where you've added the code component.
-1. On the left pane, select **Tree view**, and then select the screen where you've added the code component.
+1. Open the app where you've added the code component.
+1. On the left pane, select **Tree view**, and then select the screen where you've added the code component.
1. Next to the component, select **More** (**...**), and then select **Delete**.
> [!div class="mx-imgBorder"]
> 
-1. Save the app to see the changes.
+1. Save the app to see the changes.
## Update existing code components
@@ -116,5 +118,4 @@ Whenever you update the code components and want to see the runtime changes, you
[Create your first code component](implementing-controls-using-typescript.md)
[Learn Power Apps component framework](/training/paths/use-power-apps-component-framework)
-
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md b/powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md
index 14aa065548..b4d8528270 100644
--- a/powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md
+++ b/powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md
@@ -2,11 +2,11 @@
title: Create and build a code component| Microsoft Docs
description: Start creating a component using the Power Apps component framework tooling.
keywords: Power Apps component framework, code components, Component Framework
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 01/27/2023
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
diff --git a/powerapps-docs/developer/component-framework/custom-controls-overview.md b/powerapps-docs/developer/component-framework/custom-controls-overview.md
index 2e517a1c20..fea14d8d90 100644
--- a/powerapps-docs/developer/component-framework/custom-controls-overview.md
+++ b/powerapps-docs/developer/component-framework/custom-controls-overview.md
@@ -1,11 +1,11 @@
---
title: "Code components | MicrosoftDocs"
description: "What are code components? Use the Power Apps component framework to create code components to provide enhanced user experiences for users to view and work with data in model-driven apps, canvas apps, and Power Pages."
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 02/10/2023
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
@@ -108,7 +108,7 @@ You can define additional resource files in the manifest to include:
More information: [resources element](manifest-schema-reference/resources.md)
-### Related topics
+### Related articles
[Create and build a code component](create-custom-controls-using-pcf.md)
diff --git a/powerapps-docs/developer/component-framework/customize-editable-grid-control.md b/powerapps-docs/developer/component-framework/customize-editable-grid-control.md
index d78a771c48..13a42e5817 100644
--- a/powerapps-docs/developer/component-framework/customize-editable-grid-control.md
+++ b/powerapps-docs/developer/component-framework/customize-editable-grid-control.md
@@ -2,11 +2,11 @@
title: "Customize the editable grid control | Microsoft Docs"
description: "Learn how you can customize the editable grid control."
keywords: "Component Framework, code components, Power Apps controls"
-ms.author: jasongre
-author: jasongre
+author: clromano
+ms.author: clromano
ms.date: 07/25/2022
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
@@ -15,19 +15,19 @@ contributors:
# Customize the editable grid control
-The [Power Apps grid control](../../maker/model-driven-apps/the-power-apps-grid-control.md) uses modern Microsoft Fluent controls to allow users to see and edit values in grid cells. Scenarios may exist that have special needs requiring modification of the out-of-the-box visuals and user interactions. To facilitate this, the Power Apps grid control provides extensibility APIs that allow the grid interface to be customized. Using these APIs, makers can implement a grid customizer control (code component) to provide custom cell renderer and editor components to the grid.
+The [Power Apps grid control](../../maker/model-driven-apps/the-power-apps-grid-control.md) uses modern Microsoft Fluent controls to allow users to see and edit values in grid cells. Scenarios might exist that have special requirements requiring modification of the out-of-the-box visuals and user interactions. To facilitate these scenarios, the Power Apps grid control provides extensibility APIs that allow the grid interface to be customized. Makers can use these APIs to implement a grid customizer control (code component) to provide custom cell renderer and editor components to the grid.
:::image type="content" source="../../maker/model-driven-apps/media/power-apps-grid-custom-renderers.png" alt-text="Custom cell renderers for the Power Apps grid control" lightbox="../../maker/model-driven-apps/media/power-apps-grid-custom-renderers.png":::
## Grid customizer control
-A grid customizer is a PCF control implementing the Power Apps grid control customizer interface. This interface allows you to define the React element that will be rendered when a grid cell is in read-only mode (the cell renderer) or in edit mode (the cell editor). Multiple grid customizer controls can exist in an environment, but each grid can only have a single grid customizer control assigned. You may decide that a separate customizer control is needed for each grid you want to modify, or you may choose to reuse the same customizer control for multiple grids.
+A grid customizer is a PCF control implementing the Power Apps grid control customizer interface. This interface allows you to define the React element that is rendered when a grid cell is in read-only mode (the cell renderer) or in edit mode (the cell editor). Multiple grid customizer controls can exist in an environment, but each grid can only have a single grid customizer control assigned. You might decide that a separate customizer control is needed for each grid you want to modify, or you might choose to reuse the same customizer control for multiple grids.
### Implementing a grid customizer control
To implement a grid customizer control, you first need to be familiar with the steps to [Create and build a code component](create-custom-controls-using-pcf.md) and you must have access to the template control.
-The template control is included in the [PowerApps-Samples](https://github.com/microsoft/PowerApps-Samples) GitHub repository. You will need to clone or download the repo to access the files located here: [PowerApps-Samples/component-framework/resources/GridCustomizerControlTemplate](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/resources/GridCustomizerControlTemplate)
+The template control is included in the [PowerApps-Samples](https://github.com/microsoft/PowerApps-Samples) GitHub repository. You need to clone or download the repo to access the files located here: [PowerApps-Samples/component-framework/resources/GridCustomizerControlTemplate](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/resources/GridCustomizerControlTemplate)
1. Open the `GridCustomizerControlTemplate` folder using Visual Studio Code.
1. In a terminal window, run `npm install`.
@@ -61,14 +61,14 @@ The template control is included in the [PowerApps-Samples](https://github.com/m
```
> [!NOTE]
- > If the function returns null or undefined, then the grid will use the internal renderer/editor for the targeted cells.
+ > If the function returns null or undefined, then the grid uses the internal renderer/editor for the targeted cells.
1. After defining your custom cell renderers and editors, **package** the grid customizer control and **import** it to your Power Apps environment. Alternatively, you can use the [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push) command.
1. After publishing the grid customizer control, open the **Customize the system** panel from the **Settings > Customizations** menu.
:::image type="content" source="media/customize-editable-grid-settings-customize-system.png" alt-text="Open the Customize the system panel from the Settings > Customizations menu":::
-1. From the entities node, select an entity that your customizer control will target (e.g. Account).
+1. From the entities node, select an entity that your customizer control targets (for example, Account).
1. From the right panel, select the **Controls** tab.
:::image type="content" source="media/customize-editable-grid-control-tab.png" alt-text="The grid control tab":::
@@ -89,13 +89,13 @@ The template control is included in the [PowerApps-Samples](https://github.com/m
## Best practices
-- Cell renderers and editors are user interface components. Do not use them to mutate data or metadata of the grid.
+- Cell renderers and editors are user interface components. Don't use them to mutate data or metadata of the grid.
- The customizer controls should be lightweight and fast so as to not affect overall grid performance.
- To maintain the design consistency, follow [Fluent design principles](https://www.microsoft.com/design/fluent/#/) and use [Fluent controls](https://developer.microsoft.com/en-us/fluentui#/controls/web) in your customizers.
- Make sure your custom renderer or editor is accessible.
-- The customizer function should be pure since the grid will call it multiple times to get customized elements and will expect the return value to be consistent.
-- The grid may dispose a customizer element at any time and call to get a new one at any time. Make sure to dispose of any internal state on unmount to prevent memory leaks.
-- Do not use renderers to override the values in the grid since the new values will not be used by the server to do filtering or sorting.
+- The customizer function should be pure since the grid calls it multiple times to get customized elements and expects the return value to be consistent.
+- The grid might dispose a customizer element at any time and call to get a new one at any time. Make sure to dispose of any internal state on unmount to prevent memory leaks.
+- Don't use renderers to override the values in the grid since the server doesn't use the new values to do filtering or sorting.
## Example
diff --git a/powerapps-docs/developer/component-framework/debugging-custom-controls.md b/powerapps-docs/developer/component-framework/debugging-custom-controls.md
index 99c23783a4..2cdd5bc2d5 100644
--- a/powerapps-docs/developer/component-framework/debugging-custom-controls.md
+++ b/powerapps-docs/developer/component-framework/debugging-custom-controls.md
@@ -1,11 +1,11 @@
---
title: "Debug code components | MicrosoftDocs"
description: "How to debug a code component using Fiddler and Native debugging"
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
@@ -14,7 +14,7 @@ contributors:
# Debug code components
-This article provides information on how to debug your code component logic while it is being developed. Writing unit tests for your code is considered good practice so that the logic can be tested independently from the Power Apps component framework runtime.
+This article provides information on how to debug your code component logic while it's being developed. Writing unit tests for your code is considered good practice so that the logic can be tested independently from the Power Apps component framework runtime.
This article shows how to debug your code components using the test harness and after deploying to Microsoft Dataverse:
@@ -35,12 +35,12 @@ This article shows how to debug your code components using the test harness and
## Debugging using the browser test harness
-While you are implementing the code component logic, using `npm start` or `npm start watch` builds the code component and open the local test harness in a new browser window. This test harness is part of Microsoft Power Platform CLI and hence is the same irrespective of if you plan to use your code component in model-driven apps, canvas apps, or portals. More information: [Create your first component](implementing-controls-using-typescript.md).
+While you're implementing the code component logic, using `npm start` or `npm start watch` builds the code component and open the local test harness in a new browser window. This test harness is part of Microsoft Power Platform CLI and hence is the same irrespective of if you plan to use your code component in model-driven apps, canvas apps, or portals. More information: [Create your first component](implementing-controls-using-typescript.md).
> [!NOTE]
> Before you can use `npm start` you need to check if npm is installed in your machine.
-The following image shows what Visual Studio Code will look like when you use the `npm start watch` for the `DataSetGrid` sample:
+The following image shows what Visual Studio Code looks like when you use the `npm start watch` for the `DataSetGrid` sample:
> [!div class="mx-imgBorder"]
> 
@@ -51,12 +51,12 @@ Launching the test harness in `watch` mode enables you to quickly see the change
1. Imported modules in `index.ts` (excluding node_modules).
1. All of the resources listed in the `ControlManifest.Input.xml` file, for example, `css/DataSetGrid.css` or `strings/DataSetGrid.1033.resx`
-If you make changes to any of these files, you will see a `Change detected` message and the browser reloads with the updated code.
+If you make changes to any of these files, you'll see a `Change detected` message and the browser reloads with the updated code.
> [!div class="mx-imgBorder"]
> 
-The following image shows the test harness once it is opened in a new browser window:
+The following image shows the test harness once it's opened in a new browser window:
> [!div class="mx-imgBorder"]
> 
@@ -65,8 +65,8 @@ As the image above shows, the browser window opens to display four areas. The co
- **Context Inputs** is shown for all code component types:
- - **Form Factor**: Provides a way to specify the form factor and test the code component with each form factor (web, tablet, phone). This is helpful when the code component changes its layout depending on where the component is loaded. You can detect the form factor in the code using [`context.client.getFormFactor()`](reference\client\getformfactor.md).
- - **Component Container Width & Height**: Initially, the width and height are empty. This places your code component inside a container `div` that has no width or height CSS style set. If you provide a width or height, the container `div` will have its dimensions constrained so that you can see how your code component will adapt to the space available. You will need to carefully test your code components behavior inside Power Apps once deployed since the exact behavior will be different to that of the test harness. Additionally, your component will need to make a call to `context.mode.trackContainerResize(true)` if it wants to receive `context.mode.allocatedHeight` `context.mode.allocatedWidth` in the `updateView` method, however the test harness will always provide the height and width irrespective of this call.
+ - **Form Factor**: Provides a way to specify the form factor and test the code component with each form factor (web, tablet, phone). Form factor is helpful when the code component changes its layout depending on where the component is loaded. You can detect the form factor in the code using [`context.client.getFormFactor()`](reference\client\getformfactor.md).
+ - **Component Container Width & Height**: Initially, the width and height are empty. This places your code component inside a container `div` that has no width or height CSS style set. If you provide a width or height, the container `div` has its dimensions constrained so that you can see how your code component adapts to the space available. You need to carefully test your code components behavior inside Power Apps once deployed since the exact behavior is different to that of the test harness. Additionally, your component needs to make a call to `context.mode.trackContainerResize(true)` if it wants to receive `context.mode.allocatedHeight` `context.mode.allocatedWidth` in the `updateView` method, however the test harness always provides the height and width irrespective of this call.
More information: [trackContainerResize](reference\mode\trackcontainerresize.md).
> [!NOTE]
@@ -84,17 +84,17 @@ As the image above shows, the browser window opens to display four areas. The co
### Test code components with mock data
-- For components with [`property`](reference\property.md) elements in the `ControlManifest.Input.xml`, the **Data Inputs** section will show an input box for each value.
+- For components with [`property`](reference\property.md) elements in the `ControlManifest.Input.xml`, the **Data Inputs** section shows an input box for each value.
> [!div class="mx-imgBorder"]
> 
-- For _dataset_ type components, you can load a CSV file with test data for each [data-set](manifest-schema-reference\data-set.md) element. You manually create or export in .csv format directly from your environment. After loading a CSV file, you can bind each [property-set](manifest-schema-reference\property-set.md) defined in the `ControlManifest.Input.xml` to a column in the CSV file. This is done by picking the column for each property as shown below:
+- For _dataset_ type components, you can load a CSV file with test data for each [data-set](manifest-schema-reference\data-set.md) element. You manually create or export in .csv format directly from your environment. After loading a CSV file, you can bind each [property-set](manifest-schema-reference\property-set.md) defined in the `ControlManifest.Input.xml` to a column in the CSV file. The following screenshot shows how this binding is done by picking the column for each property:
> [!div class="mx-imgBorder"]
> 
-- If you do not have any properties defined in the `ControlManifest.Input.xml` file, then all the columns get automatically loaded into the test harness. For each column in the source CSV, you can then assign the data type to be used provided to the code component as shown below:
+- If you don't have any properties defined in the `ControlManifest.Input.xml` file, then all the columns get automatically loaded into the test harness. The following screenshot shows how you can assign the data type to the code component for each column in the source CSV:
> [!div class="mx-imgBorder"]
> 
@@ -104,28 +104,28 @@ As the image above shows, the browser window opens to display four areas. The co
### Common limitations when using the test harness
-While the test harness is suitable for testing simple code components, the following scenarios may mean that the test harness cannot be used to test a more complex code component:
+While the test harness is suitable for testing simple code components, the following scenarios might mean that the test harness can't be used to test a more complex code component:
-1. The [updatedProperties](reference\updatedproperties.md) array is not populated when properties are changed via the test harness **Data Inputs** section.
-2. Using features listed in the `feature-usage` section of the `ControlManifest.Input.xml`. For example, calling the `context.WebApi.*` methods will throw an exception from within the test harness.
-3. Use of the [paging](reference/paging.md), [sorting](reference/sortstatus.md), and [filtering](reference/filtering.md) APIs on datasets will throw an exception from within the test harness.
-4. Use of complex datatype bindings that provide additional metadata such as choices and lookups. For choice columns, the test harness will give you three simple choices with minimal metadata.
-5. Model-driven apps specifics such as field level security, read-only behavior, dataset selection API, and integration with the model-driven apps command bar.
-6. Other context APIs such as [Navigation](reference/navigation.md) and [Utility](reference/utility.md) methods.
+1. The [updatedProperties](reference\updatedproperties.md) array isn't populated when properties are changed via the test harness **Data Inputs** section.
+1. Using features listed in the `feature-usage` section of the `ControlManifest.Input.xml`. For example, calling the `context.WebApi.*` methods throw an exception from within the test harness.
+1. Use of the [paging](reference/paging.md), [sorting](reference/sortstatus.md), and [filtering](reference/filtering.md) APIs on datasets throw an exception from within the test harness.
+1. Use of complex datatype bindings that provide more metadata such as choices and lookups. For choice columns, the test harness gives you three simple choices with minimal metadata.
+1. Model-driven apps specifics such as field level security, read-only behavior, dataset selection API, and integration with the model-driven apps command bar.
+1. Other context APIs such as [Navigation](reference/navigation.md) and [Utility](reference/utility.md) methods.
-To test these scenarios, you will need to first deploy your code component and test using the technique described in [Debugging after deploying to Dataverse using Fiddler](#debugging-after-deploying-into-microsoft-dataverse)
+To test these scenarios, you'll need to first deploy your code component and test using the technique described in [Debugging after deploying to Dataverse using Fiddler](#debugging-after-deploying-into-microsoft-dataverse)
## Using browser developer tools to debug your code component
-Modern browsers have a built-in set of developer tools that allow you to inspect the HTML, CSS, and JavaScript loaded on the current page. You can access these developer tools using the keyboard shortcut `Ctrl`+`Shift`+`I`. Using the `F12` key is also a common keyboard shortcut to open the developer tools however this will not work inside Power Apps Studio due to it being already used for the **Download App** keyboard shortcut.
+Modern browsers have a built-in set of developer tools that allow you to inspect the HTML, CSS, and JavaScript loaded on the current page. You can access these developer tools using the keyboard shortcut `Ctrl`+`Shift`+`I`. Using the `F12` key is also a common keyboard shortcut to open the developer tools however this shortcut doesn't work inside Power Apps Studio due to it being already used for the **Download App** keyboard shortcut.
### Bundling using webpack
-When writing code components using TypeScript, your code will likely look different from the JavaScript that is emitted into the bundled code component output. When you run `npm start` or `npm start watch`, the `pcf-scripts` module (added to the `packages.json` by running [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init)) uses web pack to build multiple TypeScript files into a single `bundle.js` inside the `out` folder. This folder will also contain any other resources (for example, `html`/`css`) that are referenced by your `ControlManifest.Input.xml` including the manifest itself, but named instead as just `ControlManifest.xml`.
+When you write code components using TypeScript, your code probably looks different from the JavaScript that is emitted into the bundled code component output. When you run `npm start` or `npm start watch`, the `pcf-scripts` module (added to the `packages.json` by running [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init)) uses web pack to build multiple TypeScript files into a single `bundle.js` inside the `out` folder. This folder also contains any other resources (for example, `html`/`css`) referenced by your `ControlManifest.Input.xml` including the manifest itself, but named instead as just `ControlManifest.xml`.
-When you use modern TypeScript language features such as import/export or async/await that are not supported by the targeted standard of JavaScript (e.g. ES5), the build process will transpile the TypeScript into JavaScript without using these language features. The source maps that are output as part of the development build, provide the information to the developer tools so that breakpoint locations in your TypeScript can be mapped to the corresponding line of JavaScript. Equally, when an exception occurs or you step through the code, you can see the original TypeScript line rather than the underlying transpiled JavaScript.
+When you use modern TypeScript language features such as import/export or async/await that the targeted standard of JavaScript (for example, ES5), doesn't support, the build process transpiles the TypeScript into JavaScript without using these language features. The source maps that are output as part of the development build, provide the information to the developer tools so that breakpoint locations in your TypeScript can be mapped to the corresponding line of JavaScript. Equally, when an exception occurs or you step through the code, you can see the original TypeScript line rather than the underlying transpiled JavaScript.
-Another feature of bundling is that when you use `npm install` to include an external module, the build process will add the required module into your code component's `bundle.js` using the contents of the associated `node_modules` directory. For this reason, any external modules used must be packaged in such a way that they can be bundled. More information: [Best practices: Module imports](code-components-best-practices.md#module-imports).
+Another feature of bundling is that when you use `npm install` to include an external module, the build process adds the required module into your code component's `bundle.js` using the contents of the associated `node_modules` directory. For this reason, any external modules used must be packaged in such a way that they can be bundled. More information: [Best practices: Module imports](code-components-best-practices.md#module-imports).
> [!NOTE]
> The source maps will only be output when you run the build-in development mode and will result in a much larger file than your production build. For this reason, it is not recommended to deploy your code component after building for development purposes. More information: [Application Lifecycle Management (ALM)](code-components-alm.md).
@@ -137,39 +137,33 @@ This section describes how to debug your code component inside the Microsoft Edg
1. Load your code component into a browser session using either:
1. The test harness using `npm start watch`.
- 2. A local development build of your code component loaded into a model-driven, canvas app, or portal browser session. You do not need to deploy a development build of your code component to Dataverse server, but instead, you can use Fiddler AutoResponders as described in [Debugging after deployment into Microsoft Dataverse using Fiddler](#debugging-after-deploying-into-microsoft-dataverse) below.
+ 1. A local development build of your code component loaded into a model-driven, canvas app, or portal browser session. You don't need to deploy a development build of your code component to Dataverse server, but instead, you can use Fiddler Auto Responders as described in [Debugging after deployment into Microsoft Dataverse using Fiddler](#debugging-after-deploying-into-microsoft-dataverse).
-2. Select `Ctrl` + `Shift` + `I` to open the developer tools.
-
-3. Select the **Sources** tab inside the developer tools panel.
-
-4. Use `Ctrl` + `P` to show the **Open File** command pallet. You can also select **Open File** from the **ellipsis** menu.
-
-5. Enter the name of your control (which will be the name of the control you used in [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init)).
-
-6. Select the file in the matches listed that will be similar to:
+1. Select `Ctrl` + `Shift` + `I` to open the developer tools.
+1. Select the **Sources** tab inside the developer tools panel.
+1. Use `Ctrl` + `P` to show the **Open File** command pallet. You can also select **Open File** from the **ellipsis** menu.
+1. Enter the name of your control (which is the name of the control you used in [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init)).
+1. Select the file in the matches listed that is similar to:
`webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./DataSetGrid/index.ts`
> [!div class="mx-imgBorder"]
> 
-7. Locate the `updateView` function and place a breakpoint on the first line.
-
-8. Make a change to the properties that are bound to your code component. In the test harness, this can be done using the properties panel, or inside Power Apps, you can make a change to a bound property or dataset. This will trigger a call to `updateView`.
-
-9. You will now see your breakpoint hit, and you can inspect the code.
+1. Locate the `updateView` function and place a breakpoint on the first line.
+1. Make a change to the properties that are bound to your code component. In the test harness, changing properties can be done using the properties panel, or inside Power Apps, you can make a change to a bound property or dataset. Changing properties triggers a call to `updateView`.
+1. You'll now see your breakpoint hit, and you can inspect the code.
> [!div class="mx-imgBorder"]
> 
-10. You can also inspect the HTML elements and CSS created by the component using the **Elements** tab. If you have a specific set of interactions that you are interested in (root container element), you can place a breakpoint on the HTML Dom element using the **Context Menu** (while the root element is selected) > **Break on** > **subtree modifications**
+1. You can also inspect the HTML elements and CSS created by the component using the **Elements** tab. If you have a specific set of interactions that you're interested in (root container element), you can place a breakpoint on the HTML Dom element using the **Context Menu** (while the root element is selected) > **Break on** > **subtree modifications**
> [!div class="mx-imgBorder"]
> 
### ES5 vs ES6
-Currently, by default, code components are configured to transpile into ES5 JavaScript so that older browsers are supported. You can change the target to ES6 if you do not need to support older browsers by setting the `target` in your projects `tsconfig.json` to `ES6`:
+Currently, by default, code components are configured to transpile into ES5 JavaScript so that older browsers are supported. You can change the target to ES6 if you don't need to support older browsers by setting the `target` in your projects `tsconfig.json` to `ES6`:
```json
{
@@ -186,9 +180,9 @@ Currently, by default, code components are configured to transpile into ES5 Java
## Debugging after deploying into Microsoft Dataverse
-To fully test the logic inside the context of a model-driven app, canvas app, or portal you can first deploy and configure your code component to Microsoft Dataverse and then use either [Fiddler](https://www.telerik.com/download/fiddler)'s AutoResponder feature or use [requestly](https://requestly.io/). In both cases you will load a development build of your code component (built locally) into the browser without having to continuously deploy changes as you debug your code. This also allows you to debug against a non-development downstream environment without having to first deploy a development build.
+To fully test the logic inside the context of a model-driven app, canvas app, or portal you can first deploy and configure your code component to Microsoft Dataverse and then use either [Fiddler](https://www.telerik.com/download/fiddler)'s Auto Responder feature or use [requestly](https://requestly.io/). In both cases, you'll load a development build of your code component (built locally) into the browser without having to continuously deploy changes as you debug your code. Debugging this way allows you to debug against a nondevelopment downstream environment without having to first deploy a development build.
-First ensure your component is deployed and configured in Microsoft Dataverse. Ideally, you should only publish production builds of code components into Microsoft Dataverse. For larger code components, publishing a development build may result in the error [Web resource size is too large](issues-and-workarounds.md#web-resource-size-is-too-large). Since we are going to redirect the code component's `bundle.js` to a locally built version, you can update your `.pcfproj` file to always build in production mode when using [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push) by setting the property `PcfBuildMode` to production.
+First ensure your component is deployed and configured in Microsoft Dataverse. Ideally, you should only publish production builds of code components into Microsoft Dataverse. For larger code components, publishing a development build might result in the error [Web resource size is too large](issues-and-workarounds.md#web-resource-size-is-too-large). Since we're going to redirect the code component's `bundle.js` to a locally built version, you can update your `.pcfproj` file to always build in production mode when using [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push) by setting the property `PcfBuildMode` to production.
```XML
@@ -204,26 +198,22 @@ First ensure your component is deployed and configured in Microsoft Dataverse. I
To debug your code component using Fiddler:
1. Download and install [Fiddler Classic](https://www.telerik.com/download/fiddler)
-
-2. Open Fiddler and from the menu bar, go to **Tools**, and then select **Options**.
-
-3. Select the **HTTPS** tab in the dialog box and check the **Capture HTTPS CONNECTS** and **Decrypt HTTPS traffic** checkboxes so that the HTTPS traffic is captured and then decrypted.
+1. Open Fiddler and from the menu bar, go to **Tools**, and then select **Options**.
+1. Select the **HTTPS** tab in the dialog box and check the **Capture HTTPS CONNECTS** and **Decrypt HTTPS traffic** checkboxes so that the HTTPS traffic is captured and then decrypted.
> [!div class="mx-imgBorder"]
> 
-4. Select **OK** to close the dialog box.
+1. Select **OK** to close the dialog box.
> [!NOTE]
>
> - If it is the first time you are enabling this setting, Fiddler will prompt you to install a certificate. Install the certificate and restart Fiddler so that the new settings take effect.
> - If you have run Fiddler in the past and get a `NET::ERR_CERT_AUTHORITY_INVALID` error, in the **HTTPS** tab, select the **Actions** button and choose **Reset All Certificates**. This will also present multiple prompts for the new certificates to be installed.
-5. In the right-hand panel, select the **AutoResponder** tab.
-
-6. Ensure that **Enable Rules** and **Unmatched requests passthrough** are checked.
-
-7. Select **Add Rule** and enter first:
+1. In the right-hand panel, select the **AutoResponder** tab.
+1. Ensure that **Enable Rules** and **Unmatched requests passthrough** are checked.
+1. Select **Add Rule** and enter first:
```
REGEX:(.*?)((?'folder'css|html)(%252f|\/))?YOUR_NAMESPACE\.YOUR_CONTROL_NAME[\.\/](?'fname'[^?]*\.*)(.*?)$
@@ -236,14 +226,14 @@ To debug your code component using Fiddler:
This rule aims to match requests for the code component's `bundle.js` and related resources (`css`/`html`) in such a way that it works for both model-driven, and canvas apps, both in Power Apps Studio and Player.
- An example of this would look like the following:
+ An example of this rule looks like the following:
> [!div class="mx-imgBorder"]
> 
- If you want a simpler **AutoResponder** rule approach, see [Script web resource development using Fiddler AutoResponder](../model-driven-apps/streamline-javascript-development-fiddler-autoresponder.md).
+ If you want a simpler **AutoResponder** rule approach, see [Script web resource development using Fiddler Auto Responder](../model-driven-apps/streamline-javascript-development-fiddler-autoresponder.md).
-8. Enter the following for the path to respond with:
+1. Enter a string like this for the path to respond with:
```
C:\COMPONENT_ROOT_FOLDER\out\controls\YOUR_CONTROL_NAME\${folder}\${fname}
@@ -255,9 +245,8 @@ To debug your code component using Fiddler:
C:\src\PowerApps-Samples\component-framework\DataSetGrid\out\controls\DataSetGrid\${folder}\${fname}
```
-9. Select **Save**.
-
-10. Open the **Filters** tab and check **Use Filters**. In the **Response Headers** section, check **Set response header** and provide the following:
+1. Select **Save**.
+1. Open the **Filters** tab and check **Use Filters**. In the **Response Headers** section, check **Set response header** and provide the following:
Header: `Access-Control-Allow-Origin`
@@ -269,12 +258,12 @@ To debug your code component using Fiddler:
> [!IMPORTANT]
> This step is only necessary when debugging code components after they are deployed to canvas apps because the resources are stored in blob storage rather than underneath the `powerapp.com` domain. As such, any requests to these resources will require cross-domain access when loaded by the browser. Only enable this `Access-Control-Allow-Origin` filter rule when you are debugging since it will modify headers of other sites that you visit.
-11. Now that you have the **AutoResponder** rules running you will need to first clear the cache in the browser and reload the page containing the code component. This can easily be done by opening developer tools (`Ctrl + Shift + I`), right-clicking the **Refresh** > **Empty cache and hard refresh**.
+1. Now that you have the **AutoResponder** rules running you'll need to first clear the cache in the browser and reload the page containing the code component. This can easily be done by opening developer tools (`Ctrl + Shift + I`), right-clicking the **Refresh** > **Empty cache and hard refresh**.
> [!div class="mx-imgBorder"]
> 
-12. Once you have your code component loaded from your local machine, you can make changes to the code (while `npm start watch` is running) and refresh the browser to load the newly built versions. Fiddler's AutoResponder will automatically add a cache-control header so that it will not be cached by the browser so a simple refresh will reload the resources without having to clear the cache each time.
+1. Once you have your code component loaded from your local machine, you can make changes to the code (while `npm start watch` is running) and refresh the browser to load the newly built versions. Fiddler's Auto Responder will automatically add a cache-control header so that it will not be cached by the browser so a simple refresh will reload the resources without having to clear the cache each time.
### Using requestly
@@ -283,45 +272,46 @@ To debug your code component using Requestly:
1. Enable Internet Information Services (IIS) on your machine.
1. Open **Control Panel** and select **Programs and Features** > **Turn Windows** features on or off.
- 2. Enable Internet Information Services.
- 3. Expand the Internet Information Services and verify that the web server components listed in the next section are enabled.
- 4. Select **OK**.
+ 1. Enable Internet Information Services.
+ 1. Expand the Internet Information Services and verify that the web server components listed in the next section are enabled.
+ 1. Select **OK**.
-2. Setup ISS
+1. Setup ISS
1. Open IIS on your machine.
- 2. In right side panel **Connections**, expand tree and right-click on **Sites**.
- 3. Add website.
- 4. Set **Site** name.
- 5. Set **Physical path** to your custom component folder, for example, `C:\COMPONENT_ROOT_FOLDER\out\controls\YOUR_CONTROL_NAME\`
- 6. Set **Port** (any number for instance **7777**).
- 7. Select **OK**. Selected folder is now hosted on `http://localhost:`
+ 1. In right side panel **Connections**, expand tree and right-click on **Sites**.
+ 1. Add website.
+ 1. Set **Site** name.
+ 1. Set **Physical path** to your custom component folder, for example, `C:\COMPONENT_ROOT_FOLDER\out\controls\YOUR_CONTROL_NAME\`
+ 1. Set **Port** (any number, for instance, **7777**).
+ 1. Select **OK**. Selected folder is now hosted on `http://localhost:`
> [!div class="mx-imgBorder"]
> 
-3. Download and install [Requestly](https://requestly.io)
+1. Download and install [Requestly](https://requestly.io)
+
+1. Follow onboarding to the tool.
-4. Follow onboarding to the tool.
+1. Open rules (navigate to https://app.requestly.io/rules).
-5. Open rules (navigate to https://app.requestly.io/rules).
+1. Add "Replace Host" rule:
-6. Add "Replace Host" rule:
1. Set name of the rule.
- 2. Set "Replace" field with `https://[ORG_URL]/[APPLICATION_ID]/webresources/[YOUR_NAMESPACE].[YOUR_CONTROL_NAME]/`
- 3. Set "With" with `http://localhost:`
- 4. Set "If request" with "URL" "Contains" `[YOUR_NAMESPACE].[YOUR_CONTROL_NAME]`
- 5. Save the rule and enable it.
+ 1. Set "Replace" field with `https://[ORG_URL]/[APPLICATION_ID]/webresources/[YOUR_NAMESPACE].[YOUR_CONTROL_NAME]/`
+ 1. Set "With" with `http://localhost:`
+ 1. Set "If request" with "URL" "Contains" `[YOUR_NAMESPACE].[YOUR_CONTROL_NAME]`
+ 1. Save the rule and enable it.
> [!div class="mx-imgBorder"]
> 
-7. Now you need to clear the cache in the browser and reload the page containing the code component. This can easily be done by opening developer tools (`Ctrl + Shift + I`), right-clicking the **Refresh** > **Empty cache and hard refresh**.
+1. Now you need to clear the cache in the browser and reload the page containing the code component. You can clear the cache in the browser and reload the page by opening developer tools (`Ctrl + Shift + I`), right-clicking the **Refresh** > **Empty cache and hard refresh**.
> [!div class="mx-imgBorder"]
> 
-8. Once you have your code component loaded from your local machine, you can make changes to the code (while `npm start watch` is running) and refresh the browser to load the newly built versions. Requestly will automatically add a cache-control header so that it will not be cached by the browser so a simple refresh will reload the resources without having to clear the cache each time.
+1. Once you have your code component loaded from your local machine, you can make changes to the code (while `npm start watch` is running) and refresh the browser to load the newly built versions. Requestly automatically adds a cache-control header so that it isn't cached by the browser so a simple refresh will reload the resources without having to clear the cache each time.
### Related articles
diff --git a/powerapps-docs/developer/component-framework/dependent-libraries.md b/powerapps-docs/developer/component-framework/dependent-libraries.md
new file mode 100644
index 0000000000..ece8d01854
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/dependent-libraries.md
@@ -0,0 +1,149 @@
+---
+title: Dependent Libraries (preview)
+description: Explains how to use dependent libraries with Power Apps Component Framework (PCF) controls.
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
+ms.reviewer: jdaly
+ms.topic: article
+ms.subservice: pcf
+contributors:
+ - JimDaly
+ - kierantpetrie
+---
+# Dependent Libraries (preview)
+
+[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+
+With model-driven apps, you can reuse a prebuilt library contained in another component that is loaded as a dependency to more than one component.
+
+Having copies of a prebuilt library in multiple controls is undesirable. Reusing existing libraries improves performance, especially when the library is large, by reducing the load time for all components that use the library. Library reuse also helps reduce the maintenance overhead in build processes.
+
+:::row:::
+ :::column span="":::
+ Before
+ :::column-end:::
+ :::column span="":::
+ After
+ :::column-end:::
+:::row-end:::
+:::row:::
+ :::column span="":::
+ :::image type="content" source="media/dependent-library-before-example.png" alt-text="Diagram showing custom library files contained in each pcf component":::
+ :::column-end:::
+ :::column span="":::
+ :::image type="content" source="media/dependent-library-after-example.png" alt-text="Diagram showing components calling a shared function from a Library Control":::
+ :::column-end:::
+:::row-end:::
+
+To use dependent libraries, you need to:
+
+- Create a *Library component* that contains the library. This component can provide some functionality or only be a container for the library.
+- Configure another component to depend on the library loaded by the library component.
+
+By default, the library loads when the dependent component loads, but you can [configure it to load on demand](#dependency-as-on-demand-load-of-a-component).
+
+This way you can independently maintain the library in the Library Control and the dependent controls don't need to have a copy of the library bundled with them.
+
+## How it works
+
+You need to add configuration data to your component project so that the build process deploys your libraries the way you want. Set this configuration data by adding or editing the following files:
+
+- [featureconfig.json](#featureconfigjson)
+- [webpack.config.js](#webpackconfigjs)
+- Edit the manifest schema to [Register dependencies](#register-dependencies)
+
+### featureconfig.json
+
+Add this file to override the default feature flags for a component without modifying the files generated in the `node_modules` folder.
+
+The following table describes the feature flags you can set in `featureconfig.json`:
+
+|Name|Description|
+|---|---|
+|`pcfResourceDependency`|Enables the component to use a library resource.|
+|`pcfAllowCustomWebpack`|Enables the component to use a custom web pack. This feature must be enabled for components that define a library resource.|
+
+By default, these values are `off`. Set them to `on` to override the default. For example:
+
+```json
+{
+ "pcfAllowCustomWebpack": "on"
+}
+```
+
+```json
+{
+ "pcfResourceDependency": "on",
+ "pcfAllowCustomWebpack": "off"
+}
+```
+
+### webpack.config.js
+
+The build process for components uses [Webpack](https://webpack.js.org/) to bundle the code and dependencies into a deployable asset. To exclude your libraries from this bundling, add a `webpack.config.js` file to the project root folder that specifies the alias of the library as `externals`. [Learn more about the Webpack externals configuration option](https://webpack.js.org/configuration/externals/)
+
+This file might look like the following when the library alias is `myLib`.
+
+```typescript
+/* eslint-disable */
+"use strict";
+
+module.exports = {
+ externals: {
+ "myLib": "myLib"
+ },
+}
+```
+
+
+### Register dependencies
+
+Use the [dependency element](manifest-schema-reference/dependency.md) within [resources](manifest-schema-reference/resources.md) of the manifest schema.
+
+```xml
+
+
+
+
+
+```
+
+### Dependency as on demand load of a component
+
+Rather than loading the dependent library when a component loads, you can load the dependent library on demand. Loading on demand provides the flexibility for more complex controls to only load dependencies when they're required, especially if the dependent libraries are large.
+
+:::image type="content" source="media/dependent-library-on-demand-load.png" alt-text="Diagram showing the use of a function from a library where the library is loaded on demand":::
+
+
+
+To enable on demand loading, you need to:
+
+1. Add these [platform-action element](manifest-schema-reference/platform-action.md), [feature-usage element](manifest-schema-reference/feature-usage.md), and [uses-feature element](manifest-schema-reference/uses-feature.md) child elements to the [control element](manifest-schema-reference/control.md):
+
+ ```xml
+
+
+
+
+ ```
+
+1. Set the `load-type` attribute of the [dependency element](manifest-schema-reference/dependency.md) to `onDemand`.
+
+ ```xml
+
+ ```
+
+### Next steps
+
+Try a tutorial that walks you through creating a dependent library.
+
+> [!div class="nextstepaction"]
+> [Tutorial: Use dependent libraries in a component](tutorial-use-dependent-libraries.md)
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/events.md b/powerapps-docs/developer/component-framework/events.md
new file mode 100644
index 0000000000..728102202c
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/events.md
@@ -0,0 +1,108 @@
+---
+title: Define Events (preview)
+description: Explains how to define new events with Power Apps Component Framework (PCF) controls.
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
+ms.reviewer: jdaly
+ms.topic: how-to
+ms.subservice: pcf
+contributors:
+ - JimDaly
+ - kierantpetrie
+---
+# Define Events (preview)
+
+[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+
+A common requirement when building custom components with the Power Apps Component Framework is the ability to react to events generated within the control. These events can be invoked either due to user interaction or programmatically via code. For example, an application can have a code component that lets a user build a product bundle. This component can also raise an event which could show product information in another area of the application.
+
+## Component Data Flow
+
+The common data flow for a code component is data flowing from the hosting application into the control as inputs and updated data flowing out of the control to the hosting form or page. This diagram shows the standard pattern of data flow for a typical PCF component:
+
+:::image type="content" source="media/component-events-onchange-example.png" alt-text="Shows that data update from the code component to the binding field triggers the `OnChange` event":::
+
+The data update from the code component to the bound field triggers the `OnChange` event. For most component scenarios, this is enough and makers just add a handler to trigger subsequent actions. However, a more complicated control might require events to be raised that aren't field updates. The event mechanism allows code components to define events that have separate event handlers.
+
+## Using events
+
+The event mechanism in PCF is based on the standard event model in JavaScript. The component can define events in the manifest file and raise these events in the code. The hosting application can listen to these events and react to them.
+
+The component defines events using the [event element](manifest-schema-reference/event.md) in the manifest file. This data allows the respective hosting application to react to events in different ways.
+
+```xml
+
+
+
+```
+
+Canvas apps react to the event using Power Fx expressions:
+
+:::image type="content" source="media\custom-events-in-canvas-designer.png" alt-text="Shows the custom events in the canvas apps designer":::
+
+Model Driven Apps use the [addEventHandler method](../model-driven-apps/clientapi/reference/controls/addeventhandler.md) to associate event handlers to custom events for a component.
+
+```javascript
+ const controlName1 = "cr116_personid";
+
+ this.onLoad = function (executionContext) {
+ const formContext = executionContext.getFormContext();
+
+ const sampleControl1 = formContext.getControl(controlName1);
+ sampleControl1.addEventHandler("customEvent1", this.onSampleControl1CustomEvent1);
+ sampleControl1.addEventHandler("customEvent2", this.onSampleControl1CustomEvent2);
+ }
+```
+
+> [!NOTE]
+> These events occur separately for each instance of the code component in the app.
+
+## Defining an event for model-driven apps
+
+For model-driven apps you can pass a payload with the event allowing for more complex scenarios. For example in the diagram below the component passes a callback function in the event allowing the script handling to call back to the component.
+
+:::image type="content" source="media/passing-payload-in-events.png" alt-text="In this example, the component passes a callback function in the event allowing the script handling to call back to the component":::
+
+
+
+```javascript
+this.onSampleControl1CustomEvent1 = function (params) {
+ //alert(`SampleControl1 Custom Event 1: ${params}`);
+ alert(`SampleControl1 Custom Event 1`);
+}.bind(this);
+
+this.onSampleControl2CustomEvent2 = function (params) {
+alert(`SampleControl2 Custom Event 2: ${params.message}`);
+// prevent the default action for the event
+params.callBackFunction();
+}
+```
+
+## Defining an event for canvas apps
+
+Makers configure an event using Power Fx on the PCF control in the properties pane.
+
+### Calling an event
+
+See how to call an event in [Events](reference/events.md).
+
+### Next steps
+
+> [!div class="nextstepaction"]
+> [Tutorial: Define a custom event in a component](tutorial-define-event.md)
diff --git a/powerapps-docs/developer/component-framework/fluent-modern-theming.md b/powerapps-docs/developer/component-framework/fluent-modern-theming.md
index 0a880d8171..3ae93e9599 100644
--- a/powerapps-docs/developer/component-framework/fluent-modern-theming.md
+++ b/powerapps-docs/developer/component-framework/fluent-modern-theming.md
@@ -2,18 +2,17 @@
title: "Style components with modern theming (preview) | Microsoft Docs"
description: You can style your components based on the modern theme used in the app."
keywords: "Component Framework, code components, Power Apps controls"
-ms.author: hemantg
-author: HemantGaur
-ms.date: 11/15/2023
+author: jasongre
+ms.author: jasongre
+ms.date: 12/04/2024
ms.reviewer: jdaly
ms.custom:
- "dyn365-a11y"
- "dyn365-developer"
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- HemantGaur
- - noazarur-microsoft
- JimDaly
---
@@ -32,13 +31,13 @@ There are four different ways to apply modern theming to your component.
## Fluent UI v9 controls
-Wrapping Fluent UI v9 controls as a component is the easiest way to utilize modern theming because the modern theme is automatically applied to these controls. The only prerequisite is to ensure your component adds a dependency on the [React controls & platform libraries (preview)](react-controls-platform-libraries.md) as shown below. This approach allows your component to use the same React and Fluent libraries as the platform, and therefore share the same React context that passes the theme tokens down to the component.
+Wrapping Fluent UI v9 controls as a component is the easiest way to utilize modern theming because the modern theme is automatically applied to these controls. The only prerequisite is to ensure your component adds a dependency on the [React controls & platform libraries](react-controls-platform-libraries.md) as shown below. This approach allows your component to use the same React and Fluent libraries as the platform, and therefore share the same React context that passes the theme tokens down to the component.
```xml
-
+
```
diff --git a/powerapps-docs/developer/component-framework/get-powerapps-cli.md b/powerapps-docs/developer/component-framework/get-powerapps-cli.md
index 4fd6f8fe70..5aea1cc453 100644
--- a/powerapps-docs/developer/component-framework/get-powerapps-cli.md
+++ b/powerapps-docs/developer/component-framework/get-powerapps-cli.md
@@ -2,8 +2,8 @@
title: Get tooling for Power Apps component framework | Microsoft Docs
description: "Get Microsoft Power Platform CLI to create, debug, and deploy code components using Power Apps component framework."
keywords: Power Apps component framework, code components, Component Framework
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: article
diff --git a/powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md b/powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md
index ae7e056d58..47fd7bfbe2 100644
--- a/powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md
+++ b/powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md
@@ -1,11 +1,11 @@
---
title: "Create your first component using Power Apps Component Framework in Microsoft Dataverse| MicrosoftDocs"
description: "Learn how to implement code components using Power Apps component framework"
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 02/06/2023
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
diff --git a/powerapps-docs/developer/component-framework/import-custom-controls.md b/powerapps-docs/developer/component-framework/import-custom-controls.md
index 98c021bf73..98fc646abe 100644
--- a/powerapps-docs/developer/component-framework/import-custom-controls.md
+++ b/powerapps-docs/developer/component-framework/import-custom-controls.md
@@ -1,11 +1,11 @@
---
title: Package a code component| Microsoft Docs
description: This article describes how to import code components into model-driven apps in Microsoft Dataverse.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 03/22/2023
+author: anuitz
+ms.author: anuitz
+ms.date: 12/04/2024
ms.reviewer: jdaly
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- JimDaly
@@ -39,8 +39,18 @@ To create and import a solution file:
3. To generate a zip file from the solution project, go into your solution project directory and build the project using the following command. This command uses *MSBuild* to build the solution project by pulling down the *NuGet* dependencies as part of the restore. Use the `/restore` only for the first time when the solution project is built. For every build after that, you can run the command `msbuild`.
```CLI
- msbuild /t:build /restore
+ msbuild /t:restore
```
+ ```CLI
+ msbuild
+ ```
+
+ Or if you have installed the .NET SDK, version >= 6 :
+
+ ```CLI
+ dotnet build
+ ```
+
> [!TIP]
> - If msbuild 15.9.* is not in the path, open Developer Command Prompt for VS 2017 to run the `msbuild` commands.
diff --git a/powerapps-docs/developer/component-framework/issues-and-workarounds.md b/powerapps-docs/developer/component-framework/issues-and-workarounds.md
index 443c1bce7c..2c81b5f21a 100644
--- a/powerapps-docs/developer/component-framework/issues-and-workarounds.md
+++ b/powerapps-docs/developer/component-framework/issues-and-workarounds.md
@@ -1,9 +1,9 @@
---
title: Common issues and workarounds (Power Apps Component Framework) | Microsoft Docs
description: Provides information on known issues and workarounds some come across while working with Power Apps component framework and CLI
-ms.author: hemantg
-author: HemantGaur
-ms.date: 02/18/2023
+author: anuitz
+ms.author: anuitz
+ms.date: 07/01/2025
ms.reviewer: jdaly
ms.topic: article
ms.subservice: pcf
@@ -17,7 +17,7 @@ Here are some common issues that you might come across while using the Power App
[!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
-## Component changes are not reflected after the updated solution import?
+## Component changes aren't reflected after the updated solution import?
Update the component version (minor or patch) in the component manifest file (for example, 1.0.0 to 1.0.1). Every update in the component needs a component version bump to be reflected on the Microsoft Dataverse server.
@@ -45,7 +45,7 @@ Update the component version (minor or patch) in the component manifest file (fo
## Issues while updating existing code components
-- If you have created a code component using the CLI version 0.1.817.1 or earlier and want to ensure that the latest build and debug modules are being used, make the updates to the `package.json` file as shown below:
+- If you created a code component using CLI version 0.1.817.1 or earlier and want to ensure that the latest build and debug modules are being used, make the following updates to the `package.json` file:
```JSON
"dependencies": { "@types/node": "^10.12.18", "@types/powerapps-component-framework": "1.1.0"}, "devDependencies": { "pcf-scripts": "~0", "pcf-start": "~0" }
@@ -77,17 +77,31 @@ Update the component version (minor or patch) in the component manifest file (fo
Error **Import Solution Failed: Web resource content size is too big**.
-**Workaround**
+### Workarounds
+
+There are two ways to work around this error:
+
+ - [Build the PCF using the release configuration](#build-the-pcf-using-the-release-configuration)
+ - [Increase the maximum size for email attachments](#increase-the-maximum-size-for-email-attachments)
+
+
+#### Build the PCF using the release configuration
+
+
+- Build the `.pcfproj` as release configuration, which sets the web pack to production mode using the command:
-- Build the `.pcfproj` as release configuration, which sets the web pack to production mode using the command
```CLI
msbuild /property:configuration=Release
```
-- Run the msbuild command with an extra property as shown below:
+
+- Run the msbuild command with the following extra property:
+
```CLI
msbuild /p:PcfBuildMode=production
```
+
- Edit the `.pcfproj` to always build the web pack in production mode by setting the property `PcfBuildMode` to production:
+
```XML
TS_ReactStandardControl
@@ -97,6 +111,12 @@ Error **Import Solution Failed: Web resource content size is too big**.
```
+#### Increase the maximum size for email attachments
+
+The size limit for files used by PCF controls is limited by the same setting that limits the size of email attachments. See the **Maximum file size for attachments** setting described in [Manage email settings](/power-platform/admin/settings-email).
+
+This value is set in the [Organization.MaxUploadFileSize](../data-platform/reference/entities/organization.md#BKMK_MaxUploadFileSize) column. [Learn how to read and update environment settings using code](../data-platform/organization-table.md)
+
## When running Power Apps checker with the solution built using CLI tooling in default configuration
**Error: Do not use the eval function or its functional equivalents**
@@ -144,23 +164,23 @@ Power Apps component framework dataset component currently does not properly sho
No workaround as of now. We are working on pushing a fix to our deployment trains.-->
-## Authentication for third party services fails in Canvas
+## Custom authentication fails in Canvas
-PCF authentication for third parties is not supported.
+Custom authentication within PCF controls is not supported within canvas apps.
**Workaround**
-Use combination of a [custom page](../../maker/model-driven-apps/model-app-page-overview.md) and a [connector](../../maker/canvas-apps/connections-list.md).
+Use [connectors](../../maker/canvas-apps/connections-list.md) to handle authentication.
-## Control cannot finish loading
+## Control can't finish loading
-If you use [refresh](./reference/dataset/refresh.md) in `updateView` you must include a guarding condition, otherwise it will create an infinite loop. Whenever `refresh` is called, it will reset the page number to 1, and then fetch the first page of records under the current filtering and sorting criteria. When the updated data is received by the client, `updateView` will be called to update the display. The result is that the control cannot finish loading and will not be able to fetch records beyond the first page.
+If you use [refresh](./reference/dataset/refresh.md) in `updateView` you must include a guarding condition, otherwise it creates an infinite loop. Whenever `refresh` is called, it resets the page number to 1, and then fetch the first page of records under the current filtering and sorting criteria. When the client recieves the updated data, `updateView` is called to update the display. The result is that the control can't finish loading and won't be able to fetch records beyond the first page.
## Same page is loaded rather than the expected one
-[refresh](./reference/dataset/refresh.md), [loadExactPage](./reference/paging/loadExactPage.md), [loadNextPage](./reference/paging/loadnextpage.md), [loadPreviousPage](./reference/paging/loadpreviouspage.md) do not support parallel execution.
+[refresh](./reference/dataset/refresh.md), [loadExactPage](./reference/paging/loadExactPage.md), [loadNextPage](./reference/paging/loadnextpage.md), [loadPreviousPage](./reference/paging/loadpreviouspage.md) don't support parallel execution.
-When these functions are called, the results for the requested page will not be available immediately in the next line. Instead they will trigger `updateView` on the control with newly fetched results.
+When these functions are called, the results for the requested page won't be available immediately in the next line. Instead they'll trigger `updateView` on the control with newly fetched results.
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/limitations.md b/powerapps-docs/developer/component-framework/limitations.md
index 44cfece627..6785aac149 100644
--- a/powerapps-docs/developer/component-framework/limitations.md
+++ b/powerapps-docs/developer/component-framework/limitations.md
@@ -1,9 +1,9 @@
---
title: "Limitations of Power Apps component framework | MicrosoftDocs"
description: "Limitations using Power Apps component framework"
-ms.author: hemantg
-author: HemantGaur
-ms.date: 02/10/2023
+author: anuitz
+ms.author: anuitz
+ms.date: 07/01/2025
ms.reviewer: jdaly
ms.topic: article
ms.subservice: pcf
@@ -17,17 +17,16 @@ With Power Apps component framework, you can create your own code components to
1. Microsoft Dataverse dependent APIs, including WebAPI, are not available for Power Apps canvas applications yet. For individual API availability, see [Power Apps component framework API reference](reference/index.md).
-2. Code components should bundle all the code including external library content into the primary code bundle. To see an example of how the Power Apps command line interface can help with bundling your external library content into a component-specific bundle, see [Angular flip component](sample-controls/angular-flip-control.md) example.
-
- > [!NOTE]
- > Support for shared libraries across components using library nodes in the component manifest is currently in public preview. More information: [React controls & platform libraries (Preview)](react-controls-platform-libraries.md).
+2. Code components should either use [React controls & platform libraries](react-controls-platform-libraries.md) or bundle all the code including external library content into the primary code bundle. To see an example of how the Power Apps command line interface can help with bundling your external library content into a component-specific bundle, see [Angular flip component](sample-controls/angular-flip-control.md) example.
3. Code components should not use the HTML web storage objects, like `window.localStorage` and `window.sessionStorage`, to store data. Data stored locally on the user's browser or mobile client is not secure and not guaranteed to be available reliably.
+4. Custom auth in code components is not supported in Power Apps canvas applications. Use connectors to get data and take actions instead.
+
## Related topics
[Power Apps component framework API reference](reference/index.md)
[Power Apps component framework overview](overview.md)
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
\ No newline at end of file
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/code.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/code.md
index 4a06c1f7d1..f74368febc 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/code.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/code.md
@@ -1,8 +1,8 @@
---
title: Code Element | Microsoft Docs
description: Refers to the path where the resource files are located.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -40,7 +40,7 @@ Model-driven and canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/control.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/control.md
index 796324a117..40b3a25a6d 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/control.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/control.md
@@ -1,9 +1,9 @@
---
-title: Control Element | Microsoft Docs
-description: Defines the component's namespace, version and display information.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 02/22/2023
+title: control Element | Microsoft Docs
+description: Defines the component's namespace, version, and display information.
+ms.author: anuitz
+author: anuitz
+ms.date: 03/24/2025
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -25,10 +25,10 @@ Model-driven and canvas apps
|--|--|--|--|--------|
|`namespace`|Defines the object prototype of the component|[!INCLUDE [alphanumerictype-description](includes/alphanumerictype-description.md)]|Yes|Model-driven and canvas apps |
|`constructor`|A method for initializing the object|[!INCLUDE [alphanumerictype-description](includes/alphanumerictype-description.md)]|Yes|Model-driven and canvas apps |
-|`control-type`|Whether the control is a standard control or a React control. The value of `virtual` indicates a React control using platform React library. Virtual controls are a feature in public preview. More information: [React controls & platform libraries (Preview) ](../react-controls-platform-libraries.md)|[!INCLUDE [controltype-description](includes/controltype-description.md)]|No|Model-driven and canvas apps |
-|`description-key`|Defines the description of the component that will be seen on the UI.|`string`|No|Model-driven and canvas apps |
-|`display-name-key`|Defines the name of the control that is displayed on the UI.|`string`|Yes|Model-driven and canvas apps |
-|`preview-image`|Image that will be used on the customization screens to show a preview of the component.|`string`|No|Model-driven apps|
+|`control-type`|Whether the control is a standard control or a React control. The value of `virtual` indicates a React control using platform React library. Virtual controls are a feature in public preview. More information: [React controls & platform libraries](../react-controls-platform-libraries.md)|[!INCLUDE [controltype-description](includes/controltype-description.md)]|No|Model-driven and canvas apps |
+|`description-key`|Defines the description of the component visible in the UI.|`string`|No|Model-driven and canvas apps |
+|`display-name-key`|Defines the name of the control visible in the UI.|`string`|Yes|Model-driven and canvas apps |
+|`preview-image`|Image used on the customization screens to show a preview of the component.|`string`|No|Model-driven apps|
|`version`|Defines the version of the component defined in [Semantic Versioning](https://semver.org)|`string`|Yes|Model-driven and canvas apps |
@@ -48,6 +48,7 @@ Model-driven and canvas apps
|[resources](resources.md)|[!INCLUDE [resources-description](includes/resources-description.md)]|1|
|[type-group](type-group.md)|[!INCLUDE [type-group-description](includes/type-group-description.md)]|0 or more|
|[property-dependencies](property-dependencies.md)|[!INCLUDE [property-dependencies-description](includes/property-dependencies-description.md)]|0 or more|
+|[platform-action](platform-action.md)|[!INCLUDE [platform-action-description](includes/platform-action-description.md)]|0 or 1|
## Example
@@ -62,10 +63,10 @@ Model-driven and canvas apps
```
-### Related topics
+### Related articles
-[Power Apps component framework manifest schema reference](index.md)
-[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/css.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/css.md
index 97afd532ed..41e81da5d8 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/css.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/css.md
@@ -1,8 +1,8 @@
---
title: CSS Element | Microsoft Docs
description: CSS describes how code components are to be displayed on UI.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -41,7 +41,7 @@ Model-driven and canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/data-set.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/data-set.md
index 5d82250851..e590bd2bf5 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/data-set.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/data-set.md
@@ -1,8 +1,8 @@
---
-title: DataSet Element | Microsoft Docs
+title: data-set Element | Microsoft Docs
description: The data-set node in the component manifest represents a specific, configurable representation of a set of table records.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -15,9 +15,9 @@ contributors:
[!INCLUDE [data-set-description](includes/data-set-description.md)]
-You can define multiple datasets in the manifest. The first dataset in the manifest is as the primary dataset. When configuring the multi dataset component, the primary dataset property always has name `Items`. All non-primary dataset properties will have a `_Items` suffix after the dataset name.
+You can define multiple datasets in the manifest. The first dataset in the manifest is as the primary dataset. When you configure a multi dataset component, the primary dataset property always has name `Items`. All nonprimary dataset properties will have a `_Items` suffix after the dataset name.
-Certain features in the authoring panel will only apply to the primary dataset properties, such as data source selector, field selector, and view selector. To configure a non-primary dataset property, the maker needs to first import the data source to the app, then set the property value to that secondary data source. Property-set should be used for accessing columns in a non-primary dataset property.
+Certain features in the authoring panel only apply to the primary dataset properties, such as data source selector, field selector, and view selector. To configure a nonprimary dataset property, the maker needs to first import the data source to the app, then set the property value to that secondary data source. Property-set should be used for accessing columns in a nonprimary dataset property.
## Parameters
@@ -26,7 +26,7 @@ Certain features in the authoring panel will only apply to the primary dataset p
|`description-key`|Defines the description of the property.|`string`|Optional|Model-driven and canvas apps|
|`display-name-key`|Defines the name of the property.|`string`|Yes|Model-driven and canvas apps|
|`name`|Name of the grid|`string`|Yes|Model-driven and canvas apps|
-|`cds-data-set-options`|Displays the Commandbar, ViewSelector, QuickFind if set to true |`string`|Yes|Model-driven apps|
+|`cds-data-set-options`|Displays the `Commandbar`, `ViewSelector`, `QuickFind` if set to true |`string`|Yes|Model-driven apps|
## Parent Elements
@@ -38,14 +38,16 @@ Certain features in the authoring panel will only apply to the primary dataset p
## Example
```xml
-
-
+
+
```
-### Related topics
+### Related articles
-[Power Apps component framework manifest schema reference](index.md)
-[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/dependency.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/dependency.md
new file mode 100644
index 0000000000..afaef96415
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/dependency.md
@@ -0,0 +1,54 @@
+---
+title: dependency Element | Microsoft Docs
+description: Refers to a library in another component that this component depends on.
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+ - kierantpetrie
+---
+
+# dependency element
+
+[!INCLUDE [dependency-description](includes/dependency-description.md)]
+
+## Available for
+
+Model-driven apps
+
+## Parameters
+
+|Name|Description|Type|Required|Available for|
+|--|--|--|--|-----|
+|`type`|Set to `control`|`String`|Yes|Model-driven apps |
+|`name`|The schema name name of the library component|`String`|Yes|Model-driven apps |
+|`order`|The order in which the dependent library should load|`Positive integer`|No|Model-driven apps |
+|`load-type`|Set to `onDemand`|`String`|No|Model-driven apps |
+
+## Parent Elements
+
+|Element|Description|
+|--|--|
+|[resources](resources.md)|[!INCLUDE [resources-description](includes/resources-description.md)]|
+
+### Example
+
+```XML
+
+```
+
+### Related articles
+
+[Dependent Libraries (preview)](../dependent-libraries.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework overview](../overview.md)
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/domain.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/domain.md
index 89de0d219b..900b406a9c 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/domain.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/domain.md
@@ -1,8 +1,8 @@
---
title: domain element | Microsoft Docs
description: Indicates the domain that the external-usage-element applies to.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 02/22/2023
ms.reviewer: jdaly
ms.topic: reference
@@ -32,7 +32,7 @@ Canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/event.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/event.md
index 028f2f8cb5..a956918404 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/event.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/event.md
@@ -1,9 +1,10 @@
---
title: Event Element | Microsoft Docs
description: Defines a Power FX expression that can be configured within Power Apps Studio, then triggered within the component code.
-ms.author: olidum
-author: OliverDumrique
-ms.date: 11/20/2023
+author: anuitz
+ms.author: anuitz
+ms.reviewer: jdaly
+ms.date: 03/24/2025
ms.topic: reference
ms.subservice: pcf
contributors:
@@ -16,15 +17,15 @@ contributors:
## Available for
-Canvas apps
+Canvas and model-driven apps
## Properties
|Name |Description |Type |Required | Available for|
|------|------|------|-------|------------|
-|`name` |Name of the event |`string` |Yes |Canvas apps|
-|`display-name-key` |Used in the customization screens as localized strings that describes the name of the event. |`string` |Yes |Canvas apps|
-|`description-key` |Used in the customization screens as localized strings that describes the description of the event. |`string` |Optional |Canvas apps|
+|`name` |Name of the event |`string` |Yes |Canvas and model-driven apps|
+|`display-name-key` |Used in the customization screens as localized strings that describe the name of the event. |`string` |Yes |Canvas apps|
+|`description-key` |Used in the customization screens as localized strings that describe the description of the event. |`string` |Optional |Canvas apps|
|`pfx-default-value` |The default Power Fx expression value provided to the component. |See [Remarks](#remarks) |Optional |Canvas apps|
### Remarks
@@ -46,7 +47,7 @@ Canvas apps
description-key="OnSelectCustomButton_Desc_Key" />
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/external-service-usage.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/external-service-usage.md
index 7dcb48499b..d3609da5ec 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/external-service-usage.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/external-service-usage.md
@@ -1,8 +1,8 @@
---
title: external-service-usage element | Microsoft Docs
description: Indicates whether this control is using external service or not.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 02/22/2023
ms.reviewer: jdaly
ms.topic: reference
@@ -55,13 +55,13 @@ External usage enabled for multiple domains.
## Example 3
-External usage is not enabled.
+External usage isn't enabled.
```xml
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/feature-usage.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/feature-usage.md
index dbeddf3a53..2d1ac31116 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/feature-usage.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/feature-usage.md
@@ -1,8 +1,8 @@
---
title: feature-usage | Microsoft Docs
description: The feature-usage element acts as a wrapper around the uses-feature elements, which themselves allow developers to declare which features their component wants to use.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/img.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/img.md
index 3878ca5982..0dd0f06245 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/img.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/img.md
@@ -1,8 +1,8 @@
---
title: Image Element | Microsoft Docs
description: The img web resource allows you to add images for the code components.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -41,7 +41,7 @@ Model-driven apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/control-description.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/control-description.md
index 4292509fd2..ccfe1d6eaf 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/control-description.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/control-description.md
@@ -1 +1 @@
-Defines the component's namespace, version and display information.
+Defines the component's namespace, version, and display information.
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/dependency-description.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/dependency-description.md
new file mode 100644
index 0000000000..058e1f200d
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/dependency-description.md
@@ -0,0 +1 @@
+Refers to a library in another component that this component depends on.
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/platform-action-description.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/platform-action-description.md
new file mode 100644
index 0000000000..cb2479ec97
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/platform-action-description.md
@@ -0,0 +1 @@
+Used to specify that control dependencies load on demand instead of when the control is loaded.
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/index.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/index.md
index 01304a8d76..ef6e912509 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/index.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/index.md
@@ -1,9 +1,9 @@
---
title: Power Apps component framework manifest schema reference | Microsoft Docs
description: This section contains reference documentation for manifest schema generated using Microsoft Power Platform CLI.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 02/22/2023
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -25,11 +25,13 @@ This section contains reference documentation for manifest schema generated usin
|[css](css.md)|[!INCLUDE [css-description](includes/css-description.md)]|Model-driven and canvas apps|
|[data-set](data-set.md)|[!INCLUDE [data-set-description](includes/data-set-description.md)]|Model-driven apps|
|[domain](domain.md)|[!INCLUDE [domain-description](includes/domain-description.md)]|Canvas apps|
+|[dependency](dependency.md)|[!INCLUDE [dependency-description](includes/dependency-description.md)]|Model-driven apps|
|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|Canvas apps|
|[event element](event.md)|[!INCLUDE [event-description](includes/event-description.md)]|Canvas apps|
|[feature-usage](feature-usage.md)|The feature-usage element acts as a wrapper around the `uses-feature` elements, which themselves allow developers to declare which features their component wants to use. If there are no uses-feature elements defined, the feature-usage element is not required.|Model-driven apps|
|[img](img.md)|[!INCLUDE [img-description](includes/img-description.md)]|Model-driven apps|
|[manifest](manifest.md)|Manifest is the metadata file that defines a component. It is an XML document that describes - The namespace of the component. - The kind of data it can be configured, either a field or a data-set. - Any properties that can be configured in the application when the component is added. - A list of resource files that the component needs. - One of them must be a JavaScript web resource. This JavaScript must include a function that will instantiate an object. This implements an interface that exposes methods that are required for the component to work. This is called the component implementation library. - The name of a JavaScript function in the component implementation library that will return an object that applies the required interface. When someone configures a component in the application, the data in the manifest filters out the available components so that only valid components for the context are available for configuration. The properties defined in the manifest for a component are rendered as configuration fields so that the person configuring the control can specify values. These property values are then available to your component function at run time.|Model-driven and canvas apps|
+|[platform-action](platform-action.md)|[!INCLUDE [platform-action-description](includes/platform-action-description.md)]|Model-driven and canvas apps|
|[platform-library](platform-library.md)|[!INCLUDE [platform-library-description](includes/platform-library-description.md)]|Model-driven and canvas apps|
|[property-dependencies](property-dependencies.md)|[!INCLUDE [property-dependencies-description](includes/property-dependencies-description.md)]|Canvas apps|
|[property-dependency](property-dependency.md)|[!INCLUDE [property-dependency-description](includes/property-dependency-description.md)]|Canvas apps|
@@ -37,15 +39,16 @@ This section contains reference documentation for manifest schema generated usin
|[property](property.md)|[!INCLUDE [property-description](includes/property-description.md)]|Model-driven and canvas apps|
|[resources](resources.md)|[!INCLUDE [resources-description](includes/resources-description.md)]|Model-driven and canvas apps|
|[resx](resx.md)|[!INCLUDE [resx-description](includes/resx-description.md)]|Model-driven and canvas apps|
-|[type-group](type-group.md)|[!INCLUDE [type-group-description](includes/type-group-description.md)]|Model-driven and canvas apps|
|[type](type.md)|[!INCLUDE [type-description](includes/type-description.md)]|Model-driven apps|
+|[type-group](type-group.md)|[!INCLUDE [type-group-description](includes/type-group-description.md)]|Model-driven and canvas apps|
+|[types](types.md)|[!INCLUDE [types-description](includes/types-description.md)]|Model-driven and canvas apps|
|[uses-feature](uses-feature.md)|[!INCLUDE [uses-feature-description](includes/uses-feature-description.md)]|Model-driven apps|
-### Related topics
+### Related articles
-[Power Apps component framework manifest schema reference](index.md)
-[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/manifest.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/manifest.md
index d0030a1f5e..3c1188f81e 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/manifest.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/manifest.md
@@ -1,8 +1,8 @@
---
title: Manifest Element | Microsoft Docs
description: Manifest is the metadata file that defines a component.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 02/06/2023
ms.reviewer: jdaly
ms.topic: reference
@@ -59,7 +59,7 @@ Model-driven and canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-action.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-action.md
new file mode 100644
index 0000000000..34be66278f
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-action.md
@@ -0,0 +1,48 @@
+---
+title: platform-action Element | Microsoft Docs
+description: "Used to specify that control dependencies load on demand instead of when the control is loaded."
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+ - kierantpetrie
+---
+
+# platform-action element
+
+[!INCLUDE [platform-action-description](includes/platform-action-description.md)]
+
+## Available for
+
+Model-driven apps
+
+## Parameters
+
+|Name|Description|Type|Required|Available for|
+|--|--|--|--|--------|
+|`action-type`| Set to `afterPageLoad` | string | No | Model-driven apps|
+
+## Parent Elements
+
+|Element|Description|
+|--|--|
+|[control](control.md)|[!INCLUDE [control-description](includes/control-description.md)]|
+
+### Example
+
+```XML
+
+```
+
+### Related articles
+
+[Dependent Libraries (preview)](../dependent-libraries.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework overview](../overview.md)
+
+[!INCLUDE [footer-banner](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-library.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-library.md
index 89504718c2..febcd37672 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-library.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/platform-library.md
@@ -1,9 +1,9 @@
---
title: platform-library Element | Microsoft Docs
description: "Platform library resources used in the component."
-ms.author: hemantg
-author: HemantGaur
-ms.date: 04/02/2024
+author: anuitz
+ms.author: anuitz
+ms.date: 12/04/2024
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -39,14 +39,14 @@ Model-driven and canvas apps
```xml
-
+
```
### Related articles
-[React controls & platform libraries (Preview)](../react-controls-platform-libraries.md)
+[React controls & platform libraries](../react-controls-platform-libraries.md)
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependencies.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependencies.md
index e468c19809..51f83447ac 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependencies.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependencies.md
@@ -1,8 +1,8 @@
---
title: property-dependencies Element | Microsoft Docs
description: Defines a group of property-dependencies.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 11/21/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -39,7 +39,7 @@ Canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependency.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependency.md
index 6d4d0b9cbc..9d647c7234 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependency.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/property-dependency.md
@@ -1,8 +1,8 @@
---
title: property-dependency Element | Microsoft Docs
description: A property dependency in the property-dependencies node. Defines dependency between two properties.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 11/30/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -41,7 +41,7 @@ Canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/property-set.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/property-set.md
index 7c49a9fae9..865c9f43c9 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/property-set.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/property-set.md
@@ -1,8 +1,8 @@
---
title: Property Set Element | Microsoft Docs
description: Defines an inner configuration within a dataset manifest node to allow you to explicitly configure a column of your dataset against a column of a given type from the table against which the dataset is configured.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -49,7 +49,7 @@ The `of-type` attribute value must be one of the following:
[!INCLUDE [type-table](includes/type-table.md)]
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/property.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/property.md
index 8840134c53..1827319b22 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/property.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/property.md
@@ -1,8 +1,8 @@
---
title: Property Element | Microsoft Docs
description: The property node defines a specific, configurable piece of data that the component expects from the Microsoft Dataverse.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -61,7 +61,7 @@ The `of-type` property value must be one of the following:
description-key="myFirstProperty_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" />
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/resources.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/resources.md
index 2786be5dac..57523f466d 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/resources.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/resources.md
@@ -1,9 +1,9 @@
---
-title: Resources Element | Microsoft Docs
+title: resources Element | Microsoft Docs
description: The resources node in the component manifest refers to the resource files that component requires to implement it's visualization.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -34,6 +34,7 @@ Model-driven and canvas apps
|[img](img.md)|[!INCLUDE [img-description](includes/img-description.md)]|0 or more|
|[resx](resx.md)|[!INCLUDE [resx-description](includes/resx-description.md)]|0 or more|
|[platform-library](platform-library.md)|[!INCLUDE [platform-library-description](includes/platform-library-description.md)]|0 or more|
+|[dependency](dependency.md)|[!INCLUDE [dependency-description](includes/dependency-description.md)]|0 or more|
## Example
@@ -45,10 +46,10 @@ Model-driven and canvas apps
```
-### Related topics
+### Related articles
-[Power Apps component framework manifest schema reference](index.md)
-[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/resx.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/resx.md
index b3cdab5842..dda55a3a91 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/resx.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/resx.md
@@ -1,8 +1,8 @@
---
title: Resx Element | Microsoft Docs
description: The resx web resource is used to manage the localized strings you define.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -44,7 +44,7 @@ Model-driven and canvas apps
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/type-group.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/type-group.md
index 31c053bb38..6ef35895de 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/type-group.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/type-group.md
@@ -1,8 +1,8 @@
---
title: Type Group Element | Microsoft Docs
description: The type-group node defines a set of types identified by a single name. This information can be used to identify the data types supported by a specific property.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -85,7 +85,7 @@ While the following would again receive "Decimal":
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/type.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/type.md
index 31ee76fa85..dc5d402dc8 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/type.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/type.md
@@ -1,8 +1,8 @@
---
title: Type | Microsoft Docs
description: The type in the type-group node defines the data type in Microsoft Dataverse.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -40,7 +40,7 @@ This element contains a `string` with one of the following values:
```
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/types.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/types.md
index 9d4502207c..880da2ded2 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/types.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/types.md
@@ -1,8 +1,8 @@
---
title: Types | Microsoft Docs
description: Provides information on methods available for types element.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -30,7 +30,7 @@ Model-driven and canvas apps
|[type](type.md)|[!INCLUDE [type-description](includes/type-description.md)]|0 or more|
-### Related topics
+### Related articles
[Power Apps component framework manifest schema reference](index.md)
[Power Apps component framework API reference](../reference/index.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/uses-feature.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/uses-feature.md
index fe0bdd46e2..ba912b2e76 100644
--- a/powerapps-docs/developer/component-framework/manifest-schema-reference/uses-feature.md
+++ b/powerapps-docs/developer/component-framework/manifest-schema-reference/uses-feature.md
@@ -1,9 +1,9 @@
---
title: uses-feature | Microsoft Docs
description: Indicates which feature their components want to use.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+author: anuitz
+ms.author: anuitz
+ms.date: 03/24/2025
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -19,18 +19,20 @@ contributors:
Model-driven apps
+## Parameters
+
+|Element|Description|Type|Required|
+|--|--|---|----|
+|`name`|Name of the feature that is declared in the component|`string`|Yes|
+|`required`|Indicates if the component requires that feature or not|`boolean`|Yes|
+
## Parent Element
|Element|Description|
|--|--|
-|feature-usage|The feature-usage element acts as a wrapper around the uses-feature elements, which themselves allow developers to declare which features their component wants to use. If there are no uses-feature elements defined, the feature-usage element is not required.|
+|[feature-usage](feature-usage.md)|[!INCLUDE [feature-usage-description](includes/feature-usage-description.md)]|
-## Child Elements
-|Element|Description|Type|Required|
-|--|--|---|----|
-|name|Name of the feature that is declared in the component|`string`|Yes|
-|required|Indicates if the component requires that feature or not|`boolean`|Yes|
### Example
@@ -40,18 +42,18 @@ Model-driven apps
```
-The table below shows the relationship of these settings to what happens in the code at runtime whether the feature function will be available to call based upon the uses-feature settings defined in the manifest.
+The following table shows the relationship of these settings to what happens in the code at runtime whether the feature function is available to call based upon the `uses-feature` settings defined in the manifest.
|Manifest|If Host supports|If Host doesn't support|
|----|----|-----|
-|`uses-feature name="device.captureImage" required="true"`|`Context.device.captureImage != null`, no check needed.|Warning at design time. Component load will fail at runtime.|
+|`uses-feature name="device.captureImage" required="true"`|`Context.device.captureImage != null`, no check needed.|Warning at design time. Component load fails at runtime.|
|`uses-feature name="device.captureImage" required="false"`|`Context.device.captureImage != null`|`Context.device.captureImage == null`, component can adaptively check this at runtime. |
|(none)|`Context.device.captureImage == null` |`Context.device.captureImage == null` |
-### Related topics
+### Related articles
-[Power Apps component framework manifest schema reference](index.md)
-[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework manifest schema reference](index.md)
+[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/media/component-events-onchange-example.png b/powerapps-docs/developer/component-framework/media/component-events-onchange-example.png
new file mode 100644
index 0000000000..0a8d70e3e9
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/component-events-onchange-example.png differ
diff --git a/powerapps-docs/developer/component-framework/media/custom-events-in-canvas-designer.png b/powerapps-docs/developer/component-framework/media/custom-events-in-canvas-designer.png
new file mode 100644
index 0000000000..6088a7caf5
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/custom-events-in-canvas-designer.png differ
diff --git a/powerapps-docs/developer/component-framework/media/define-custom-event-tutorial-diagram.png b/powerapps-docs/developer/component-framework/media/define-custom-event-tutorial-diagram.png
new file mode 100644
index 0000000000..da4b2604d9
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/define-custom-event-tutorial-diagram.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-after-example.png b/powerapps-docs/developer/component-framework/media/dependent-library-after-example.png
new file mode 100644
index 0000000000..da74bcf518
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-after-example.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-before-example.png b/powerapps-docs/developer/component-framework/media/dependent-library-before-example.png
new file mode 100644
index 0000000000..d7c9778dd5
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-before-example.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-libprojectview.png b/powerapps-docs/developer/component-framework/media/dependent-library-libprojectview.png
new file mode 100644
index 0000000000..3567011838
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-libprojectview.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-loaded.png b/powerapps-docs/developer/component-framework/media/dependent-library-loaded.png
new file mode 100644
index 0000000000..dd4f7bcf45
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-loaded.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-loading.png b/powerapps-docs/developer/component-framework/media/dependent-library-loading.png
new file mode 100644
index 0000000000..cf9de9dd3d
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-loading.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-on-demand-load.png b/powerapps-docs/developer/component-framework/media/dependent-library-on-demand-load.png
new file mode 100644
index 0000000000..49db58ec8b
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-on-demand-load.png differ
diff --git a/powerapps-docs/developer/component-framework/media/dependent-library-running.png b/powerapps-docs/developer/component-framework/media/dependent-library-running.png
new file mode 100644
index 0000000000..f728924c7b
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/dependent-library-running.png differ
diff --git a/powerapps-docs/developer/component-framework/media/event_canvas_sample_app.png b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app.png
new file mode 100644
index 0000000000..c707ad2bc8
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app.png differ
diff --git a/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_customevents.png b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_customevents.png
new file mode 100644
index 0000000000..8f2a84e34f
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_customevents.png differ
diff --git a/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_displaymode.png b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_displaymode.png
new file mode 100644
index 0000000000..847251c1b7
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_displaymode.png differ
diff --git a/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_visible.png b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_visible.png
new file mode 100644
index 0000000000..bcfed542b6
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/event_canvas_sample_app_visible.png differ
diff --git a/powerapps-docs/developer/component-framework/media/event_mda_sample_jsbinding.png b/powerapps-docs/developer/component-framework/media/event_mda_sample_jsbinding.png
new file mode 100644
index 0000000000..35a4162b95
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/event_mda_sample_jsbinding.png differ
diff --git a/powerapps-docs/developer/component-framework/media/event_mda_sample_param.png b/powerapps-docs/developer/component-framework/media/event_mda_sample_param.png
new file mode 100644
index 0000000000..0622681cb7
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/event_mda_sample_param.png differ
diff --git a/powerapps-docs/developer/component-framework/media/passing-payload-in-events.png b/powerapps-docs/developer/component-framework/media/passing-payload-in-events.png
new file mode 100644
index 0000000000..537f7e9bcb
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/passing-payload-in-events.png differ
diff --git a/powerapps-docs/developer/component-framework/media/src/define-custom-event-tutorial-diagram.vsdx b/powerapps-docs/developer/component-framework/media/src/define-custom-event-tutorial-diagram.vsdx
new file mode 100644
index 0000000000..e731bf7d36
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/src/define-custom-event-tutorial-diagram.vsdx differ
diff --git a/powerapps-docs/developer/component-framework/media/src/passing-payload-in-events.vsdx b/powerapps-docs/developer/component-framework/media/src/passing-payload-in-events.vsdx
new file mode 100644
index 0000000000..85cd0b240e
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/src/passing-payload-in-events.vsdx differ
diff --git a/powerapps-docs/developer/component-framework/media/src/pcf_events_dependencies_diagrams.vsdx b/powerapps-docs/developer/component-framework/media/src/pcf_events_dependencies_diagrams.vsdx
new file mode 100644
index 0000000000..0cfe7cc936
Binary files /dev/null and b/powerapps-docs/developer/component-framework/media/src/pcf_events_dependencies_diagrams.vsdx differ
diff --git a/powerapps-docs/developer/component-framework/overview.md b/powerapps-docs/developer/component-framework/overview.md
index 19cafad27b..06ad7e9470 100644
--- a/powerapps-docs/developer/component-framework/overview.md
+++ b/powerapps-docs/developer/component-framework/overview.md
@@ -2,8 +2,8 @@
title: "Power Apps component framework overview in Microsoft Dataverse | Microsoft Docs"
description: "Use the Power Apps component framework to create code components to provide an enhanced experiences for people to view and work with data in forms, views, and dashboards."
keywords: "Component Framework, code components, Power Apps controls"
-ms.author: hemantg
-author: HemantGaur
+ms.author: anuitz
+author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: overview
@@ -19,7 +19,7 @@ Power Apps component framework empowers professional developers and app makers t
- Replace a column on a form that displays a numeric text value with a `dial` or `slider` code component.
- Transform a list into an entirely different visual experience bound to the dataset, like a `Calendar` or `Map`.
-> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4slRe]
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=69a0fdf4-5b3c-461e-b921-94aad4b7f717]
> [!IMPORTANT]
diff --git a/powerapps-docs/developer/component-framework/publish-components-app-source.md b/powerapps-docs/developer/component-framework/publish-components-app-source.md
index 081624acec..83b87f859a 100644
--- a/powerapps-docs/developer/component-framework/publish-components-app-source.md
+++ b/powerapps-docs/developer/component-framework/publish-components-app-source.md
@@ -2,8 +2,8 @@
title: "Publish code components on AppSource | Microsoft Docs"
description: "After you have tested your code components and want it to distribute to others to use it, you must publish it on Microsoft AppSource."
keywords: "Component Framework, code components, Power Apps controls"
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: article
diff --git a/powerapps-docs/developer/component-framework/react-controls-platform-libraries.md b/powerapps-docs/developer/component-framework/react-controls-platform-libraries.md
index 3dd24ad0be..c9320ae428 100644
--- a/powerapps-docs/developer/component-framework/react-controls-platform-libraries.md
+++ b/powerapps-docs/developer/component-framework/react-controls-platform-libraries.md
@@ -1,35 +1,37 @@
---
-title: "React controls & platform libraries (preview) | Microsoft Docs"
+title: "React controls & platform libraries | Microsoft Docs"
description: "You can achieve significant performance gains using React and platform libraries. When you use React and platform libraries, you're using the same infrastructure used by the Power Apps platform. This means you no longer have to package React and Fluent packages individually for each control."
keywords: "Component Framework, code components, Power Apps controls"
-ms.author: hemantg
-author: HemantGaur
-ms.date: 06/18/2024
+author: anuitz
+ms.author: anuitz
+ms.date: 12/04/2024
ms.reviewer: jdaly
ms.custom:
- "dyn365-a11y"
- "dyn365-developer"
-ms.topic: article
+ms.topic: how-to
ms.subservice: pcf
contributors:
- miglisic
- JimDaly
---
-# React controls & platform libraries (preview)
+# React controls & platform libraries
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
-
-You can achieve significant performance gains using React and platform libraries. When you use React and platform libraries, you're using the same infrastructure used by the Power Apps platform. This means you no longer have to package React and Fluent libraries individually for each control. All controls share a common library instance and version to provide a seamless and consistent experience.
+When you use React and platform libraries, you're using the same infrastructure used by the Power Apps platform. This means you no longer have to package React and Fluent libraries individually for each control. All controls share a common library instance and version to provide a seamless and consistent experience.
By reusing the existing platform React and Fluent libraries, you can expect the following benefits:
- Reduced control bundle size
- Optimized solution packaging
- Faster runtime transfer, scripting, and control rendering
+- Design and theme alignment with the Power Apps Fluent design system
With the benefits available by reusing these component resources, we expect this approach will become the preferred way all Power Apps code components will be created after this feature reaches general availability.
+> [!NOTE]
+> With GA release, all existing virtual controls will continue to function. However, they should be rebuilt and deployed using the latest CLI version (>=1.37) to facilitate future platform React version upgrades.
+
## Prerequisites
As with any component, you must install [Visual Studio Code](https://code.visualstudio.com/Download) and the [Microsoft Power Platform CLI](../data-platform/powerapps-cli.md#install-microsoft-power-platform-cli) as described here: [Prerequisites](implementing-controls-using-typescript.md#prerequisites)
@@ -81,7 +83,7 @@ Within the [resources element](manifest-schema-reference/resources.md), find two
```xml
-
+
```
@@ -100,7 +102,7 @@ React and Fluent libraries aren't included in the package because they're shared
## Sample controls
-You can find two new controls added to the samples as part of this preview. Functionally, they're the same as their standard version but have better performance.
+The following controls are included in the samples. They function the same as their standard versions but offer better performance since they are virtual controls.
|Sample |Description|Link|
|---------|---------|---------|
@@ -113,8 +115,9 @@ Platform libraries are made available both at the build and runtime to the contr
| Name | npm package name | Allowed version range | Version loaded |
| ------ | --------------------------- | ---------------------- | -------------- |
-| React | react | 16.8.6 | 17.0.2 (Model), 16.14.0 (Canvas) |
+| React | react | 16.14.0 | 17.0.2 (Model), 16.14.0 (Canvas) |
| Fluent | @fluentui/react | 8.29.0 | 8.29.0 |
+| Fluent | @fluentui/react | 8.121.1 | 8.121.1 |
| Fluent | @fluentui/react-components | >=9.4.0 <=9.46.2 | 9.46.2 |
> [!NOTE]
diff --git a/powerapps-docs/developer/component-framework/reference/ControlAttributes.md b/powerapps-docs/developer/component-framework/reference/ControlAttributes.md
index 808c70cab2..692b99ced8 100644
--- a/powerapps-docs/developer/component-framework/reference/ControlAttributes.md
+++ b/powerapps-docs/developer/component-framework/reference/ControlAttributes.md
@@ -1,8 +1,8 @@
---
title: ControlAttributes (Power Apps component framework API reference) | Microsoft Docs
description: Attributes of control that necessary for formatting.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/ControlAttributesType.md b/powerapps-docs/developer/component-framework/reference/ControlAttributesType.md
index 23e86d0d0d..73e9bf5004 100644
--- a/powerapps-docs/developer/component-framework/reference/ControlAttributesType.md
+++ b/powerapps-docs/developer/component-framework/reference/ControlAttributesType.md
@@ -1,8 +1,8 @@
---
title: ControlAttributesType (Power Apps component framework API reference)| Microsoft Docs
description: Enumeration of control attribute type.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/DataProviderCapabilities.md b/powerapps-docs/developer/component-framework/reference/DataProviderCapabilities.md
index 6fe087a63e..f9a0621227 100644
--- a/powerapps-docs/developer/component-framework/reference/DataProviderCapabilities.md
+++ b/powerapps-docs/developer/component-framework/reference/DataProviderCapabilities.md
@@ -1,8 +1,8 @@
---
title: DataProviderCapabilities (Power Apps component framework API reference) | Microsoft Docs
description: Provides methods to use dataset capabilities.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/DateTimeFieldBehavior.md b/powerapps-docs/developer/component-framework/reference/DateTimeFieldBehavior.md
index 01a9a37585..60e89c28d7 100644
--- a/powerapps-docs/developer/component-framework/reference/DateTimeFieldBehavior.md
+++ b/powerapps-docs/developer/component-framework/reference/DateTimeFieldBehavior.md
@@ -1,8 +1,8 @@
---
title: DateTimeFieldBehavior (Power Apps component framework API reference)| Microsoft Docs
description: The behavior of the datetime object to be formatted.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/ICommand.md b/powerapps-docs/developer/component-framework/reference/ICommand.md
index 44b928f69a..4494f23856 100644
--- a/powerapps-docs/developer/component-framework/reference/ICommand.md
+++ b/powerapps-docs/developer/component-framework/reference/ICommand.md
@@ -1,8 +1,8 @@
---
title: ICommand (Power Apps component framework API reference) | Microsoft Docs
description: A command button control types.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/ImageObject.md b/powerapps-docs/developer/component-framework/reference/ImageObject.md
index 0193988dda..301fa97eec 100644
--- a/powerapps-docs/developer/component-framework/reference/ImageObject.md
+++ b/powerapps-docs/developer/component-framework/reference/ImageObject.md
@@ -1,8 +1,8 @@
---
title: ImageObject (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to all the properties of an image.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 08/31/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/MoneyPrecisionSource.md b/powerapps-docs/developer/component-framework/reference/MoneyPrecisionSource.md
index 5580368ae0..711577122d 100644
--- a/powerapps-docs/developer/component-framework/reference/MoneyPrecisionSource.md
+++ b/powerapps-docs/developer/component-framework/reference/MoneyPrecisionSource.md
@@ -1,8 +1,8 @@
---
title: MoneyPrecisionSource (Power Apps component framework API reference)| Microsoft Docs
description: Enumeration for money precision source.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/OptionDescriptor.md b/powerapps-docs/developer/component-framework/reference/OptionDescriptor.md
index 2d418ff042..223f438d8d 100644
--- a/powerapps-docs/developer/component-framework/reference/OptionDescriptor.md
+++ b/powerapps-docs/developer/component-framework/reference/OptionDescriptor.md
@@ -1,8 +1,8 @@
---
title: OptionDescriptor (Power Apps component framework API reference)| Microsoft Docs
description: Optionset object of the attribute.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/attributemetadata.md b/powerapps-docs/developer/component-framework/reference/attributemetadata.md
index bd13775ae0..7d7125b52a 100644
--- a/powerapps-docs/developer/component-framework/reference/attributemetadata.md
+++ b/powerapps-docs/developer/component-framework/reference/attributemetadata.md
@@ -1,8 +1,8 @@
---
title: AttributeMetadata (Power Apps component framework API reference) | Microsoft Docs
description: Provides all the information about attributes/columns definitions.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 07/20/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/attributetype.md b/powerapps-docs/developer/component-framework/reference/attributetype.md
index 60371ca395..0deefc6541 100644
--- a/powerapps-docs/developer/component-framework/reference/attributetype.md
+++ b/powerapps-docs/developer/component-framework/reference/attributetype.md
@@ -1,8 +1,8 @@
---
title: AttributeType (Power Apps component framework API reference) | Microsoft Docs
description: Provides all the information about AttributeType.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/client.md b/powerapps-docs/developer/component-framework/reference/client.md
index f4ba601249..e0f1481801 100644
--- a/powerapps-docs/developer/component-framework/reference/client.md
+++ b/powerapps-docs/developer/component-framework/reference/client.md
@@ -1,8 +1,8 @@
---
title: Client (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to the methods to determine which client is being used, whether the client is connected to server, and what kind of device is being used.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/client/getclient.md b/powerapps-docs/developer/component-framework/reference/client/getclient.md
index 93ec73f55c..967053ccbf 100644
--- a/powerapps-docs/developer/component-framework/reference/client/getclient.md
+++ b/powerapps-docs/developer/component-framework/reference/client/getclient.md
@@ -1,8 +1,8 @@
---
title: getClient (Power Apps component framework API reference) | Microsoft Docs
description: Returns a value to indicate which client the script is executing in.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/client/getformfactor.md b/powerapps-docs/developer/component-framework/reference/client/getformfactor.md
index 810819f5d9..068dd130be 100644
--- a/powerapps-docs/developer/component-framework/reference/client/getformfactor.md
+++ b/powerapps-docs/developer/component-framework/reference/client/getformfactor.md
@@ -1,8 +1,8 @@
---
title: getFormFactor (Power Apps component framework API reference) | Microsoft Docs
description: Returns information about the kind of device the user is using.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/client/isNetworkAvailable.md b/powerapps-docs/developer/component-framework/reference/client/isNetworkAvailable.md
index 7598f0b0ae..b98cd48a86 100644
--- a/powerapps-docs/developer/component-framework/reference/client/isNetworkAvailable.md
+++ b/powerapps-docs/developer/component-framework/reference/client/isNetworkAvailable.md
@@ -1,8 +1,8 @@
---
title: isNetworkAvailable (Power Apps component framework API reference) | Microsoft Docs
description: Returns information whether the network is available or not.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 08/29/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/client/isoffline.md b/powerapps-docs/developer/component-framework/reference/client/isoffline.md
index 05bada9659..a6bff31c7e 100644
--- a/powerapps-docs/developer/component-framework/reference/client/isoffline.md
+++ b/powerapps-docs/developer/component-framework/reference/client/isoffline.md
@@ -1,8 +1,8 @@
---
title: isOffline (Power Apps component framework API reference) | Microsoft Docs
description: Returns the information whether the server is online or offline.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/column.md b/powerapps-docs/developer/component-framework/reference/column.md
index 16125f5d91..2c5b3ab209 100644
--- a/powerapps-docs/developer/component-framework/reference/column.md
+++ b/powerapps-docs/developer/component-framework/reference/column.md
@@ -1,8 +1,8 @@
---
title: Column in Microsoft Dataverse (Power Apps component framework API reference) | Microsoft Docs
description: Learn how to use different methods and properties available for column in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/columninfo.md b/powerapps-docs/developer/component-framework/reference/columninfo.md
index 3065826ae3..1027664559 100644
--- a/powerapps-docs/developer/component-framework/reference/columninfo.md
+++ b/powerapps-docs/developer/component-framework/reference/columninfo.md
@@ -1,8 +1,8 @@
---
title: ColumnInfo (Power Apps component framework API reference) | Microsoft Docs
description: Provides column information.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/conditionexpression.md b/powerapps-docs/developer/component-framework/reference/conditionexpression.md
index b9e035960f..04f5d9dc23 100644
--- a/powerapps-docs/developer/component-framework/reference/conditionexpression.md
+++ b/powerapps-docs/developer/component-framework/reference/conditionexpression.md
@@ -1,8 +1,8 @@
---
title: ConditionExpression (Power Apps component framework API reference)| Microsoft Docs
description: Learn how to use different methods and properties available for ConditionExpression in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/context.md b/powerapps-docs/developer/component-framework/reference/context.md
index 002863f0c1..714ab5fb54 100644
--- a/powerapps-docs/developer/component-framework/reference/context.md
+++ b/powerapps-docs/developer/component-framework/reference/context.md
@@ -1,9 +1,9 @@
---
title: Context (Power Apps component framework API reference) | Microsoft Docs
description: Provides all the properties and methods available in the Power Apps component framework
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+author: anuitz
+ms.author: anuitz
+ms.date: 06/16/2025
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -28,6 +28,12 @@ Model-driven apps, canvas apps, & portals.
[!INCLUDE [client-description](includes/client-description.md)]
**Type**: [Client](client.md)
+### copilot
+
+[!INCLUDE [copilot-description](includes/copilot-description.md)]
+
+**Type**: [Copilot](copilot.md)
+
### device
[!INCLUDE [device-description](includes/device-description.md)]
diff --git a/powerapps-docs/developer/component-framework/reference/control.md b/powerapps-docs/developer/component-framework/reference/control.md
index 4f6f308a2c..6f76e082dd 100644
--- a/powerapps-docs/developer/component-framework/reference/control.md
+++ b/powerapps-docs/developer/component-framework/reference/control.md
@@ -1,9 +1,9 @@
---
title: StandardControl (Power Apps component framework API reference) | MicrosoftDocs
description: Provides properties and methods to initiate, update, destroy and perform various actions to build a component.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+author: anuitz
+ms.author: anuitz
+ms.date: 12/04/2024
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
diff --git a/powerapps-docs/developer/component-framework/reference/control/destroy.md b/powerapps-docs/developer/component-framework/reference/control/destroy.md
index c7d660ed76..9d44554076 100644
--- a/powerapps-docs/developer/component-framework/reference/control/destroy.md
+++ b/powerapps-docs/developer/component-framework/reference/control/destroy.md
@@ -1,8 +1,8 @@
---
title: "StandardControl.destroy (Power Apps component framework API reference) | MicrosoftDocs"
description: This method is invoked when the component is to be removed from the DOM tree. Use it for the cleanup and to release any memory that the component is using.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/control/getoutputs.md b/powerapps-docs/developer/component-framework/reference/control/getoutputs.md
index 2d316570a3..9f77f30584 100644
--- a/powerapps-docs/developer/component-framework/reference/control/getoutputs.md
+++ b/powerapps-docs/developer/component-framework/reference/control/getoutputs.md
@@ -1,8 +1,8 @@
---
title: "StandardControl.getOutputs (Power Apps component framework API reference) | MicrosoftDocs"
description: This method is called by the framework before a component receives the new data. Returns an object based on nomenclature defined in manifest, expecting objects[s] for the property marked as bound.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/control/getoutputschema.md b/powerapps-docs/developer/component-framework/reference/control/getoutputschema.md
index 6d1a32759e..035f669ffb 100644
--- a/powerapps-docs/developer/component-framework/reference/control/getoutputschema.md
+++ b/powerapps-docs/developer/component-framework/reference/control/getoutputschema.md
@@ -1,8 +1,8 @@
---
title: "StandardControl.getOutputSchema (Power Apps component framework API reference) | MicrosoftDocs"
description: "Called by the framework prior to a component initialization in a standard control. Returns an object schema based on nomenclature defined in manifest, for any output property of type object."
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 11/07/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/control/init.md b/powerapps-docs/developer/component-framework/reference/control/init.md
index eab86b2ba0..edba3bf667 100644
--- a/powerapps-docs/developer/component-framework/reference/control/init.md
+++ b/powerapps-docs/developer/component-framework/reference/control/init.md
@@ -1,8 +1,8 @@
---
title: "StandardControl.init (Power Apps component framework API reference) | MicrosoftDocs"
description: Used to initialize the component instance. Components can kick off remote server calls and other initialization actions.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/control/updateview.md b/powerapps-docs/developer/component-framework/reference/control/updateview.md
index 856df638be..0523876eab 100644
--- a/powerapps-docs/developer/component-framework/reference/control/updateview.md
+++ b/powerapps-docs/developer/component-framework/reference/control/updateview.md
@@ -1,8 +1,8 @@
---
title: "StandardControl.updateView (Power Apps component framework API reference) | MicrosoftDocs"
description: This method is called for a StandardControl when any value in the property bag changes.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 03/25/2024
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/copilot.md b/powerapps-docs/developer/component-framework/reference/copilot.md
new file mode 100644
index 0000000000..d1a941e6fc
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/copilot.md
@@ -0,0 +1,41 @@
+---
+title: Copilot (Power Apps component framework API reference) (preview)
+description: Provides methods to execute registered Microsoft Copilot Studio Topics.
+author: aorth
+ms.author: aorth
+ms.date: 06/16/2025
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+
+# Copilot (Power Apps component framework API reference) (preview)
+
+[!INCLUDE [preview-note-pp](~/../shared-content/shared/preview-includes/preview-note-pp.md)]
+
+[!INCLUDE [copilot-description](includes/copilot-description.md)]
+
+## Available for
+
+Model-driven apps
+
+## Syntax
+
+`context.copilot`
+
+## Methods
+
+| Method| Description|
+| --- | --- |
+| [executeEvent](copilot/executeevent.md) | [!INCLUDE [executeevent-description](copilot/includes/executeevent-description.md)] |
+| [executePrompt](copilot/executeprompt.md) | [!INCLUDE [executeprompt-description](copilot/includes/executeprompt-description.md)] |
+
+
+### Related articles
+
+[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework overview](../overview.md)
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/reference/copilot/executeevent.md b/powerapps-docs/developer/component-framework/reference/copilot/executeevent.md
new file mode 100644
index 0000000000..9f55710d90
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/copilot/executeevent.md
@@ -0,0 +1,73 @@
+---
+title: executeEvent (Power Apps component framework API reference) (preview)
+description: Executes a Microsoft Copilot Studio topic based on the registered Event Name.
+author: adrianorth
+ms.author: aorth
+ms.date: 07/07/2025
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+
+# executeEvent (preview)
+
+[!INCLUDE [preview-note-pp](~/../shared-content/shared/preview-includes/preview-note-pp.md)]
+
+[!INCLUDE[./includes/executeevent-description.md](./includes/executeevent-description.md)]
+
+## Available for
+
+Model-driven apps
+
+## Syntax
+
+`context.copilot.executeEvent(eventName, eventParameters).then(successCallback, errorCallback);`
+
+## Parameters
+
+| Parameter Name| Type| Required | Description|
+| --- | --- | --- | --- |
+| `eventName` | string | Yes | Event Name registered in the Copilot Studio topic |
+| `eventParameters` | Unknown | Yes | Parameters needed for the event execution. These depend on what the topic does.|
+| `successCallback` | Function | Yes | A function to call when the operation succeeds.|
+| `errorCallback` | Function | Yes | A function to call when the operation fails.|
+
+## Return Value
+
+Type: `Promise<`[MCSResponse](mcsresponse.md)`>`
+
+See [Promise](https://developer.mozilla.org/docs/Web/JavaScript/reference/Global_Objects/Promise) and [MCSResponse](mcsresponse.md)
+
+## Accessing app context
+
+When an Agent API is called, context for the app is passed to the Copilot Studio topic through a set of variables. The following are context variables available as [Copilot Studio global variables](/microsoft-copilot-studio/authoring-variables-bot).
+
+[!INCLUDE [app-context-table](../../../model-driven-apps/clientapi/includes/app-context-table.md)]
+
+For example, using `Global.PA__Copilot_Model_PageContext.pageContext.id.guid` and `Global.PA__Copilot_Model_PageContext.pageContext.entityTypeName`, the form's record can be retrieved from Dataverse.
+
+[!INCLUDE [accessing-event-parameters](../../../model-driven-apps/clientapi/includes/accessing-event-parameters.md)]
+
+### Example
+
+In Microsoft Copilot Studio, where a topic is registered that accepts an ID (entity record ID) as an input parameter. Based on the input, it retrieves the related activities of that entity record and returns the results as an Copilot Studio event activity. The PCF context API enables the execution of these methods within the context of PCF controls.
+
+```javascript
+const response = await context.copilot.executeEvent(
+ "Microsoft.PowerApps.Copilot.RelatedActivities",
+ { id:"aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb"});
+```
+
+[!INCLUDE [accessing-event-parameters-response](../../../model-driven-apps/clientapi/includes/accessing-event-parameters-response.md)]
+
+
+### Related articles
+
+[Copilot](../copilot.md)
+[executePrompt](executeprompt.md)
+[Power Apps component framework API reference](../../reference/index.md)
+[Power Apps component framework overview](../../overview.md)
+
+[!INCLUDE[footer-include](../../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/reference/copilot/executeprompt.md b/powerapps-docs/developer/component-framework/reference/copilot/executeprompt.md
new file mode 100644
index 0000000000..282ce2ab15
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/copilot/executeprompt.md
@@ -0,0 +1,73 @@
+---
+title: executePrompt (Power Apps component framework API reference) (preview)
+description: Executes a Microsoft Copilot Studio topic based on the trigger queries registered in the topic.
+author: adrianorth
+ms.author: aorth
+ms.date: 06/16/2025
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+
+# executePrompt (preview)
+
+[!INCLUDE [preview-note-pp](~/../shared-content/shared/preview-includes/preview-note-pp.md)]
+
+[!INCLUDE[./includes/executeprompt-description.md](./includes/executeprompt-description.md)]
+
+## Available for
+
+Model-driven apps
+
+## Syntax
+
+`context.copilot.executeEvent(promptText).then(successCallback, errorCallback);`
+
+## Parameters
+
+| Parameter Name| Type| Required | Description|
+| --- | --- | --- | --- |
+| `promptText` | string | Yes | The text that is registered as a trigger query in the MCS topic. |
+| `successCallback` | Function | Yes | A function to call when the operation succeeds.|
+| `errorCallback` | Function | Yes | A function to call when the operation fails.|
+
+## Return Value
+
+Type: `Promise<`[MCSResponse](mcsresponse.md)`>`
+
+See [Promise](https://developer.mozilla.org/docs/Web/JavaScript/reference/Global_Objects/Promise) and [MCSResponse](mcsresponse.md)
+
+## Example
+
+In Microsoft Copilot Studio, when a topic is triggered by queries like "hello" or "hi." When `executePrompt` runs with matching `promptText`, it activates the topic and returns a Message activity with the response text.
+
+```typescript
+const response = await context.copilot.executePrompt("hello");
+```
+
+### Response
+
+```json
+[
+ {
+ "type": "message",
+ "timestamp": "2025-02-05T16:46:07.7799759+00:00",
+ "replyToId": "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
+ "attachments": [],
+ "textFormat": "markdown",
+ "text": "Hello, how can I help you today?",
+ "speak": "Hello, how can I help?"
+ }
+]
+```
+
+### Related articles
+
+[Copilot](../copilot.md)
+[executeEvent](executeevent.md)
+[Power Apps component framework API reference](../../reference/index.md)
+[Power Apps component framework overview](../../overview.md)
+
+[!INCLUDE[footer-include](../../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/reference/copilot/includes/executeevent-description.md b/powerapps-docs/developer/component-framework/reference/copilot/includes/executeevent-description.md
new file mode 100644
index 0000000000..f14865b3a6
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/copilot/includes/executeevent-description.md
@@ -0,0 +1 @@
+Executes a Microsoft Copilot Studio topic based on the registered Event Name. Returns an array of type [MCSResponse](../mcsresponse.md).
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/reference/copilot/includes/executeprompt-description.md b/powerapps-docs/developer/component-framework/reference/copilot/includes/executeprompt-description.md
new file mode 100644
index 0000000000..c0ed81bd8d
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/copilot/includes/executeprompt-description.md
@@ -0,0 +1 @@
+Executes a Microsoft Copilot Studio topic based on the trigger queries registered in the topic. Returns an array of type [MCSResponse](../mcsresponse.md).
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/reference/copilot/mcsresponse.md b/powerapps-docs/developer/component-framework/reference/copilot/mcsresponse.md
new file mode 100644
index 0000000000..7297d75dac
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/copilot/mcsresponse.md
@@ -0,0 +1,54 @@
+---
+title: "MCSResponse Interface (Power Apps component framework API reference) (preview)"
+description: The interface that describes the properties of contains data returned by the context.executeEvent and context.executePrompt methods.
+author: adrianorth
+ms.author: aorth
+ms.date: 06/16/2025
+ms.reviewer: jdaly
+ms.topic: reference
+applies_to: "Dynamics 365 (online)"
+search.audienceType:
+ - developer
+contributors:
+ - JimDaly
+---
+
+# MCSResponse Interface (Power Apps component framework API reference) (preview)
+
+[!INCLUDE [preview-note-pp](~/../shared-content/shared/preview-includes/preview-note-pp.md)]
+
+An interface that describes the data returned by the [executeEvent](executeevent.md) and [executePrompt](executeprompt.md) methods.
+
+
+
+## Properties
+
+The following table describes the `MCSResponse` properties. Only the `type` property will always be present.
+
+
+| Name| Type| Description|
+|---|---|---|
+| `type`| `string`| **Required.** The type of the response.|
+| `id`| `string`| Unique identifier for the response.|
+| `locale`| `string`| Locale information (e.g., language or region).|
+| `replyToId`| `string`| ID of the message this is replying to.|
+| `timestamp`| `string`| Timestamp of the response.|
+| `speak`| `string`| Text to be spoken by a speech synthesizer.|
+| `text`| `string`| Text content of the response.|
+| `textFormat`| `plain` \| `markdown` \| `xml` | Format of the text content.|
+| `suggestedActions` | `{ actions: any[]; to?: string[] }` | Suggested actions for the user to take.|
+| `value`| `unknown`| Custom payload or data.|
+| `valueType`| `string`| Type of the value payload.|
+| `name`| `string`| Name of the response or action.|
+| `attachmentLayout` | `list` \| `carousel` | Layout style for displaying attachments.|
+| `attachments`| [Attachment](#attachment-interface)[]| Array of attachments included in the response.|
+
+### Attachment Interface
+
+| Name| Type| Description|
+|---|---|---|
+| `content`| `unknown` | **Required.** The content of the attachment. |
+| `contentType`| `string` | Describes the type of content. |
+
+
diff --git a/powerapps-docs/developer/component-framework/reference/dataset.md b/powerapps-docs/developer/component-framework/reference/dataset.md
index f8926fed5d..cda24c1a15 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset.md
@@ -1,8 +1,8 @@
---
title: DataSet (Power Apps component framework API reference) | Microsoft Docs
description: Learn how to use different methods and properties available for DatSet in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/addColumn.md b/powerapps-docs/developer/component-framework/reference/dataset/addColumn.md
index 7a5c954380..df2147969e 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/addColumn.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/addColumn.md
@@ -1,8 +1,8 @@
---
title: addColumn (Power Apps component framework API reference) | Microsoft Docs
description: Adds column to the column set.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/clearselectedrecordids.md b/powerapps-docs/developer/component-framework/reference/dataset/clearselectedrecordids.md
index be0142b781..e2cf875e18 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/clearselectedrecordids.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/clearselectedrecordids.md
@@ -1,8 +1,8 @@
---
title: clearSelectedRecordIds (Power Apps component framework API reference) | Microsoft Docs
description: Clears the selected record ids list.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/delete.md b/powerapps-docs/developer/component-framework/reference/dataset/delete.md
index 16f4730b97..d66b9fc019 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/delete.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/delete.md
@@ -1,8 +1,8 @@
---
title: delete (Power Apps component framework API reference) | Microsoft Docs
description: Delete the records from data source.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -27,7 +27,7 @@ Canvas apps
| Parameter Name | Type | Required | description |
| -------------- | ---------- | -------- | --------------------------- |
-| ids | `string[]` | Yes | Array of IDs to be deleted. |
+| `ids` | `string[]` | Yes | Array of IDs to be deleted. |
## Return value
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/getCommands.md b/powerapps-docs/developer/component-framework/reference/dataset/getCommands.md
index 6cacd30423..6319c65dde 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/getCommands.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/getCommands.md
@@ -1,8 +1,8 @@
---
title: getCommands (Power Apps component framework API reference) | Microsoft Docs
description: The commands for this dataset.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/getDataSetCapabilities.md b/powerapps-docs/developer/component-framework/reference/dataset/getDataSetCapabilities.md
index 2350dee241..e7c4893f4f 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/getDataSetCapabilities.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/getDataSetCapabilities.md
@@ -1,8 +1,8 @@
---
title: getDataSetCapabilities (Power Apps component framework API reference) | Microsoft Docs
description: The capabilities for this dataset.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/getselectedrecordids.md b/powerapps-docs/developer/component-framework/reference/dataset/getselectedrecordids.md
index 5ebba360c8..be4846e0d6 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/getselectedrecordids.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/getselectedrecordids.md
@@ -1,8 +1,8 @@
---
title: getSelectedRecordIds (Power Apps component framework API reference) | Microsoft Docs
description: Retrieves all the selected record IDs.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/gettargetentitytype.md b/powerapps-docs/developer/component-framework/reference/dataset/gettargetentitytype.md
index 27b597a58b..7354f71139 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/gettargetentitytype.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/gettargetentitytype.md
@@ -1,8 +1,8 @@
---
title: getTargetEntityType (Power Apps component framework API reference) | Microsoft Docs
description: Returns the target table type name.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/gettitle.md b/powerapps-docs/developer/component-framework/reference/dataset/gettitle.md
index ea32b8d8f7..ba32c3ceda 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/gettitle.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/gettitle.md
@@ -1,8 +1,8 @@
---
title: getTitle (Power Apps component framework API reference) | Microsoft Docs
description: Retrieves the view display name used by the dataset property.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/getviewid.md b/powerapps-docs/developer/component-framework/reference/dataset/getviewid.md
index 9c4c465c24..8fafbaa569 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/getviewid.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/getviewid.md
@@ -1,8 +1,8 @@
---
title: getViewId (Power Apps component framework API reference) | Microsoft Docs
description: Returns the Id of view used by dataset parameter.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/includes/opendatasetitem-description.md b/powerapps-docs/developer/component-framework/reference/dataset/includes/opendatasetitem-description.md
index 641a3528e7..cd212125a4 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/includes/opendatasetitem-description.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/includes/opendatasetitem-description.md
@@ -1 +1 @@
-Open dataset item for a given EntityReference. It checks if there is a command with command button id `Mscrm.OpenRecordItem`. If exists, it executes the command, otherwise it just navigates to the associated form of the EntityReference.
+Open dataset item for a given EntityReference. It checks if there's a command with command button ID `Mscrm.OpenRecordItem`. If exists, it executes the command, otherwise it just navigates to the associated form of the EntityReference.
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/newRecord.md b/powerapps-docs/developer/component-framework/reference/dataset/newRecord.md
index 23f69f2b9f..0ecb5d4eb8 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/newRecord.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/newRecord.md
@@ -1,8 +1,8 @@
---
title: newRecord (Power Apps component framework API reference) | Microsoft Docs
description: Initialize a local record object for control to set the value. The control will need to invoke save() on the newly created record to persist the change.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/opendatasetitem.md b/powerapps-docs/developer/component-framework/reference/dataset/opendatasetitem.md
index e30787854b..87508c5fdb 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/opendatasetitem.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/opendatasetitem.md
@@ -1,8 +1,8 @@
---
title: openDatasetItem (Power Apps component framework API reference) | Microsoft Docs
-description: Open dataset item for a given EntityReference. It checks if there is a command with command button id Mscrm.OpenRecordItem.
-ms.author: hemantg
-author: HemantGaur
+description: Open dataset item for a given EntityReference. It checks if there's a command with command button ID `Mscrm.OpenRecordItem`. If exists, it executes the command, otherwise it just navigates to the associated form of the EntityReference.
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -27,7 +27,7 @@ Model-driven and canvas apps
| Parameter Name | Type | Required | description |
| --------------- | ------------------------------------------ | -------- | ------------------------------ |
-| entityReference | [Entityreference](../entityreference.md) | Yes | Reference that will be opened. |
+| entityReference | [Entityreference](../entityreference.md) | Yes | Reference that is opened. |
### Related articles
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/refresh.md b/powerapps-docs/developer/component-framework/reference/dataset/refresh.md
index e7b3c78b15..3fd0b34835 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/refresh.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/refresh.md
@@ -1,8 +1,8 @@
---
title: refresh (Power Apps component framework API reference) | Microsoft Docs
description: Refreshes the dataset based on filters, sorting, linking, new column.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/retrieveRecordCommand.md b/powerapps-docs/developer/component-framework/reference/dataset/retrieveRecordCommand.md
index 6d04cac201..c38f30dd6e 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/retrieveRecordCommand.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/retrieveRecordCommand.md
@@ -1,8 +1,8 @@
---
title: retrieveRecordCommand (Power Apps component framework API reference) | Microsoft Docs
description: Retrieve record's associated commands.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dataset/setselectedrecordids.md b/powerapps-docs/developer/component-framework/reference/dataset/setselectedrecordids.md
index 30f69304f5..c321c48014 100644
--- a/powerapps-docs/developer/component-framework/reference/dataset/setselectedrecordids.md
+++ b/powerapps-docs/developer/component-framework/reference/dataset/setselectedrecordids.md
@@ -1,8 +1,8 @@
---
title: setSelectedRecordIds (Power Apps component framework API reference) | Microsoft Docs
description: Set the ids of the selected records.
-ms.author: hemantg
-author: HemantGaur
+author: clromano
+ms.author: clromano
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/dateformattinginfo.md b/powerapps-docs/developer/component-framework/reference/dateformattinginfo.md
index 776ad8e546..e38cd2c97e 100644
--- a/powerapps-docs/developer/component-framework/reference/dateformattinginfo.md
+++ b/powerapps-docs/developer/component-framework/reference/dateformattinginfo.md
@@ -1,8 +1,8 @@
---
title: DateFormattingInfo (Power Apps component framework API reference) | Microsoft Docs
description: Provides the date formatting information for the current user.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device.md b/powerapps-docs/developer/component-framework/reference/device.md
index 4e47bddc95..50c6147589 100644
--- a/powerapps-docs/developer/component-framework/reference/device.md
+++ b/powerapps-docs/developer/component-framework/reference/device.md
@@ -1,8 +1,8 @@
---
title: Device (Power Apps component framework API reference) | Microsoft Docs
description: Provides methods to use native device capabilities.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device/captureaudio.md b/powerapps-docs/developer/component-framework/reference/device/captureaudio.md
index cb363bdd24..adee09f24c 100644
--- a/powerapps-docs/developer/component-framework/reference/device/captureaudio.md
+++ b/powerapps-docs/developer/component-framework/reference/device/captureaudio.md
@@ -1,8 +1,8 @@
---
title: CaptureAudio (Power Apps component framework API reference) | Microsoft Docs
description: Invokes the device microphone to record audio.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device/captureimage.md b/powerapps-docs/developer/component-framework/reference/device/captureimage.md
index cfc9749952..fe07d39f84 100644
--- a/powerapps-docs/developer/component-framework/reference/device/captureimage.md
+++ b/powerapps-docs/developer/component-framework/reference/device/captureimage.md
@@ -1,8 +1,8 @@
---
title: CaptureImage (Power Apps component framework API reference) | Microsoft Docs
description: Invokes the device camera to capture the image.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device/capturevideo.md b/powerapps-docs/developer/component-framework/reference/device/capturevideo.md
index bd9aae5a6a..09f2c9115b 100644
--- a/powerapps-docs/developer/component-framework/reference/device/capturevideo.md
+++ b/powerapps-docs/developer/component-framework/reference/device/capturevideo.md
@@ -1,8 +1,8 @@
---
title: CaptureVideo (Power Apps component framework API reference) | Microsoft Docs
description: Invokes the device camera to record video.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device/getbarcodevalue.md b/powerapps-docs/developer/component-framework/reference/device/getbarcodevalue.md
index b6cbb88224..21a7c9d04b 100644
--- a/powerapps-docs/developer/component-framework/reference/device/getbarcodevalue.md
+++ b/powerapps-docs/developer/component-framework/reference/device/getbarcodevalue.md
@@ -1,8 +1,8 @@
---
title: getBarcodeValue (Power Apps component framework API reference) | Microsoft Docs
description: Invokes the device camera to scan the barcode information, such as product number.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device/getcurrentposition.md b/powerapps-docs/developer/component-framework/reference/device/getcurrentposition.md
index 65626c01a2..fb2f56e27b 100644
--- a/powerapps-docs/developer/component-framework/reference/device/getcurrentposition.md
+++ b/powerapps-docs/developer/component-framework/reference/device/getcurrentposition.md
@@ -1,8 +1,8 @@
---
title: CaptureImageOptions (Power Apps component framework API reference) | Microsoft Docs
description: Returns the current location using the device geo location capability.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/device/pickfile.md b/powerapps-docs/developer/component-framework/reference/device/pickfile.md
index c41de58221..301490b69a 100644
--- a/powerapps-docs/developer/component-framework/reference/device/pickfile.md
+++ b/powerapps-docs/developer/component-framework/reference/device/pickfile.md
@@ -1,8 +1,8 @@
---
title: PickFile (Power Apps component framework API reference) | Microsoft Docs
description: Opens a window to select files for the upload.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entity.md b/powerapps-docs/developer/component-framework/reference/entity.md
index 1bfca06aaf..449a7c0fbf 100644
--- a/powerapps-docs/developer/component-framework/reference/entity.md
+++ b/powerapps-docs/developer/component-framework/reference/entity.md
@@ -1,8 +1,8 @@
---
title: Entity (Power Apps component framework API reference)| Microsoft Docs
description: Learn how to use different methods and properties available for Entity in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityformoptions.md b/powerapps-docs/developer/component-framework/reference/entityformoptions.md
index e72da98906..ee66a3cdee 100644
--- a/powerapps-docs/developer/component-framework/reference/entityformoptions.md
+++ b/powerapps-docs/developer/component-framework/reference/entityformoptions.md
@@ -1,8 +1,8 @@
---
title: EntityFormOptions (Power Apps component framework API reference)| Microsoft Docs
description: Learn how to use different methods and properties available for EntityFormOptions in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 04/17/2024
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entitymetadata.md b/powerapps-docs/developer/component-framework/reference/entitymetadata.md
index 3c674f2cf1..eb574f1270 100644
--- a/powerapps-docs/developer/component-framework/reference/entitymetadata.md
+++ b/powerapps-docs/developer/component-framework/reference/entitymetadata.md
@@ -1,8 +1,8 @@
---
title: EntityMetadata (Power Apps component framework API reference)| Microsoft Docs
description: Information about methods and properties for table definitions.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord.md b/powerapps-docs/developer/component-framework/reference/entityrecord.md
index b22c0d955c..0e21e1221f 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord.md
@@ -1,8 +1,8 @@
---
title: EntityRecord (Power Apps component framework API reference)| Microsoft Docs
description: Learn how to use different methods and properties available for EntityRecord in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 08/18/2023
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/getColumnInfo.md b/powerapps-docs/developer/component-framework/reference/entityrecord/getColumnInfo.md
index 2b9a3f2675..7955396e6b 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/getColumnInfo.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/getColumnInfo.md
@@ -1,8 +1,8 @@
---
title: getColumnInfo (Power Apps component framework API reference) | Microsoft Docs
description: Gets the current state of the column for the record.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/getformattedvalue.md b/powerapps-docs/developer/component-framework/reference/entityrecord/getformattedvalue.md
index 04577268c9..d57e0b15ee 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/getformattedvalue.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/getformattedvalue.md
@@ -1,8 +1,8 @@
---
title: getFormattedValue (Power Apps component framework API reference) | Microsoft Docs
description: Gets the current formatted value of the record column.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/getnamedreference.md b/powerapps-docs/developer/component-framework/reference/entityrecord/getnamedreference.md
index 572e81a449..280b6eb01d 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/getnamedreference.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/getnamedreference.md
@@ -1,8 +1,8 @@
---
title: getNamedReference (Power Apps component framework API reference) | Microsoft Docs
description: Gets the object that encapsulates an EntityReference as a plain object.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/getrecordid.md b/powerapps-docs/developer/component-framework/reference/entityrecord/getrecordid.md
index 661d57d164..c75fe0f752 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/getrecordid.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/getrecordid.md
@@ -1,8 +1,8 @@
---
title: GetRecordId (Power Apps component framework API reference) | Microsoft Docs
description: Gets the record ID.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/getvalue.md b/powerapps-docs/developer/component-framework/reference/entityrecord/getvalue.md
index ad9d5343ec..2a28d529fa 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/getvalue.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/getvalue.md
@@ -1,8 +1,8 @@
---
title: EntityRecord.getValue (Power Apps component framework API reference) | Microsoft Docs
description: Gets the value of the record's column.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 04/21/2023
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/isDirty.md b/powerapps-docs/developer/component-framework/reference/entityrecord/isDirty.md
index 8face08f52..ddc714306c 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/isDirty.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/isDirty.md
@@ -1,8 +1,8 @@
---
title: isDirty (Power Apps component framework API reference) | Microsoft Docs
description: Whether this record is has changed values.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/isValid.md b/powerapps-docs/developer/component-framework/reference/entityrecord/isValid.md
index d1d7fc6c39..2a9b798313 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/isValid.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/isValid.md
@@ -1,8 +1,8 @@
---
title: isValid (Power Apps component framework API reference) | Microsoft Docs
description: Whether this record is valid.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/save.md b/powerapps-docs/developer/component-framework/reference/entityrecord/save.md
index 61908e26d5..ddc8a3f3b7 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/save.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/save.md
@@ -1,8 +1,8 @@
---
title: save (Power Apps component framework API reference) | Microsoft Docs
description: Saves the record
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 04/21/2023
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityrecord/setValue.md b/powerapps-docs/developer/component-framework/reference/entityrecord/setValue.md
index e0a6f4b26c..3f4d6e9ed5 100644
--- a/powerapps-docs/developer/component-framework/reference/entityrecord/setValue.md
+++ b/powerapps-docs/developer/component-framework/reference/entityrecord/setValue.md
@@ -1,8 +1,8 @@
---
title: setValue (Power Apps component framework API reference) | Microsoft Docs
description: Set value for the column.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 04/21/2023
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/entityreference.md b/powerapps-docs/developer/component-framework/reference/entityreference.md
index 1a6457441c..ae41e0c0fd 100644
--- a/powerapps-docs/developer/component-framework/reference/entityreference.md
+++ b/powerapps-docs/developer/component-framework/reference/entityreference.md
@@ -1,8 +1,8 @@
---
title: EntityReference (Power Apps component framework API reference)| Microsoft Docs
description: Learn how to use different methods and properties available for EntityReference in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/events.md b/powerapps-docs/developer/component-framework/reference/events.md
index e25d36480b..25731e73c8 100644
--- a/powerapps-docs/developer/component-framework/reference/events.md
+++ b/powerapps-docs/developer/component-framework/reference/events.md
@@ -1,14 +1,12 @@
---
title: Events (Power Apps component framework API reference) | Microsoft Docs
-description: Provides methods to call maker-defined Power Fx events that are configured in Power Apps Studio.
-ms.author: olidum
+description: Provides methods to call events defined in a PCF. For canvas apps, makers configure these events using Power Fx. For model-driven apps, developers describe the events using JavaScript.
author: OliverDumrique
-ms.date: 11/20/2023
-ms.reviewer: olidum
+ms.author: olidum
+ms.reviewer: jdaly
+ms.date: 03/17/2025
ms.topic: reference
ms.subservice: pcf
-contributors:
- - OliverDumrique
---
# Events
@@ -17,7 +15,7 @@ contributors:
## Available for
-Canvas apps only
+Canvas apps and model-driven apps
## Syntax
@@ -27,6 +25,8 @@ Canvas apps only
[event](../manifest-schema-reference/event.md) nodes in the manifest file are built as callable methods in the `context.events` object.
+[Define Events](../events.md)
+
## Example
```JSX
@@ -40,7 +40,8 @@ return (
```
### Related articles
-[Power Apps component framework API reference](../reference/index.md)
-[Power Apps component framework overview](../overview.md)
+
+[Power Apps component framework API reference](../reference/index.md)
+[Power Apps component framework overview](../overview.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/reference/factory.md b/powerapps-docs/developer/component-framework/reference/factory.md
index 3b3e8b49f3..ffee730c5a 100644
--- a/powerapps-docs/developer/component-framework/reference/factory.md
+++ b/powerapps-docs/developer/component-framework/reference/factory.md
@@ -1,8 +1,8 @@
---
title: Factory (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods to work with Popup services.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/factory/getpopupservice.md b/powerapps-docs/developer/component-framework/reference/factory/getpopupservice.md
index 240dda4854..e2371225fc 100644
--- a/powerapps-docs/developer/component-framework/reference/factory/getpopupservice.md
+++ b/powerapps-docs/developer/component-framework/reference/factory/getpopupservice.md
@@ -1,8 +1,8 @@
---
title: getPopupService (Power Apps component framework API reference) | Microsoft Docs
description: Gets the popup service which helps to create popups and manage popups easily.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/factory/requestrender.md b/powerapps-docs/developer/component-framework/reference/factory/requestrender.md
index fec2df5d38..07406c4551 100644
--- a/powerapps-docs/developer/component-framework/reference/factory/requestrender.md
+++ b/powerapps-docs/developer/component-framework/reference/factory/requestrender.md
@@ -1,8 +1,8 @@
---
title: requestRender (Power Apps component framework API reference) | Microsoft Docs
description: Requests re-rendering of the component with the updated data.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/fileobject.md b/powerapps-docs/developer/component-framework/reference/fileobject.md
index 3b5b9f63bd..13b9df25a0 100644
--- a/powerapps-docs/developer/component-framework/reference/fileobject.md
+++ b/powerapps-docs/developer/component-framework/reference/fileobject.md
@@ -1,8 +1,8 @@
---
title: FileObject (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to all the properties of a file.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/filterexpression.md b/powerapps-docs/developer/component-framework/reference/filterexpression.md
index 2f24e1e2eb..0b0a1b266c 100644
--- a/powerapps-docs/developer/component-framework/reference/filterexpression.md
+++ b/powerapps-docs/developer/component-framework/reference/filterexpression.md
@@ -1,8 +1,8 @@
---
title: FilterExpression (Power Apps component framework API reference) | Microsoft Docs
description: An expression used to represent a filter.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/filtering.md b/powerapps-docs/developer/component-framework/reference/filtering.md
index 4b5c40e6a2..62b9205df7 100644
--- a/powerapps-docs/developer/component-framework/reference/filtering.md
+++ b/powerapps-docs/developer/component-framework/reference/filtering.md
@@ -1,8 +1,8 @@
---
title: Filtering (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods for filtering in a dataset.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/filtering/clearfilter.md b/powerapps-docs/developer/component-framework/reference/filtering/clearfilter.md
index e191532817..d73fa2c7ef 100644
--- a/powerapps-docs/developer/component-framework/reference/filtering/clearfilter.md
+++ b/powerapps-docs/developer/component-framework/reference/filtering/clearfilter.md
@@ -1,8 +1,8 @@
---
title: clearFilter (Power Apps component framework API reference) | Microsoft Docs
description: Clears the filter associated with the dataset.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/filtering/getfilter.md b/powerapps-docs/developer/component-framework/reference/filtering/getfilter.md
index da4ed066f4..77f6ec2788 100644
--- a/powerapps-docs/developer/component-framework/reference/filtering/getfilter.md
+++ b/powerapps-docs/developer/component-framework/reference/filtering/getfilter.md
@@ -1,8 +1,8 @@
---
title: getFilter (Power Apps component framework API reference) | Microsoft Docs
description: Returns the top-most filter associated with the dataset.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/filtering/setfilter.md b/powerapps-docs/developer/component-framework/reference/filtering/setfilter.md
index 4468abd78f..86be8c29e7 100644
--- a/powerapps-docs/developer/component-framework/reference/filtering/setfilter.md
+++ b/powerapps-docs/developer/component-framework/reference/filtering/setfilter.md
@@ -1,8 +1,8 @@
---
title: setFilter (Power Apps component framework API reference) | Microsoft Docs
description: Sets the top-most filter associated with the dataset.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting.md b/powerapps-docs/developer/component-framework/reference/formatting.md
index 7dd7ed51d5..cc2e184033 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting.md
@@ -1,8 +1,8 @@
---
title: Formatting (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods to work with formatting.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatDateLong.md b/powerapps-docs/developer/component-framework/reference/formatting/formatDateLong.md
index a2377782be..44213db33c 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatDateLong.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatDateLong.md
@@ -1,8 +1,8 @@
---
title: formatDateLong (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents a date in the long form. Results pattern is based on the culture. In USA it's "Abbreviated Day of week, Month dd, yyyy".
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatDateLongAbbreviated.md b/powerapps-docs/developer/component-framework/reference/formatting/formatDateLongAbbreviated.md
index 1dcc52b75b..5c3eceb490 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatDateLongAbbreviated.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatDateLongAbbreviated.md
@@ -1,8 +1,8 @@
---
title: formatDateLongAbbreviated (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents a date in the long form using abbreviation. Results pattern is based on culture. In USA it's "Abbreviated Day of week, Month dd, yyyy".
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatDateShort.md b/powerapps-docs/developer/component-framework/reference/formatting/formatDateShort.md
index cf429026fd..a9e7512a05 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatDateShort.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatDateShort.md
@@ -1,8 +1,8 @@
---
title: formatDateShort (Power Apps component framework API reference) | Microsoft Docs
description: Returns a string represents the datetime value after being formatted. Result pattern is based on culture. In USA it is represented as MM/DD/YYYY.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatDateYearMonth.md b/powerapps-docs/developer/component-framework/reference/formatting/formatDateYearMonth.md
index 60da236b55..1ec979f258 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatDateYearMonth.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatDateYearMonth.md
@@ -2,8 +2,8 @@
title: formatDateYearMonth (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents a date in the year month format.
keywords:
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatDecimal.md b/powerapps-docs/developer/component-framework/reference/formatting/formatDecimal.md
index a12f023aaf..ab4b53a448 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatDecimal.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatDecimal.md
@@ -1,8 +1,8 @@
---
title: formatDecimal (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents the decimal value after being formatted.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatInteger.md b/powerapps-docs/developer/component-framework/reference/formatting/formatInteger.md
index 0935f0d4f4..4d5b7abcd9 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatInteger.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatInteger.md
@@ -2,8 +2,8 @@
title: formatInteger (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string represents a given integer value.
keywords:
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatLanguage.md b/powerapps-docs/developer/component-framework/reference/formatting/formatLanguage.md
index 1b3f92baaa..1500af95da 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatLanguage.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatLanguage.md
@@ -1,8 +1,8 @@
---
title: formatLanguage (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents a given language.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatTime.md b/powerapps-docs/developer/component-framework/reference/formatting/formatTime.md
index e151726433..699ea4e03e 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatTime.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatTime.md
@@ -1,8 +1,8 @@
---
title: formatTime (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents the datetime value after being formatted.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatUTCDateTimeToUserDate.md b/powerapps-docs/developer/component-framework/reference/formatting/formatUTCDateTimeToUserDate.md
index 08b4cfa29a..2faa9b0241 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatUTCDateTimeToUserDate.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatUTCDateTimeToUserDate.md
@@ -1,8 +1,8 @@
---
title: formatUTCDateTimeToUserDate (Power Apps component framework API reference) | Microsoft Docs
description: Returns a date that represents the UTC value after being formatted.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatUserDateTimeToUTC.md b/powerapps-docs/developer/component-framework/reference/formatting/formatUserDateTimeToUTC.md
index 5417fd58a7..92b8bd3299 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatUserDateTimeToUTC.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatUserDateTimeToUTC.md
@@ -1,8 +1,8 @@
---
title: formatUserDateTimeToUTC (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents the UTC datetime value after being formatted.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatUserInput.md b/powerapps-docs/developer/component-framework/reference/formatting/formatUserInput.md
index 98254f8131..fb7409e769 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatUserInput.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatUserInput.md
@@ -1,8 +1,8 @@
---
title: formatUserInput (Power Apps component framework API reference) | Microsoft Docs
description: Returns formatter user input based on the passed in attribute type. If type is not recognized, returns the input itself.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatcurrency.md b/powerapps-docs/developer/component-framework/reference/formatting/formatcurrency.md
index e6f32d0596..66f4e8275b 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatcurrency.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatcurrency.md
@@ -1,8 +1,8 @@
---
title: FormatCurrency (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents the currency value after being formatted.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/formatdateasfilterstringinutc.md b/powerapps-docs/developer/component-framework/reference/formatting/formatdateasfilterstringinutc.md
index ab9e3fa432..417dd77187 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/formatdateasfilterstringinutc.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/formatdateasfilterstringinutc.md
@@ -1,8 +1,8 @@
---
title: formatDateAsFilterStringUTC (Power Apps component framework API reference) | Microsoft Docs
description: Returns a formatted string that represents a date in YYYY-MM-DD standard UTC format. Results pattern is based on standard UTC format.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/getWeekOfYear.md b/powerapps-docs/developer/component-framework/reference/formatting/getWeekOfYear.md
index 5d7edf5cdb..2651c05304 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/getWeekOfYear.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/getWeekOfYear.md
@@ -1,8 +1,8 @@
---
title: getWeekOfYear (Power Apps component framework API reference) | Microsoft Docs
description: Gets the ISO week number of the year for a given date. Range is from 1-53.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/formatting/parseDateFromInput.md b/powerapps-docs/developer/component-framework/reference/formatting/parseDateFromInput.md
index 25c265a83d..daab6d1224 100644
--- a/powerapps-docs/developer/component-framework/reference/formatting/parseDateFromInput.md
+++ b/powerapps-docs/developer/component-framework/reference/formatting/parseDateFromInput.md
@@ -1,8 +1,8 @@
---
title: parseDateFromInput (Power Apps component framework API reference) | Microsoft Docs
description: Returns parsed string as date.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/ilinkentityexposedexpression.md b/powerapps-docs/developer/component-framework/reference/ilinkentityexposedexpression.md
index 7cd024570c..029c2bcf31 100644
--- a/powerapps-docs/developer/component-framework/reference/ilinkentityexposedexpression.md
+++ b/powerapps-docs/developer/component-framework/reference/ilinkentityexposedexpression.md
@@ -1,8 +1,8 @@
---
title: ILinkEntityExposedExpression (Power Apps component framework API reference) | Microsoft Docs
description: Learn how to use different methods and properties available for ILinkEntityExposedExpression in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/includes/copilot-description.md b/powerapps-docs/developer/component-framework/reference/includes/copilot-description.md
new file mode 100644
index 0000000000..81c6808b1b
--- /dev/null
+++ b/powerapps-docs/developer/component-framework/reference/includes/copilot-description.md
@@ -0,0 +1 @@
+Provides methods to execute registered Microsoft Copilot Studio Topics.
\ No newline at end of file
diff --git a/powerapps-docs/developer/component-framework/reference/includes/events-description.md b/powerapps-docs/developer/component-framework/reference/includes/events-description.md
index 79a6a56de7..0e61a58f50 100644
--- a/powerapps-docs/developer/component-framework/reference/includes/events-description.md
+++ b/powerapps-docs/developer/component-framework/reference/includes/events-description.md
@@ -1 +1 @@
-Provides methods to call maker-defined Power Fx events that are configured in Power Apps Studio.
+Provides methods to call events defined in a PCF. For canvas apps, makers configure these events using Power Fx. For model-driven apps, developers describe the events using JavaScript
diff --git a/powerapps-docs/developer/component-framework/reference/includes/react-control-description.md b/powerapps-docs/developer/component-framework/reference/includes/react-control-description.md
index e2f32fa9cc..71e51d2279 100644
--- a/powerapps-docs/developer/component-framework/reference/includes/react-control-description.md
+++ b/powerapps-docs/developer/component-framework/reference/includes/react-control-description.md
@@ -1,3 +1,3 @@
Provides properties and methods to initiate, update, destroy and perform various actions to build a component using a React control.
-This control is part of the [React controls & platform libraries (Preview) ](../../react-controls-platform-libraries.md).
\ No newline at end of file
+This control is part of the [React controls & platform libraries](../../react-controls-platform-libraries.md).
diff --git a/powerapps-docs/developer/component-framework/reference/index.md b/powerapps-docs/developer/component-framework/reference/index.md
index 7234516218..fc0149f751 100644
--- a/powerapps-docs/developer/component-framework/reference/index.md
+++ b/powerapps-docs/developer/component-framework/reference/index.md
@@ -1,9 +1,9 @@
---
title: "Power Apps component framework API reference | MicrosoftDocs"
description: "The topic provides Power Apps component framework API reference."
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+ms.author: anuitz
+author: anuitz
+ms.date: 03/24/2025
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -58,7 +58,7 @@ This section contains reference documentation for creating code components using
|[PopupService](popupservice.md)|[!INCLUDE [popupservice-description](includes/popupservice-description.md)]|Model-driven and canvas apps|
|[Position](position.md)|[!INCLUDE [position-description](includes/position-description.md)]|Model-driven and canvas apps|
|[Property](property.md)|[!INCLUDE [property-description](includes/property-description.md)]|Model-driven and canvas apps|
-|[ReactControl (Preview)](react-control.md)|[!INCLUDE [react-control-description](includes/react-control-description.md)]|Model-driven and canvas apps|
+|[ReactControl](react-control.md)|[!INCLUDE [react-control-description](includes/react-control-description.md)]|Model-driven and canvas apps|
|[Resources](resources.md)|[!INCLUDE [resources-description](includes/resources-description.md)]|Model-driven and canvas apps|
|[RetrieveMultipleResponse](retrievemultipleresponse.md)|[!INCLUDE [retrievemultipleresponse-description](includes/retrievemultipleresponse-description.md)]|Model-driven apps|
|[Security Values](securityvalues.md)|[!INCLUDE [securityvalues-description](includes/securityvalues-description.md)]|Model-driven apps|
diff --git a/powerapps-docs/developer/component-framework/reference/linking.md b/powerapps-docs/developer/component-framework/reference/linking.md
index bc14b62a9c..6869d4274f 100644
--- a/powerapps-docs/developer/component-framework/reference/linking.md
+++ b/powerapps-docs/developer/component-framework/reference/linking.md
@@ -1,8 +1,8 @@
---
title: Linking (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods to determine which table is linked and to get all the tables linked.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/linking/addlinkedentity.md b/powerapps-docs/developer/component-framework/reference/linking/addlinkedentity.md
index c374ac094b..96e957ac8b 100644
--- a/powerapps-docs/developer/component-framework/reference/linking/addlinkedentity.md
+++ b/powerapps-docs/developer/component-framework/reference/linking/addlinkedentity.md
@@ -1,8 +1,8 @@
---
title: addLinkedEntity (Power Apps component framework API reference) | Microsoft Docs
description: Adds a new linked table relationship with the existing query primary table.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/linking/getlinkedentities.md b/powerapps-docs/developer/component-framework/reference/linking/getlinkedentities.md
index 7963abb582..22f6c51bd7 100644
--- a/powerapps-docs/developer/component-framework/reference/linking/getlinkedentities.md
+++ b/powerapps-docs/developer/component-framework/reference/linking/getlinkedentities.md
@@ -1,8 +1,8 @@
---
title: getLinkedEntities (Power Apps component framework API reference) | Microsoft Docs
description: Returns all the linked tables information.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/lookupvalue.md b/powerapps-docs/developer/component-framework/reference/lookupvalue.md
index 6c49262343..89504d8ec7 100644
--- a/powerapps-docs/developer/component-framework/reference/lookupvalue.md
+++ b/powerapps-docs/developer/component-framework/reference/lookupvalue.md
@@ -1,8 +1,8 @@
---
title: LookupValue (Power Apps component framework API reference) | Microsoft Docs
description: Learn how to use different properties available for LookupValue in Power Apps component framework.
-ms.author: rarattay
-author: rarattay
+author: anuitz
+ms.author: anuitz
ms.date: 04/17/2024
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/metadata.md b/powerapps-docs/developer/component-framework/reference/metadata.md
index 386e66495c..0bf5ec5afc 100644
--- a/powerapps-docs/developer/component-framework/reference/metadata.md
+++ b/powerapps-docs/developer/component-framework/reference/metadata.md
@@ -1,8 +1,8 @@
---
title: Metadata (Power Apps component framework API reference) | Microsoft Docs
description: Provides all the information about column definitions.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/mode.md b/powerapps-docs/developer/component-framework/reference/mode.md
index 84b6dfcbec..bef5272db2 100644
--- a/powerapps-docs/developer/component-framework/reference/mode.md
+++ b/powerapps-docs/developer/component-framework/reference/mode.md
@@ -1,8 +1,8 @@
---
title: Mode (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to methods to get the information about the current state of the code component.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/mode/setcontrolstate.md b/powerapps-docs/developer/component-framework/reference/mode/setcontrolstate.md
index 6282fda6aa..c9c3f9658a 100644
--- a/powerapps-docs/developer/component-framework/reference/mode/setcontrolstate.md
+++ b/powerapps-docs/developer/component-framework/reference/mode/setcontrolstate.md
@@ -1,8 +1,8 @@
---
title: setControlState (Power Apps component framework API reference) | Microsoft Docs
description: Set component state so that it will be stored in one session.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/mode/setfullscreen.md b/powerapps-docs/developer/component-framework/reference/mode/setfullscreen.md
index c9b0d9f4e5..cec205ca10 100644
--- a/powerapps-docs/developer/component-framework/reference/mode/setfullscreen.md
+++ b/powerapps-docs/developer/component-framework/reference/mode/setfullscreen.md
@@ -1,8 +1,8 @@
---
title: setFullScreen (Power Apps component framework API reference) | Microsoft Docs
description: Make the component full screen.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/mode/trackcontainerresize.md b/powerapps-docs/developer/component-framework/reference/mode/trackcontainerresize.md
index 37a179c20a..5b142deaf7 100644
--- a/powerapps-docs/developer/component-framework/reference/mode/trackcontainerresize.md
+++ b/powerapps-docs/developer/component-framework/reference/mode/trackcontainerresize.md
@@ -1,8 +1,8 @@
---
title: TrackContainerResize (Power Apps component framework API reference) | Microsoft Docs
description: Determines the container sizing if the component needs to react.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation.md b/powerapps-docs/developer/component-framework/reference/navigation.md
index ad4fe94f7f..70292a5c51 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation.md
@@ -1,8 +1,8 @@
---
title: Navigation (Power Apps component framework API reference) | Microsoft Docs
description: Provides navigation-related methods.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openalertdialog.md b/powerapps-docs/developer/component-framework/reference/navigation/openalertdialog.md
index f8e98e4dba..0a637e07d9 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openalertdialog.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openalertdialog.md
@@ -1,8 +1,8 @@
---
title: openAlertDialog (Power Apps component framework API reference) | Microsoft Docs
description: Displays an alert dialog containing a message and a button.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openconfirmdialog.md b/powerapps-docs/developer/component-framework/reference/navigation/openconfirmdialog.md
index 377d1f9aab..98297533f8 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openconfirmdialog.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openconfirmdialog.md
@@ -1,8 +1,8 @@
---
title: openConfirmDialog (Power Apps component framework API reference) | Microsoft Docs
description: Displays a confirmation dialog box containing a message and two buttons.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openerrordialog.md b/powerapps-docs/developer/component-framework/reference/navigation/openerrordialog.md
index 9575fead87..0c447e7650 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openerrordialog.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openerrordialog.md
@@ -1,8 +1,8 @@
---
title: openErrorDialog (Power Apps component framework API reference) | Microsoft Docs
description: Displays an error dialog.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openfile.md b/powerapps-docs/developer/component-framework/reference/navigation/openfile.md
index 0dd452fc0c..e35fb0f4c1 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openfile.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openfile.md
@@ -1,8 +1,8 @@
---
title: openFile (Power Apps component framework API reference) | Microsoft Docs
description: Opens a file.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 08/22/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openform.md b/powerapps-docs/developer/component-framework/reference/navigation/openform.md
index 740daf4ba2..e98fcd4912 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openform.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openform.md
@@ -1,8 +1,8 @@
---
title: openForm (Power Apps component framework API reference) | Microsoft Docs
description: Opens a form or a quick create form.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openurl.md b/powerapps-docs/developer/component-framework/reference/navigation/openurl.md
index a2dd5bae67..ebaee99a94 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openurl.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openurl.md
@@ -1,8 +1,8 @@
---
title: openUrl (Power Apps component framework API reference) | Microsoft Docs
description: Opens a url, including file urls.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/navigation/openwebresource.md b/powerapps-docs/developer/component-framework/reference/navigation/openwebresource.md
index 17f4b054a9..ca13051d25 100644
--- a/powerapps-docs/developer/component-framework/reference/navigation/openwebresource.md
+++ b/powerapps-docs/developer/component-framework/reference/navigation/openwebresource.md
@@ -1,8 +1,8 @@
---
title: openWebResource (Power Apps component framework API reference) | Microsoft Docs
description: Opens a HTML web resource.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/numberformattinginfo.md b/powerapps-docs/developer/component-framework/reference/numberformattinginfo.md
index 8ffcd325f6..3b83e1afb0 100644
--- a/powerapps-docs/developer/component-framework/reference/numberformattinginfo.md
+++ b/powerapps-docs/developer/component-framework/reference/numberformattinginfo.md
@@ -1,8 +1,8 @@
---
title: NumberFormattingInfo (Power Apps component framework API reference) | Microsoft Docs
description: The interface for the Organization System Settings Number Format info exposed to a code component.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/paging.md b/powerapps-docs/developer/component-framework/reference/paging.md
index 8e989dcebb..7a33a422a2 100644
--- a/powerapps-docs/developer/component-framework/reference/paging.md
+++ b/powerapps-docs/developer/component-framework/reference/paging.md
@@ -1,8 +1,8 @@
---
title: Paging (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods to work with paging.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 06/14/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/paging/loadExactPage.md b/powerapps-docs/developer/component-framework/reference/paging/loadExactPage.md
index ca827e673a..3dff7453ec 100644
--- a/powerapps-docs/developer/component-framework/reference/paging/loadExactPage.md
+++ b/powerapps-docs/developer/component-framework/reference/paging/loadExactPage.md
@@ -1,8 +1,8 @@
---
title: loadExactPage (Power Apps component framework API reference) | Microsoft Docs
description: Request the exact page of results to be loaded.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/paging/loadnextpage.md b/powerapps-docs/developer/component-framework/reference/paging/loadnextpage.md
index 5887e0230d..5e885d39f1 100644
--- a/powerapps-docs/developer/component-framework/reference/paging/loadnextpage.md
+++ b/powerapps-docs/developer/component-framework/reference/paging/loadnextpage.md
@@ -1,8 +1,8 @@
---
title: loadNextPage (Power Apps component framework API reference) | Microsoft Docs
description: Request the next page of results to be loaded.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/paging/loadpreviouspage.md b/powerapps-docs/developer/component-framework/reference/paging/loadpreviouspage.md
index a815f6be54..5ead74f480 100644
--- a/powerapps-docs/developer/component-framework/reference/paging/loadpreviouspage.md
+++ b/powerapps-docs/developer/component-framework/reference/paging/loadpreviouspage.md
@@ -1,8 +1,8 @@
---
title: loadPreviousPage (Power Apps component framework API reference) | Microsoft Docs
description: Request the previous page of results to be loaded.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/paging/reset.md b/powerapps-docs/developer/component-framework/reference/paging/reset.md
index f82ee28ebd..74143504c1 100644
--- a/powerapps-docs/developer/component-framework/reference/paging/reset.md
+++ b/powerapps-docs/developer/component-framework/reference/paging/reset.md
@@ -1,8 +1,8 @@
---
title: reset (Power Apps component framework API reference) | Microsoft Docs
description: Reload the results from the server, and reset to page 1.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/paging/setpagesize.md b/powerapps-docs/developer/component-framework/reference/paging/setpagesize.md
index 198e679e05..d5f1df88ac 100644
--- a/powerapps-docs/developer/component-framework/reference/paging/setpagesize.md
+++ b/powerapps-docs/developer/component-framework/reference/paging/setpagesize.md
@@ -1,8 +1,8 @@
---
title: setPageSize (Power Apps component framework API reference) | Microsoft Docs
description: Sets the number of results to return per page on the next data refresh.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/pickfileoptions.md b/powerapps-docs/developer/component-framework/reference/pickfileoptions.md
index 76fffc8680..35eacfafc5 100644
--- a/powerapps-docs/developer/component-framework/reference/pickfileoptions.md
+++ b/powerapps-docs/developer/component-framework/reference/pickfileoptions.md
@@ -1,8 +1,8 @@
---
title: PickFileOptions (Power Apps component framework API reference)| Microsoft Docs
description: Provides set of options for the pickFile options parameter.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popup.md b/powerapps-docs/developer/component-framework/reference/popup.md
index 7e4cbb6303..4739a06725 100644
--- a/powerapps-docs/developer/component-framework/reference/popup.md
+++ b/powerapps-docs/developer/component-framework/reference/popup.md
@@ -1,8 +1,8 @@
---
title: Popup (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to get all the information about the popup.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice.md b/powerapps-docs/developer/component-framework/reference/popupservice.md
index 2ff342612f..0bd4c724f6 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice.md
@@ -1,8 +1,8 @@
---
title: PopupService (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods to create and manage popups.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/closepopup.md b/powerapps-docs/developer/component-framework/reference/popupservice/closepopup.md
index 2c3da93173..cb5664b7ff 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/closepopup.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/closepopup.md
@@ -1,8 +1,8 @@
---
title: closePopup (Power Apps component framework API reference) | Microsoft Docs
description: Closes an existing popup in the service with the given name. Does nothing if popup does not exist yet.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/createpopup.md b/powerapps-docs/developer/component-framework/reference/popupservice/createpopup.md
index be55fee847..c306b75305 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/createpopup.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/createpopup.md
@@ -1,8 +1,8 @@
---
title: createPopup (Power Apps component framework API reference) | Microsoft Docs
description: Creates a new popup element.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/deletepopup.md b/powerapps-docs/developer/component-framework/reference/popupservice/deletepopup.md
index 09bb33a486..7cdf7d42c0 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/deletepopup.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/deletepopup.md
@@ -1,8 +1,8 @@
---
title: deletePopup (Power Apps component framework API reference) | Microsoft Docs
description: Removes the referenced popup from the popup service and unregister the service.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/getpopupsid.md b/powerapps-docs/developer/component-framework/reference/popupservice/getpopupsid.md
index ab1a03655b..5f29520674 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/getpopupsid.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/getpopupsid.md
@@ -1,8 +1,8 @@
---
title: getPopupsId (Power Apps component framework API reference) | Microsoft Docs
description: Gets the currently set popup Id.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/openpopup.md b/powerapps-docs/developer/component-framework/reference/popupservice/openpopup.md
index b5c18cef03..5de1022264 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/openpopup.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/openpopup.md
@@ -1,8 +1,8 @@
---
title: openPopup (Power Apps component framework API reference) | Microsoft Docs
description: Opens an existing popup in the service with the given name. Does nothing if popup does not exist yet.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/setpopupsid.md b/powerapps-docs/developer/component-framework/reference/popupservice/setpopupsid.md
index 840830eccc..b2a827ba67 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/setpopupsid.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/setpopupsid.md
@@ -1,8 +1,8 @@
---
title: setPopupsId (Power Apps component framework API reference) | Microsoft Docs
description: Sets the ID (on the DOM and in the system) for the root popup element.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/popupservice/updatepopup.md b/powerapps-docs/developer/component-framework/reference/popupservice/updatepopup.md
index 6544b7df46..6a75c3e43f 100644
--- a/powerapps-docs/developer/component-framework/reference/popupservice/updatepopup.md
+++ b/powerapps-docs/developer/component-framework/reference/popupservice/updatepopup.md
@@ -1,8 +1,8 @@
---
title: updatePopup (Power Apps component framework API reference) | Microsoft Docs
description: Updates an existing popup in the service with the given name. Does nothing if popup does not exist yet.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/position.md b/powerapps-docs/developer/component-framework/reference/position.md
index d4f254eedf..d8fd1108d3 100644
--- a/powerapps-docs/developer/component-framework/reference/position.md
+++ b/powerapps-docs/developer/component-framework/reference/position.md
@@ -1,8 +1,8 @@
---
title: Position (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to get geographical information from context.device.getCurrentPosition method.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/property.md b/powerapps-docs/developer/component-framework/reference/property.md
index 04b40bfd9f..cd3cafde70 100644
--- a/powerapps-docs/developer/component-framework/reference/property.md
+++ b/powerapps-docs/developer/component-framework/reference/property.md
@@ -1,8 +1,8 @@
---
title: Property (Power Apps component framework API reference) | Microsoft Docs
description: Interface for context.parameters.
-ms.author: hemantg
-author: HemantGaur
+ms.author: anuitz
+author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/react-control.md b/powerapps-docs/developer/component-framework/reference/react-control.md
index b306632842..93a6d0e644 100644
--- a/powerapps-docs/developer/component-framework/reference/react-control.md
+++ b/powerapps-docs/developer/component-framework/reference/react-control.md
@@ -1,9 +1,9 @@
---
title: ReactControl (Power Apps component framework API reference) | MicrosoftDocs
description: Provides properties and methods to initiate, update, destroy and perform various actions to build a component using a ReactControl.
-ms.author: hemantg
-author: HemantGaur
-ms.date: 05/27/2022
+author: anuitz
+ms.author: anuitz
+ms.date: 12/04/2024
ms.reviewer: jdaly
ms.topic: reference
ms.subservice: pcf
@@ -11,7 +11,7 @@ contributors:
- JimDaly
---
-# ReactControl (Preview)
+# ReactControl
[!INCLUDE [react-control-description](includes/react-control-description.md)]
@@ -30,7 +30,7 @@ Model-driven and canvas apps
### Related articles
-[React controls & platform libraries (Preview) ](../react-controls-platform-libraries.md)
+[React controls & platform libraries](../react-controls-platform-libraries.md)
[Power Apps component framework API reference](../reference/index.md)
[Power Apps component framework overview](../overview.md)
diff --git a/powerapps-docs/developer/component-framework/reference/react-control/destroy.md b/powerapps-docs/developer/component-framework/reference/react-control/destroy.md
index cbb7f40f07..d522448035 100644
--- a/powerapps-docs/developer/component-framework/reference/react-control/destroy.md
+++ b/powerapps-docs/developer/component-framework/reference/react-control/destroy.md
@@ -1,8 +1,8 @@
---
title: "ReactControl.destroy (Power Apps component framework API reference) | MicrosoftDocs"
description: This method is invoked in a ReactControl when the component is to be removed from the DOM tree. Use it for the cleanup and to release any memory that the component is using.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -34,7 +34,7 @@ public destroy(): void
### Related articles
-[React controls & platform libraries (Preview) ](../../react-controls-platform-libraries.md)
+[React controls & platform libraries](../../react-controls-platform-libraries.md)
[ReactControl](../react-control.md)
[Power Apps component framework API reference](../../reference/index.md)
[Power Apps component framework overview](../../overview.md)
diff --git a/powerapps-docs/developer/component-framework/reference/react-control/getOutputs.md b/powerapps-docs/developer/component-framework/reference/react-control/getOutputs.md
index cb4a4038fb..a18b97950c 100644
--- a/powerapps-docs/developer/component-framework/reference/react-control/getOutputs.md
+++ b/powerapps-docs/developer/component-framework/reference/react-control/getOutputs.md
@@ -1,8 +1,8 @@
---
title: "ReactControl.getOutputs (Power Apps component framework API reference) | MicrosoftDocs"
description: It is called by the framework for a ReactControl prior to a component receiving the new data. Returns an object based on nomenclature defined in manifest, expecting objects[s] for the property marked as bound.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -47,7 +47,7 @@ public getOutputs(): IOutputs
### Related articles
-[React controls & platform libraries (Preview) ](../../react-controls-platform-libraries.md)
+[React controls & platform libraries](../../react-controls-platform-libraries.md)
[ReactControl](../react-control.md)
[Power Apps component framework API reference](../../reference/index.md)
[Power Apps component framework overview](../../overview.md)
diff --git a/powerapps-docs/developer/component-framework/reference/react-control/getoutputschema.md b/powerapps-docs/developer/component-framework/reference/react-control/getoutputschema.md
index e44e08071e..8a511bf71a 100644
--- a/powerapps-docs/developer/component-framework/reference/react-control/getoutputschema.md
+++ b/powerapps-docs/developer/component-framework/reference/react-control/getoutputschema.md
@@ -1,8 +1,8 @@
---
title: "ReactControl.getOutputSchema (Power Apps component framework API reference) | MicrosoftDocs"
description: "Called by the framework prior to a component initialization in a react control. Returns an object schema based on nomenclature defined in manifest, for any output property of type object."
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 11/07/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/react-control/init.md b/powerapps-docs/developer/component-framework/reference/react-control/init.md
index 3df9f7d698..a041ee1faa 100644
--- a/powerapps-docs/developer/component-framework/reference/react-control/init.md
+++ b/powerapps-docs/developer/component-framework/reference/react-control/init.md
@@ -1,8 +1,8 @@
---
title: "ReactControl.init (Power Apps component framework API reference) | MicrosoftDocs"
description: Used to initialize the component instance for a ReactControl. Components can kick off remote server calls and other initialization actions.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -53,7 +53,7 @@ public init(
### Related articles
-[React controls & platform libraries (Preview) ](../../react-controls-platform-libraries.md)
+[React controls & platform libraries](../../react-controls-platform-libraries.md)
[ReactControl](../react-control.md)
[Power Apps component framework API reference](../../reference/index.md)
[Power Apps component framework overview](../../overview.md)
diff --git a/powerapps-docs/developer/component-framework/reference/react-control/updateview.md b/powerapps-docs/developer/component-framework/reference/react-control/updateview.md
index f4d1cb6585..fde7fc8ca1 100644
--- a/powerapps-docs/developer/component-framework/reference/react-control/updateview.md
+++ b/powerapps-docs/developer/component-framework/reference/react-control/updateview.md
@@ -1,8 +1,8 @@
---
title: "ReactControl.updateView (Power Apps component framework API reference)| MicrosoftDocs"
description: This method is called for a ReactControl when any value in the property bag changes.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 03/25/2024
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/resources.md b/powerapps-docs/developer/component-framework/reference/resources.md
index 8b1524a3e6..4a8c9e80c7 100644
--- a/powerapps-docs/developer/component-framework/reference/resources.md
+++ b/powerapps-docs/developer/component-framework/reference/resources.md
@@ -1,8 +1,8 @@
---
title: Resources (Power Apps component framework API reference) | Microsoft Docs
description: Provides access to the methods to get all the information about the resource files defined in the manifest.
-ms.author: hemantg
-author: HemantGaur
+ms.author: anuitz
+author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/resources/getresource.md b/powerapps-docs/developer/component-framework/reference/resources/getresource.md
index 50ca22831f..140529db2c 100644
--- a/powerapps-docs/developer/component-framework/reference/resources/getresource.md
+++ b/powerapps-docs/developer/component-framework/reference/resources/getresource.md
@@ -1,8 +1,8 @@
---
title: getResource (Power Apps component framework API reference) | Microsoft Docs
description: Provides information about the methods available for getResource.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/resources/getstring.md b/powerapps-docs/developer/component-framework/reference/resources/getstring.md
index dadd53c9a8..d50e87241c 100644
--- a/powerapps-docs/developer/component-framework/reference/resources/getstring.md
+++ b/powerapps-docs/developer/component-framework/reference/resources/getstring.md
@@ -1,8 +1,8 @@
---
title: getString (Power Apps component framework API reference) | Microsoft Docs
description: Returns the localized string for a given key associated with the specified resource (resx) defined in the manifest file.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 09/27/2023
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/retrievemultipleresponse.md b/powerapps-docs/developer/component-framework/reference/retrievemultipleresponse.md
index fe271ae794..c6820daa16 100644
--- a/powerapps-docs/developer/component-framework/reference/retrievemultipleresponse.md
+++ b/powerapps-docs/developer/component-framework/reference/retrievemultipleresponse.md
@@ -1,8 +1,8 @@
---
title: RetrieveMultipleResponse (Power Apps component framework API reference)| Microsoft Docs
description: Learn how to use different methods and properties available for RetrieveMultipleResponse in Power Apps component framework.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/securityprivilegesmetadata.md b/powerapps-docs/developer/component-framework/reference/securityprivilegesmetadata.md
index ed12c7b26c..acc045dc38 100644
--- a/powerapps-docs/developer/component-framework/reference/securityprivilegesmetadata.md
+++ b/powerapps-docs/developer/component-framework/reference/securityprivilegesmetadata.md
@@ -1,8 +1,8 @@
---
title: SecurityPrivilegesMetadata (Power Apps component framework API reference) | Microsoft Docs
description: Information about table definitions security privileges.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/securityvalues.md b/powerapps-docs/developer/component-framework/reference/securityvalues.md
index 4e90a56833..3443b44639 100644
--- a/powerapps-docs/developer/component-framework/reference/securityvalues.md
+++ b/powerapps-docs/developer/component-framework/reference/securityvalues.md
@@ -1,8 +1,8 @@
---
title: SecurityValues (Power Apps component framework API reference) | Microsoft Docs
description: Provides all the information about table definitions security values.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/sortstatus.md b/powerapps-docs/developer/component-framework/reference/sortstatus.md
index 2a77c730a1..60640fd45c 100644
--- a/powerapps-docs/developer/component-framework/reference/sortstatus.md
+++ b/powerapps-docs/developer/component-framework/reference/sortstatus.md
@@ -1,8 +1,8 @@
---
title: SortStatus (Power Apps component framework API reference) | Microsoft Docs
description: Current sort status of a dataset column.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/theming.md b/powerapps-docs/developer/component-framework/reference/theming.md
index 79ad24105d..a1bf7a287c 100644
--- a/powerapps-docs/developer/component-framework/reference/theming.md
+++ b/powerapps-docs/developer/component-framework/reference/theming.md
@@ -1,8 +1,8 @@
---
title: Theming (Power Apps component framework API reference) | Microsoft Docs
description: Provides the API for platform-provided modern theming.
-ms.author: vilesyk
-author: lesyk
+author: jasongre
+ms.author: jasongre
ms.date: 11/15/2023
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/updatedproperties.md b/powerapps-docs/developer/component-framework/reference/updatedproperties.md
index 45e8619652..21529d1fe8 100644
--- a/powerapps-docs/developer/component-framework/reference/updatedproperties.md
+++ b/powerapps-docs/developer/component-framework/reference/updatedproperties.md
@@ -1,8 +1,8 @@
---
title: updatedProperties (Power Apps component framework API reference) | Microsoft Docs
description: Provides updatesProperties related methods.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/usersettings.md b/powerapps-docs/developer/component-framework/reference/usersettings.md
index 0f58a3191a..14461afd37 100644
--- a/powerapps-docs/developer/component-framework/reference/usersettings.md
+++ b/powerapps-docs/developer/component-framework/reference/usersettings.md
@@ -1,8 +1,8 @@
---
title: UserSettings (Power Apps component framework API reference) | Microsoft Docs
description: Provides information about the current user settings.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/usersettings/gettimezoneoffsetminutes.md b/powerapps-docs/developer/component-framework/reference/usersettings/gettimezoneoffsetminutes.md
index d26cfd6215..1d032cba03 100644
--- a/powerapps-docs/developer/component-framework/reference/usersettings/gettimezoneoffsetminutes.md
+++ b/powerapps-docs/developer/component-framework/reference/usersettings/gettimezoneoffsetminutes.md
@@ -1,8 +1,8 @@
---
title: getTimeZoneOffsetMinutes (Power Apps component framework API reference) | Microsoft Docs
description: Gets the offset in minutes from UTC for the given date.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/utility.md b/powerapps-docs/developer/component-framework/reference/utility.md
index 172e167782..200e2c933e 100644
--- a/powerapps-docs/developer/component-framework/reference/utility.md
+++ b/powerapps-docs/developer/component-framework/reference/utility.md
@@ -1,8 +1,8 @@
---
title: Utility (Power Apps component framework API reference) | Microsoft Docs
description: Provides a container for useful methods.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/utility/getentitymetadata.md b/powerapps-docs/developer/component-framework/reference/utility/getentitymetadata.md
index bc43dcbdf9..599608e525 100644
--- a/powerapps-docs/developer/component-framework/reference/utility/getentitymetadata.md
+++ b/powerapps-docs/developer/component-framework/reference/utility/getentitymetadata.md
@@ -1,8 +1,8 @@
---
title: getEntityMetadata (Power Apps component framework API reference) | Microsoft Docs
description: Returns the table definitions for the specified table.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/utility/hasentityprivilege.md b/powerapps-docs/developer/component-framework/reference/utility/hasentityprivilege.md
index 6e30f5f126..2df7b7de3b 100644
--- a/powerapps-docs/developer/component-framework/reference/utility/hasentityprivilege.md
+++ b/powerapps-docs/developer/component-framework/reference/utility/hasentityprivilege.md
@@ -1,8 +1,8 @@
---
title: hasEntityPrivilege (Power Apps component framework API reference) | Microsoft Docs
description: Returns if the user has privilege for specific table.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 06/25/2024
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/utility/lookupobjects.md b/powerapps-docs/developer/component-framework/reference/utility/lookupobjects.md
index 2dfc5ed719..a4e51fd88a 100644
--- a/powerapps-docs/developer/component-framework/reference/utility/lookupobjects.md
+++ b/powerapps-docs/developer/component-framework/reference/utility/lookupobjects.md
@@ -1,8 +1,8 @@
---
title: lookupObjects (Power Apps component framework API reference) | Microsoft Docs
description: Opens a lookup dialog allowing the user to select one or more items.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 03/01/2024
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/webapi.md b/powerapps-docs/developer/component-framework/reference/webapi.md
index a8d4d9e70b..28be288e85 100644
--- a/powerapps-docs/developer/component-framework/reference/webapi.md
+++ b/powerapps-docs/developer/component-framework/reference/webapi.md
@@ -1,8 +1,8 @@
---
title: WebAPI (Power Apps component framework API reference) | Microsoft Docs
description: Provides properties and methods to use Web API to create and manage records.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/webapi/createrecord.md b/powerapps-docs/developer/component-framework/reference/webapi/createrecord.md
index 10cb1e6939..cdfb1a37ee 100644
--- a/powerapps-docs/developer/component-framework/reference/webapi/createrecord.md
+++ b/powerapps-docs/developer/component-framework/reference/webapi/createrecord.md
@@ -1,8 +1,8 @@
---
title: createRecord (Power Apps component framework API reference) | Microsoft Docs
description: Creates a table record.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/webapi/deleterecord.md b/powerapps-docs/developer/component-framework/reference/webapi/deleterecord.md
index 2b02bd3e37..e426b70db0 100644
--- a/powerapps-docs/developer/component-framework/reference/webapi/deleterecord.md
+++ b/powerapps-docs/developer/component-framework/reference/webapi/deleterecord.md
@@ -1,8 +1,8 @@
---
title: deleteRecord (Power Apps component framework API reference) | Microsoft Docs
description: Deletes a table record.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
diff --git a/powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md b/powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md
index b187f23f9b..35e23496d6 100644
--- a/powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md
+++ b/powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md
@@ -1,8 +1,8 @@
---
title: retrieveMultipleRecords (Power Apps component framework API reference) | Microsoft Docs
description: Retrieves a collection of table records.
-ms.author: hemantg
-author: HemantGaur
+author: anuitz
+ms.author: anuitz
ms.date: 05/27/2022
ms.reviewer: jdaly
ms.topic: reference
@@ -55,7 +55,7 @@ Model-driven apps & portals.