From 15c91924594122e3c4675e56c00373421664b56d Mon Sep 17 00:00:00 2001 From: Blake-Madden <66873089+Blake-Madden@users.noreply.github.com> Date: Mon, 10 Jun 2024 11:07:42 -0400 Subject: [PATCH] Fix a few typos --- power-platform/admin/about-encryption.md | 2 +- power-platform/admin/admin-activity-logging.md | 2 +- power-platform/admin/connect-exchange-online.md | 2 +- power-platform/admin/cross-tenant-restrictions.md | 2 +- power-platform/admin/customer-managed-key.md | 4 ++-- power-platform/admin/default-environment-routing.md | 2 +- power-platform/admin/dlp-activity-logging.md | 2 +- power-platform/admin/manage-group-teams.md | 2 +- power-platform/admin/manage-principalobjectaccess-storage.md | 2 +- power-platform/admin/pay-as-you-go-issues-faq.md | 2 +- power-platform/admin/pay-as-you-go-meters.md | 2 +- power-platform/admin/powerapps-analytics-reports.md | 2 +- power-platform/admin/support-overview.md | 2 +- .../admin/system-settings-dialog-box-formats-tab.md | 2 +- .../troubleshooting-monitoring-server-side-synchronization.md | 2 +- ...oubleshooting-user-needs-read-write-access-organization.md | 2 +- power-platform/admin/try-powerapps-dynamics-365.md | 2 +- .../tutorial-deploy-new-environment-with-ERP-template.md | 2 +- power-platform/admin/wp-management-monitoring.md | 2 +- power-platform/alm/move-from-unmanaged-managed-alm.md | 2 +- power-platform/alm/solution-async.md | 2 +- power-platform/alm/solution-concepts-alm.md | 2 +- power-platform/alm/when-edit-customization-file.md | 2 +- .../appendix-add-license-information-to-your-solution.md | 2 +- power-platform/developer/howto/install-vs-code-extension.md | 2 +- .../finance-operations-install-config-tools.md | 2 +- power-platform/guidance/adoption/resource-usage.md | 2 +- power-platform/guidance/coe/setup-archive-components.md | 2 +- power-platform/guidance/creator-kit/shimmer.md | 2 +- power-platform/guidance/creator-kit/spinbutton.md | 2 +- power-platform/important-changes-coming.md | 2 +- power-platform/power-fx/operators.md | 2 +- power-platform/power-fx/reference/function-copy.md | 2 +- power-platform/power-fx/reference/function-datasourceinfo.md | 2 +- power-platform/power-fx/reference/function-filter-lookup.md | 2 +- power-platform/power-fx/reference/function-find.md | 2 +- power-platform/power-fx/reference/function-groupby.md | 2 +- power-platform/power-fx/reference/function-iferror.md | 4 ++-- power-platform/power-fx/reference/function-remove-removeif.md | 2 +- power-platform/power-fx/reference/function-setfocus.md | 2 +- power-platform/power-fx/reference/function-table-shaping.md | 2 +- power-platform/power-fx/reference/function-update-updateif.md | 2 +- power-platform/power-fx/reference/operators.md | 2 +- .../experience-optimization/design-standards.md | 2 +- 44 files changed, 46 insertions(+), 46 deletions(-) diff --git a/power-platform/admin/about-encryption.md b/power-platform/admin/about-encryption.md index 14159dee80..83aac4011b 100644 --- a/power-platform/admin/about-encryption.md +++ b/power-platform/admin/about-encryption.md @@ -24,7 +24,7 @@ Data is an organization’s most valuable and irreplaceable asset, and encryptio Encrypting your information renders it unreadable to unauthorized persons, even if they break through your firewalls, infiltrate your network, get physical access to your devices, or bypass the permissions on your local machine. Encryption transforms data so that only someone with the decryption key can access it. -Dynamics 365 uses heterogenous storage (Dataverse) to store the data. The data is distributed across different storage types: +Dynamics 365 uses heterogeneous storage (Dataverse) to store the data. The data is distributed across different storage types: - Azure SQL Database for relational data - Azure Blob storage for binary data, such as images and documents diff --git a/power-platform/admin/admin-activity-logging.md b/power-platform/admin/admin-activity-logging.md index d7ede8fc05..073b1a254f 100644 --- a/power-platform/admin/admin-activity-logging.md +++ b/power-platform/admin/admin-activity-logging.md @@ -51,7 +51,7 @@ Each activity event contains a payload of metadata that is specific to the indiv | Reset environment | A sandbox environment has been reset. | | Upgraded environment | A component of an environment has been upgraded to a new version. | | CMK-Renewed environment | The customer-managed key (CMK) has been renewed on the environment. | -| CMK-Reverted environment | Environment was removed from enterprise policy and encryption was retured to Microsoft-managed key. | +| CMK-Reverted environment | Environment was removed from enterprise policy and encryption was returned to Microsoft-managed key. | ## Activity category: Environment property and setting change activities diff --git a/power-platform/admin/connect-exchange-online.md b/power-platform/admin/connect-exchange-online.md index 4ea2853d0a..65dd03c131 100644 --- a/power-platform/admin/connect-exchange-online.md +++ b/power-platform/admin/connect-exchange-online.md @@ -306,7 +306,7 @@ To approve emails, a Dynamics 365 user requires the **Approve Email Addresses fo #### Approve mailboxes -You can use a manual or programmatic processses to approve a mailbox. +You can use a manual or programmatic processes to approve a mailbox. ##### Approve a mailbox manually diff --git a/power-platform/admin/cross-tenant-restrictions.md b/power-platform/admin/cross-tenant-restrictions.md index 99ac322b5f..d9264f1b87 100644 --- a/power-platform/admin/cross-tenant-restrictions.md +++ b/power-platform/admin/cross-tenant-restrictions.md @@ -164,7 +164,7 @@ Selecting the failed run will show details of the failed flow run. ## Known issues -[Azure DevOps connector](/connectors/visualstudioteamservices) uses Microsoft Entra authentication as the identity provider, but uses its own OAuth flow and STS for authorizing and issuing a token. Since the token returned from the ADO flow based on that Connector’s configuration is not from Microsoft Entra ID, the tenant isolation policy is not enforced. As a mitigation, we recomend using other types of [data policies](wp-data-loss-prevention.md) to limit the use of the connector or its actions. +[Azure DevOps connector](/connectors/visualstudioteamservices) uses Microsoft Entra authentication as the identity provider, but uses its own OAuth flow and STS for authorizing and issuing a token. Since the token returned from the ADO flow based on that Connector’s configuration is not from Microsoft Entra ID, the tenant isolation policy is not enforced. As a mitigation, we recommend using other types of [data policies](wp-data-loss-prevention.md) to limit the use of the connector or its actions. [!INCLUDE[footer-include](../includes/footer-banner.md)] \ No newline at end of file diff --git a/power-platform/admin/customer-managed-key.md b/power-platform/admin/customer-managed-key.md index 0617a74404..2b5c44e995 100644 --- a/power-platform/admin/customer-managed-key.md +++ b/power-platform/admin/customer-managed-key.md @@ -432,7 +432,7 @@ Follow these steps if you want to return to a Microsoft managed encryption key. 1. Select **Save**. > [!IMPORTANT] - > The environment will be disabled when it is removed from the enterprise policy to revert the data encryption to the Microsoft-managed key. **Do not delete or disable the key, delete or disable the key vault, or remove the enteprise policy's permissions to the key vault.** The key and key vault's access is necessary to support database restoration. You may delete and remove the enterprise policy's permissions after 30 days. + > The environment will be disabled when it is removed from the enterprise policy to revert the data encryption to the Microsoft-managed key. **Do not delete or disable the key, delete or disable the key vault, or remove the enterprise policy's permissions to the key vault.** The key and key vault's access is necessary to support database restoration. You may delete and remove the enterprise policy's permissions after 30 days. ### Review the environment's encryption status @@ -480,7 +480,7 @@ To change your encryption key, create a new key and a new enterprise policy. You 1. Repeat steps 2-6 until all environments in the enterprise policy have been removed. > [!IMPORTANT] - > The environment will be disabled when it is removed from the enterprise policy to revert the data encryption to the Microsoft-managed key. **Do not delete or disable the key, delete or disable the key vault, or remove the enteprise policy's permissions to the key vault**. The key and key vault's access is necessary to support database restoration. You may delete and remove the enterprise policy's permissions after 30 days. + > The environment will be disabled when it is removed from the enterprise policy to revert the data encryption to the Microsoft-managed key. **Do not delete or disable the key, delete or disable the key vault, or remove the enterprise policy's permissions to the key vault**. The key and key vault's access is necessary to support database restoration. You may delete and remove the enterprise policy's permissions after 30 days. 1. Once all the environments are removed, from the Power Platform admin center go to **Enterprise policies**. 1. Select the new enterprise policy, and then select **Edit policy**. diff --git a/power-platform/admin/default-environment-routing.md b/power-platform/admin/default-environment-routing.md index 5cd972f194..aa47cc0b86 100644 --- a/power-platform/admin/default-environment-routing.md +++ b/power-platform/admin/default-environment-routing.md @@ -196,7 +196,7 @@ The maker is always routed to their own existing personal developer environment, ### What happens if the Power Platform admin changes the Developer environment assignments setting from "Everyone" to "Only specific admins" while Environment routing is **On**? -The admin recieves the following error "Something went wrong while saving your changes. Try again and if the problem persists, submit a support ticket with correlation id: 1234567910." The admin won't be able to change the Developer environment assignments setting unless they turn environment routing off. +The admin receives the following error "Something went wrong while saving your changes. Try again and if the problem persists, submit a support ticket with correlation id: 1234567910." The admin won't be able to change the Developer environment assignments setting unless they turn environment routing off. ### Where are makers routed to if they don’t have an existing developer environment? diff --git a/power-platform/admin/dlp-activity-logging.md b/power-platform/admin/dlp-activity-logging.md index d7748d4d70..743190333a 100644 --- a/power-platform/admin/dlp-activity-logging.md +++ b/power-platform/admin/dlp-activity-logging.md @@ -16,7 +16,7 @@ search.audienceType: # Data loss prevention activity logging > [!Warning] -> The schema documented in this artice is deprecated and won't be available starting in July 2024. You can use the new schema available at [Activity category: Data policy events](admin-activity-logging.md#activity-category-data-policy-events). +> The schema documented in this article is deprecated and won't be available starting in July 2024. You can use the new schema available at [Activity category: Data policy events](admin-activity-logging.md#activity-category-data-policy-events). > [!NOTE] > Activity logging for data loss protection policies is not currently available in sovereign clouds. diff --git a/power-platform/admin/manage-group-teams.md b/power-platform/admin/manage-group-teams.md index 706744b517..a93a6eb4dc 100644 --- a/power-platform/admin/manage-group-teams.md +++ b/power-platform/admin/manage-group-teams.md @@ -89,7 +89,7 @@ For more information, see [Assign a record to a user or team](/powerapps/user/as - Don't have the correct permissions? Contact your system administrator. Prerequisites: - 1. An Microsoft Entra Group is required for each group team. + 1. A Microsoft Entra Group is required for each group team. 2. Obtain the Microsoft Entra Group's **ObjectID** from your https://portal.azure.com site. 3. Create a custom security role that contains privileges per your team's collaboration requirement. See the discussion of [member's inherited privileges](security-roles-privileges.md#team-members-privilege-inheritance) if you need to extend the team member's privileges directly to a user. diff --git a/power-platform/admin/manage-principalobjectaccess-storage.md b/power-platform/admin/manage-principalobjectaccess-storage.md index 64890fd708..97468c06ad 100644 --- a/power-platform/admin/manage-principalobjectaccess-storage.md +++ b/power-platform/admin/manage-principalobjectaccess-storage.md @@ -74,7 +74,7 @@ The POA table is managed by the system to ensure proper access of users or teams ## Troubleshooting guides When the cascade configuration of a table relationship is [changed from **Reparent** or **Share** to **No Cascade**](/power-apps/developer/data-platform/configure-entity-relationship-cascading-behavior#inherited-access-repair), use this article to clean up the inherited access. This removes unnecessary POA records. More information: [How to clean up inherited access](/troubleshoot/power-platform/power-apps/dataverse/cleanup-inherited-access?tabs=sdk). -Inherited access rights cleanup is a system job that cleans up the legacy, inherited access rights that remain after the cascading behavior is changed to **Cascade None**. More information: [Inherited acccess rights cleanup](/power-apps/maker/data-platform/create-edit-entity-relationships#inherited-access-rights-cleanup) +Inherited access rights cleanup is a system job that cleans up the legacy, inherited access rights that remain after the cascading behavior is changed to **Cascade None**. More information: [Inherited access rights cleanup](/power-apps/maker/data-platform/create-edit-entity-relationships#inherited-access-rights-cleanup) To learn whether user access was granted because of POA, see [Determine why a user has access](/power-apps/developer/data-platform/security-sharing-assigning?tabs=sdk#determine-why-a-user-has-access). diff --git a/power-platform/admin/pay-as-you-go-issues-faq.md b/power-platform/admin/pay-as-you-go-issues-faq.md index 5d5459fa04..a7286727eb 100644 --- a/power-platform/admin/pay-as-you-go-issues-faq.md +++ b/power-platform/admin/pay-as-you-go-issues-faq.md @@ -157,7 +157,7 @@ If the user accesses the site using different browsers or devices or cleans up b If the users are accessing only sign in page, then they won't be counted as anonymous users. There are several types of pages that aren't counted for the anonymous user meter. The pages are described in [Power Pages – Anonymous user meter](pay-as-you-go-meters.md#anonymous-user-meter). -### I use Application Insights (or Google Analytics) on my website and monthly active user count shown by that is different then what I see in Power Pages licensing reports. Is that expected? +### I use Application Insights (or Google Analytics) on my website and monthly active user count shown by that is different than what I see in Power Pages licensing reports. Is that expected? User counts generated by analytics providers like Application Insights or Google Analytics can differ from the counts of the Power Pages meters. diff --git a/power-platform/admin/pay-as-you-go-meters.md b/power-platform/admin/pay-as-you-go-meters.md index 99dc6d37cf..c61d5b3c6d 100644 --- a/power-platform/admin/pay-as-you-go-meters.md +++ b/power-platform/admin/pay-as-you-go-meters.md @@ -123,7 +123,7 @@ Example: If an environment has Unattended bot add on units assigned and then PAY If the owner of a flow is service principal, the flow runs are charged unless the flow has a per-flow license. > [!NOTE] -> Assigning a Power Automate per user/per flow license ensures that any runs of the flow doesnt trigger Power Automate flow run meter if the flow features are within their license entitlements. But, if the flow uses more Power platform requests than the [limits](/power-platform/admin/api-request-limits-allocations#licensed-user-request-limits), Power platform request meter is triggered for any overages. +> Assigning a Power Automate per user/per flow license ensures that any runs of the flow doesn't trigger Power Automate flow run meter if the flow features are within their license entitlements. But, if the flow uses more Power platform requests than the [limits](/power-platform/admin/api-request-limits-allocations#licensed-user-request-limits), Power platform request meter is triggered for any overages. |User |Standard flow runs |Premium cloud flow runs |Attended RPA flow runs |Unattended RPA runs| Azure billable runs| |---------|----------------------|----------------|--------------|-------------|-------------| diff --git a/power-platform/admin/powerapps-analytics-reports.md b/power-platform/admin/powerapps-analytics-reports.md index 836f2a866d..d7a7f4bb4b 100644 --- a/power-platform/admin/powerapps-analytics-reports.md +++ b/power-platform/admin/powerapps-analytics-reports.md @@ -56,7 +56,7 @@ Power Apps reports provide insights into tenant and environment usage and invent ## Power Apps - Maker Activity report -The Power Apps Maker Activity report provide insights into tenant and environment usage and inventory of all apps and connectors. The report answers questions such as: +The Power Apps Maker Activity report provides insights into tenant and environment usage and inventory of all apps and connectors. The report answers questions such as: - What is the total number of apps created/published/modified/deleted by app makers across the tenant or environments? - What is the count of first-time makers across canvas and model-driven apps? diff --git a/power-platform/admin/support-overview.md b/power-platform/admin/support-overview.md index 099f0b1301..70ca7a06cf 100644 --- a/power-platform/admin/support-overview.md +++ b/power-platform/admin/support-overview.md @@ -222,7 +222,7 @@ Technical support does not conduct RCAs as part of any support experience. If an Data may become corrupt due to a variety of reasons (malfunctioning software, custom code, partner or ISV software, power outages, etc.). Microsoft does not provide assistance for correcting damaged data. Note that per the Service Provider License Agreement (SPLA), Microsoft does not have a legal obligation to change or correct data being corrupted due to malfunctioning software. Microsoft may execute scripts provided by partners/customers in the production environment if the script was tested in the UAT environment by the partner/customer prior. -### What happens if the issue can not be reproduced or has to do with customized databases? +### What happens if the issue can't be reproduced or has to do with customized databases? In scenarios where a problem is not able to be reproduced in a standard non-modified Dynamics installation, the Microsoft Dynamics support team will invest best effort support up to 4 hours of time on a break fix case to assist. If after 4 hours, we have not yet identified the repro steps of an issue, consulting a partner or the community forums will be recommended for further investigation and the technical support incident will be closed. diff --git a/power-platform/admin/system-settings-dialog-box-formats-tab.md b/power-platform/admin/system-settings-dialog-box-formats-tab.md index 6b17cb1a21..46d8ee49db 100644 --- a/power-platform/admin/system-settings-dialog-box-formats-tab.md +++ b/power-platform/admin/system-settings-dialog-box-formats-tab.md @@ -17,7 +17,7 @@ You can control how customer engagement apps (Dynamics 365 Sales, Dynamics 365 C -## Open the Formats System Settings dialog box (it it isn't already open) +## Open the Formats System Settings dialog box (it isn't already open) 1. [!INCLUDE[proc_permissions_system_admin_and_customizer](../includes/proc-permissions-system-admin-and-customizer.md)] diff --git a/power-platform/admin/troubleshooting-monitoring-server-side-synchronization.md b/power-platform/admin/troubleshooting-monitoring-server-side-synchronization.md index d09a130299..6df6848fa5 100644 --- a/power-platform/admin/troubleshooting-monitoring-server-side-synchronization.md +++ b/power-platform/admin/troubleshooting-monitoring-server-side-synchronization.md @@ -30,7 +30,7 @@ The **Sync Error** column contains information about why the item didn't synchro Selecting the link directs you to a **Learn** article for the error, if one exists. -The data for the dashboard is stored in the ExchangeSyncIdMapping table and is retained by the system for up to three days after the failure occured. This value can be modified by changing the ExchangeSyncIdMappingPersistenceTimeInDays OrgDbOrgSetting. +The data for the dashboard is stored in the ExchangeSyncIdMapping table and is retained by the system for up to three days after the failure occued. This value can be modified by changing the ExchangeSyncIdMappingPersistenceTimeInDays OrgDbOrgSetting. ## Known Issues: diff --git a/power-platform/admin/troubleshooting-user-needs-read-write-access-organization.md b/power-platform/admin/troubleshooting-user-needs-read-write-access-organization.md index cacda82c71..d0f02dc9c2 100644 --- a/power-platform/admin/troubleshooting-user-needs-read-write-access-organization.md +++ b/power-platform/admin/troubleshooting-user-needs-read-write-access-organization.md @@ -77,7 +77,7 @@ See [How access to a record is determined](how-record-access-determined.md). 1. As a system administrator of the environment, verify that the environment is associated with any Microsoft Entra group. See: [Associate a security group with an environment](control-user-access.md#associate-a-security-group-with-an-environment). 2. Ensure the user with the access issue is a member of the group associated with the environment. See: [Create a security group and add members to the security group](control-user-access.md#create-a-security-group-and-add-members-to-the-security-group). -3. Once user membership in the environment’s group is updated, it may take some time for the change to sync to the environment. To trigger a sync for this user, the system administrator for the environment can readd the user to the environment. See: [Add users to an environment that has a Dataverse database](add-users-to-environment.md#add-users-to-an-environment-that-has-a-dataverse-database). +3. Once user membership in the environment’s group is updated, it may take some time for the change to sync to the environment. To trigger a sync for this user, the system administrator for the environment can read the user to the environment. See: [Add users to an environment that has a Dataverse database](add-users-to-environment.md#add-users-to-an-environment-that-has-a-dataverse-database). ### Troubleshoot permission issues diff --git a/power-platform/admin/try-powerapps-dynamics-365.md b/power-platform/admin/try-powerapps-dynamics-365.md index eaf0ddd043..5355b0150d 100644 --- a/power-platform/admin/try-powerapps-dynamics-365.md +++ b/power-platform/admin/try-powerapps-dynamics-365.md @@ -20,7 +20,7 @@ You can explore all Power Platform apps for free by signing up for trial license |Microsoft Copilot Studio | [Sign up for a Microsoft Copilot Studio trial](/microsoft-copilot-studio/sign-up-individual) | > [!NOTE] -> You can sign up for for a 30-day free trial of customer engagement apps (such as Dynamics 365 Sales, Dynamics 365 Customer Service) by visiting , and selecting the appropriate app. +> You can sign up for a 30-day free trial of customer engagement apps (such as Dynamics 365 Sales, Dynamics 365 Customer Service) by visiting , and selecting the appropriate app. > > For detailed information about signing up, purchasing or using individual customer engagement apps, see the respective app's documentation at [Dynamics 365 documentation](/dynamics365/). diff --git a/power-platform/admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md b/power-platform/admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md index 1865f7cb1f..dfe8296f56 100644 --- a/power-platform/admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md +++ b/power-platform/admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md @@ -67,7 +67,7 @@ If you wish to create a new environment with finance and operations apps pre-ins Load up your PowerShell console and execute the following commands to generate the environment. Note the variables so that you can change the input values, as required. If you wish to use a service principal, follow the instructions at [Creating a service principal application using PowerShell](../powershell-create-service-principal.md). -In the script below, the parameter **DevToolsEnabled** determines if your sandbox environment get provisioned with support for X++ development or wether it becomes a traditional sandbox environment for user acceptance testing and training purposes. By setting this value to **true** you can do development, and by setting it to **false** or ommitting it, you receive a traditional sandbox environment with finance and operations apps installed. +In the script below, the parameter **DevToolsEnabled** determines if your sandbox environment get provisioned with support for X++ development or whether it becomes a traditional sandbox environment for user acceptance testing and training purposes. By setting this value to **true** you can do development, and by setting it to **false** or omitting it, you receive a traditional sandbox environment with finance and operations apps installed. ```powershell #Install the module diff --git a/power-platform/admin/wp-management-monitoring.md b/power-platform/admin/wp-management-monitoring.md index ff98f8a129..e00bc2d80a 100644 --- a/power-platform/admin/wp-management-monitoring.md +++ b/power-platform/admin/wp-management-monitoring.md @@ -27,7 +27,7 @@ Portals are typically considered the primary path for completing administrative - **Power Automate Management connector** is designed to help with administrative management and monitoring ([Power Automate Management](/connectors/flowmanagement/)). - **Microsoft Flow for Admins** allows you to complete typical admin actions, such as disabling a flow and deleting a flow ([Power Automate for Admins](/connectors/microsoftflowforadmins/)). - **Power Apps for Admins connector** can be used to set permissions on Power Apps or set permissions to a certain connector being used by this app ([Power Apps for Admins](/connectors/powerappsforadmins/)). -- **PowerApps for App Makers** can be used by the makers themselves, though some actions being an overlay to administrational tasks, such as settings permissions to an app as mentioned previously ([Power Apps for Makers](/connectors/powerappsforappmakers/)). +- **PowerApps for App Makers** can be used by the makers themselves, though some actions being an overlay to administrative tasks, such as settings permissions to an app as mentioned previously ([Power Apps for Makers](/connectors/powerappsforappmakers/)). - **Power Platform for Admins** can be used to perform tasks against platform components, such as creating an environment or provisioning a Microsoft Dataverse database or creating a DLP policy for a specific environment ([Power Platform for Admins](/connectors/powerplatformforadmins/)). Check out the Admin-in-a-day content that can be found in the ([GitHub repository](https://github.com/microsoft/powerapps-tools/tree/master/Administration/AdminInADay)) that walks you through examples via hands-on labs with step-by-step instructions. diff --git a/power-platform/alm/move-from-unmanaged-managed-alm.md b/power-platform/alm/move-from-unmanaged-managed-alm.md index efcb4aab19..3e7f18b46e 100644 --- a/power-platform/alm/move-from-unmanaged-managed-alm.md +++ b/power-platform/alm/move-from-unmanaged-managed-alm.md @@ -30,7 +30,7 @@ With the exception of your development environment, the end result is to only ha 1. Remove tables and components that are not needed from your production environment. For example, consider deleting tables with no records or very old records, or tables and components that have no dependencies. More information: [View dependencies for a component](/powerapps/maker/data-platform/view-component-dependencies) 2. Create a solution to use to convert components from unmanaged to managed. - - In your development environment, create a *single* unmanaged solution that will be used to contain *all* Microsoft Dataverse model-driven apps, tables, and dependant components, such as forms, views, fields, charts, and dashboards. Incorporating all of these components together can help reduce the chances of cross-solution layering issues that might occur later when you update or introduce new model-driven apps and customizations. More information: [Create a solution](/power-apps/maker/data-platform/create-solution) + - In your development environment, create a *single* unmanaged solution that will be used to contain *all* Microsoft Dataverse model-driven apps, tables, and dependent components, such as forms, views, fields, charts, and dashboards. Incorporating all of these components together can help reduce the chances of cross-solution layering issues that might occur later when you update or introduce new model-driven apps and customizations. More information: [Create a solution](/power-apps/maker/data-platform/create-solution) - For *unmanaged* components, such as custom unmanaged tables, you won't use segmentation but will select **Include all components** when adding those components to the solution. - If there are *managed* components that you've customized, use segmentation when adding those components to the solution. For example, if you've added a custom column or changed the display name for an existing column to a Power Apps standard table, such as **Account** and **Contact**, use segmentation so you only export the customized components your project needs and not additional components that you don't intend to service. To do this, choose **Select components**, and then add only your customized components to the solution. > [!TIP] diff --git a/power-platform/alm/solution-async.md b/power-platform/alm/solution-async.md index 929cac14f3..9daa593bc1 100644 --- a/power-platform/alm/solution-async.md +++ b/power-platform/alm/solution-async.md @@ -67,7 +67,7 @@ public static ImportSolutionAsyncResponse ImportSolution( // Import the staged solution var componentDetails = stagingResults.SolutionComponentsDetails; - // TODO These are not referenced in the code but are usefull to explore + // TODO These are not referenced in the code but are useful to explore var missingDependencies = stagingResults.MissingDependencies; // Contains missing dependencies var solutionDetails = stagingResults.SolutionDetails; // Contains solution details diff --git a/power-platform/alm/solution-concepts-alm.md b/power-platform/alm/solution-concepts-alm.md index 06b18fbacd..bf388464c6 100644 --- a/power-platform/alm/solution-concepts-alm.md +++ b/power-platform/alm/solution-concepts-alm.md @@ -131,7 +131,7 @@ Because of the way that managed solutions are layered, some managed solutions ca The system tracks these dependencies between solutions. If you try to install a solution that requires a base solution that isn’t installed, you won’t be able to install the solution. You will get a message saying that the solution requires another solution to be installed first. Similarly, because of the dependencies, you can’t uninstall the base solution while a solution that depends on it is still installed. You have to uninstall the dependent solution before you can uninstall the base solution. More information: [Removing dependencies](removing-dependencies.md) ## Solution component dependencies -A solution component represents something that you can potentially customize. Anything that can be included in a solution is a solution component and some components are dependant on other components. For example, the website field and account summary report are both dependant on the account entity. More information: [Dependency tracking for solution components](dependency-tracking-solution-components.md) +A solution component represents something that you can potentially customize. Anything that can be included in a solution is a solution component and some components are dependent on other components. For example, the website field and account summary report are both dependent on the account entity. More information: [Dependency tracking for solution components](dependency-tracking-solution-components.md) ### See also diff --git a/power-platform/alm/when-edit-customization-file.md b/power-platform/alm/when-edit-customization-file.md index c069835239..016da09b94 100644 --- a/power-platform/alm/when-edit-customization-file.md +++ b/power-platform/alm/when-edit-customization-file.md @@ -37,7 +37,7 @@ The customizations.xml file that is exported as part of an unmanaged solution ca For more information, see [Change Application Navigation using the SiteMap](/dynamics365/customer-engagement/developer/customize-dev/change-application-navigation-using-sitemap) **Editing FormXml** - FormXml is used to define entity forms and dashboards. The form editor and dashboard designer in the application are the most commonly used tools for this purpose. Editing the customizations.xml file is an alternative method. For more information, see [Customize entity forms](/powerapps/developer/model-driven-apps/customize-entity-forms)and [Create a Dashboard](/powerapps/developer/model-driven-apps/create-dashboard). + FormXml is used to define entity forms and dashboards. The form editor and dashboard designer in the application are the most commonly used tools for this purpose. Editing the customizations.xml file is an alternative method. For more information, see [Customize entity forms](/powerapps/developer/model-driven-apps/customize-entity-forms) and [Create a Dashboard](/powerapps/developer/model-driven-apps/create-dashboard). **Editing saved queries** Definitions of views for entities are included in the customizations.xml file and may be manually edited. The view editor in the application is the most commonly used tool for this purpose. Editing customizations.xml is an alternative method. For more information, see [Customize entity views](/powerapps/developer/model-driven-apps/customize-entity-views). diff --git a/power-platform/developer/appsource/appendix-add-license-information-to-your-solution.md b/power-platform/developer/appsource/appendix-add-license-information-to-your-solution.md index 78bc89f3f0..d6d69dd37e 100644 --- a/power-platform/developer/appsource/appendix-add-license-information-to-your-solution.md +++ b/power-platform/developer/appsource/appendix-add-license-information-to-your-solution.md @@ -84,7 +84,7 @@ The plan definition file must include the following columns laid out in the form **Service ID:** This is created automatically when you create a plan in the Partner Center as part of the offer creation. Copy it from partner center into the plan definition file. More information: [Create plans in Partner Center](/azure/marketplace/dynamics-365-customer-engage-plans). -**Display Name:** This is a descriptive name for your plan which you can choose. It will be show to users on license check error screens so it should be easily recognizable to your customers. +**Display Name:** This is a descriptive name for your plan which you can choose. It will be shown to users on license check error screens so it should be easily recognizable to your customers. **More info URL:** This is a URL where you would like to direct users to get more information about your solution, in the event they run into a license check error. diff --git a/power-platform/developer/howto/install-vs-code-extension.md b/power-platform/developer/howto/install-vs-code-extension.md index 658d0878e0..3a898294a1 100644 --- a/power-platform/developer/howto/install-vs-code-extension.md +++ b/power-platform/developer/howto/install-vs-code-extension.md @@ -97,7 +97,7 @@ If you choose to [install a previous version](#install-a-previous-version), you' By default, the Visual Studio Code extension only enables commands using the Visual Studio Code PowerShell terminal. -To enable using PAC CLI in in Command Prompt (CMD) and PowerShell terminals for Windows, you can do any of the following: +To enable using PAC CLI in Command Prompt (CMD) and PowerShell terminals for Windows, you can do any of the following: - [Install Power Platform CLI with .NET Tool](install-cli-net-tool.md) - [Install Power Platform CLI using Windows MSI](install-cli-msi.md) diff --git a/power-platform/developer/unified-experience/finance-operations-install-config-tools.md b/power-platform/developer/unified-experience/finance-operations-install-config-tools.md index 8745dfaf16..4572116756 100644 --- a/power-platform/developer/unified-experience/finance-operations-install-config-tools.md +++ b/power-platform/developer/unified-experience/finance-operations-install-config-tools.md @@ -134,7 +134,7 @@ To configure the extension, follow these instructions. :::image type="content" source="../media/unified-experience/D365FinOpsConfigureMetadata.png" alt-text="Configure Metadata dialog"::: 1. Select **Save**. -2. You can similary edit a configuration. A common field to update is the folder for your own custom metadata. +2. You can similarly edit a configuration. A common field to update is the folder for your own custom metadata. 3. You might also want to move your cross reference database from SQL server local db to SQL server and update the configuration 4. You can delete stale configurations. 5. Note that only one configuration can be current or active at any given time. diff --git a/power-platform/guidance/adoption/resource-usage.md b/power-platform/guidance/adoption/resource-usage.md index 841e86cb49..fb070906f0 100644 --- a/power-platform/guidance/adoption/resource-usage.md +++ b/power-platform/guidance/adoption/resource-usage.md @@ -34,7 +34,7 @@ Out-of-the-box tooling around monitoring, alerts, and actions falls into the fol - [Power Automate Management](/connectors/flowmanagement/) is specifically designed to help with administrative management and monitoring. - [Power Automate for Admins](/connectors/microsoftflowforadmins/) allows you to perform typical admin actions, such as disabling or deleting a flow. - [Power Apps for Admins](/connectors/powerappsforadmins/) to set permissions on Power Apps or set permissions to a certain connector being used by this app. - - [Power Apps for Makers](/connectors/powerappsforappmakers/), which can be used by the makers themselves, although some actions overlay administrational tasks, such as settings permissions to a Power Apps app as mentioned previously. + - [Power Apps for Makers](/connectors/powerappsforappmakers/), which can be used by the makers themselves, although some actions overlay administrative tasks, such as settings permissions to a Power Apps app as mentioned previously. - [Power Platform for Admins](/connectors/powerplatformforadmins) to perform tasks against platform components, such as creating an environment or provisioning a Microsoft Dataverse database or creating a data loss prevention (DLP) policy for a specific environment. The [Center of Excellence Starter Kit](../coe/starter-kit.md) offers a template implementation using the management and admin connectors and comes with a Power BI dashboard that can be used to gain tenant-wide insights. diff --git a/power-platform/guidance/coe/setup-archive-components.md b/power-platform/guidance/coe/setup-archive-components.md index 8a00359881..7415d5829b 100644 --- a/power-platform/guidance/coe/setup-archive-components.md +++ b/power-platform/guidance/coe/setup-archive-components.md @@ -103,7 +103,7 @@ Environment variables are used to store application and flow configuration data | Name | Description | Default value | |------|---------------|------| | Individual Admin | This is separate from the Admin Email environment variable because you can't use a distribution list for approvals. This environment variable holds the individual or shared account who will be charged with approving the removal of unused orphaned objects. | None | -| Auto Delete on Archive | Determines whether apps andd flows are deleted when they're approved for deletion in the following flow: Admin \|Inactivity notifications v2 (Check Approval) and Admin \|Inactivity notifications v2 (Clean Up and Delete). The value must be Yes or No. | Yes | +| Auto Delete on Archive | Determines whether apps and flows are deleted when they're approved for deletion in the following flow: Admin \|Inactivity notifications v2 (Check Approval) and Admin \|Inactivity notifications v2 (Clean Up and Delete). The value must be Yes or No. | Yes | | Cleanup Old Objects App URL | (Optional) A link to the Cleanup Old Objects canvas app included in this solution. To make cleanup easier, any communication about old objects that are no longer considered to be useful will include this link. More information: [Get an app URL from a production environment](faq.md#get-a-power-apps-url-from-a-production-environment) | None | | Flow Approvals URL | (Optional) A link to the Power Automate approval page for your CoE environment. To make cleanup easier, any communication about old objects that are no longer considered to be useful will include this link. To get the URL, go to make.powerautomate.com for your CoE environment > **Action Items** > **Approvals**. The URL will end in **approvals/received**.| None | | ProductionEnvironment | Set to **No** if you've installed the solution for development or test purposes. This will send approvals to the admin email instead of the maker. | Yes | diff --git a/power-platform/guidance/creator-kit/shimmer.md b/power-platform/guidance/creator-kit/shimmer.md index 2fab86effa..6bff90b18f 100644 --- a/power-platform/guidance/creator-kit/shimmer.md +++ b/power-platform/guidance/creator-kit/shimmer.md @@ -35,7 +35,7 @@ This code component provides a wrapper around the [Fluent UI Shimmer](https://de | -------- | ----------- | | `Items` | The action items to render | | `Rows` | The action items to render | -| `SpacebetweenShimmer` | Space or Gap between each Shimmer incase of muliple rows. | +| `SpacebetweenShimmer` | Space or Gap between each Shimmer incase of multiple rows. | ### Items properties diff --git a/power-platform/guidance/creator-kit/spinbutton.md b/power-platform/guidance/creator-kit/spinbutton.md index ab5735b587..1a62c3f43c 100644 --- a/power-platform/guidance/creator-kit/spinbutton.md +++ b/power-platform/guidance/creator-kit/spinbutton.md @@ -47,7 +47,7 @@ This code component provides a wrapper around the [Fluent UI SpinButton](https:/ | `Max` | Min value of the control. If not provided, the control has no minimum value. | | `Step` | Difference between two adjacent values of the control. This value is used to calculate the precision of the input if no precision is given. The precision calculated this way will always be >= 0. | | `Value` | Current value of the control. | -| `DefaultValue` | Intial value of the control when first rendered. | +| `DefaultValue` | Initial value of the control when first rendered. | | `Suffix` | Suffix to define any unit (e.g. cm, kg, ml) | ## Additional properties diff --git a/power-platform/important-changes-coming.md b/power-platform/important-changes-coming.md index b9685de8f5..ddf1593c2b 100644 --- a/power-platform/important-changes-coming.md +++ b/power-platform/important-changes-coming.md @@ -455,7 +455,7 @@ The Windows Player for canvas apps will no longer be able to be used. You must replace usage of the Dynamics 365 connector with the Microsoft Dataverse connector. -- **Microsoft Dataverse**: This is the newest connector and the main connector avilable for Dataverse usage. All new features, performance work, and enhancements will be available on this connector. A +- **Microsoft Dataverse**: This is the newest connector and the main connector available for Dataverse usage. All new features, performance work, and enhancements will be available on this connector. A **Mapping of common actions** diff --git a/power-platform/power-fx/operators.md b/power-platform/power-fx/operators.md index ba639e2781..1621af47e0 100644 --- a/power-platform/power-fx/operators.md +++ b/power-platform/power-fx/operators.md @@ -296,7 +296,7 @@ Behind the scenes, a mapping is maintained between the display names seen in for > Logical names are not translated when moving an app between environments. For Dataverse system entity and field names, this should not be a problem as logical names are consistent across environments. But any custom fields, such as **cra3a_customfield** in this example above, may have a different environment prefix (**cra3a** in this case). Display names are preferred as they can be matched against display names in the new environment. ## Name disambiguation -Since display names are not unique, the same display name may appear more than once in the same entity. When this happens, the logical name will be added to the end of the display name in parenthesis for one of more of the conflicting names. Building on the example above, if there was a second field with the same display name of **Custom Field** with a logical name of **cra3a_customfieldalt** then the suggestions would show: +Since display names are not unique, the same display name may appear more than once in the same entity. When this happens, the logical name will be added to the end of the display name in parentheses for one of more of the conflicting names. Building on the example above, if there was a second field with the same display name of **Custom Field** with a logical name of **cra3a_customfieldalt** then the suggestions would show: > [!div class="mx-imgBorder"] > ![Studio formula bar showing the use of the logical name cr5e3_customfieldalt to disambiguate the two versions of "Custom Field."](media/operators/customfield_suggest_alt.png) diff --git a/power-platform/power-fx/reference/function-copy.md b/power-platform/power-fx/reference/function-copy.md index ff19b114f0..cc678655e1 100644 --- a/power-platform/power-fx/reference/function-copy.md +++ b/power-platform/power-fx/reference/function-copy.md @@ -22,7 +22,7 @@ Copies text to the clipboard on the device where the app is running. The **Copy** function takes any text value and copies it to the clipboard. Regardless of the contents of the text, the clipboard will contain plain text without any special mime type. The function is considered a side-effects function and as a result it can only be used in behavior properties. > [!NOTE] -> The **Copy()** function is limited to the access given to clipboard by the host of the app. As a result, embedded apps scenarios such as Power Apps in SharePoint, embedded apps in Power BI, Teams, etc. don't support **Copy()**. Other embedded scenarios might not support the fuction either. Makers should use **[IfError()](./function-iferror.md)** to ensure the action to copy to clipboard was effective and if not, to properly alert the user that the copy failed. +> The **Copy()** function is limited to the access given to clipboard by the host of the app. As a result, embedded apps scenarios such as Power Apps in SharePoint, embedded apps in Power BI, Teams, etc. don't support **Copy()**. Other embedded scenarios might not support the function either. Makers should use **[IfError()](./function-iferror.md)** to ensure the action to copy to clipboard was effective and if not, to properly alert the user that the copy failed. ## Syntax diff --git a/power-platform/power-fx/reference/function-datasourceinfo.md b/power-platform/power-fx/reference/function-datasourceinfo.md index 520f7cfc5f..acc04bb349 100644 --- a/power-platform/power-fx/reference/function-datasourceinfo.md +++ b/power-platform/power-fx/reference/function-datasourceinfo.md @@ -76,7 +76,7 @@ You can also use **DataSourceInfo** to obtain information about a data source as - _ColumnName_ – Optional. The column name for which to retrieve column-level information. For information at the data-source level, the _ColumnName_ argument can't be used. > [!NOTE] -> In Power Apps prior to version 3.24042, column names were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. Afer this version, all apps were automatically updated to the new syntax described in this article. +> In Power Apps prior to version 3.24042, column names were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. After this version, all apps were automatically updated to the new syntax described in this article. ## Examples diff --git a/power-platform/power-fx/reference/function-filter-lookup.md b/power-platform/power-fx/reference/function-filter-lookup.md index 84a43f20df..61ff505556 100644 --- a/power-platform/power-fx/reference/function-filter-lookup.md +++ b/power-platform/power-fx/reference/function-filter-lookup.md @@ -62,7 +62,7 @@ The **Search** function finds records in a table that contain a string in one of - _Column(s)_ - Required. The names of columns within _Table_ to search. If _SearchString_ is found within the data of any of these columns as a partial match, the full record will be returned. > [!NOTE] -> In Power Apps prior to version 3.24042, column names for the **Search** function were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. Afer this version, all apps were automatically updated to the new syntax described in this article. +> In Power Apps prior to version 3.24042, column names for the **Search** function were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. After this version, all apps were automatically updated to the new syntax described in this article. **LookUp**(Table*, *Formula* [, *ReductionFormula\* ] ) diff --git a/power-platform/power-fx/reference/function-find.md b/power-platform/power-fx/reference/function-find.md index 451090e980..f1c4b47710 100644 --- a/power-platform/power-fx/reference/function-find.md +++ b/power-platform/power-fx/reference/function-find.md @@ -42,7 +42,7 @@ The **Find** function looks for a string within another string and is case sensi | Formula | Description | Result | | ------------------------------------------------ | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------- | | **Find("World", "Hello World")** | Returns the starting position of **"World"**. | 7 | -| **Find("World", "Hello World, Hello World", 10)** | Returns the starting position of the first occurence of **"World"** after the 10th character. | 20 | +| **Find("World", "Hello World, Hello World", 10)** | Returns the starting position of the first occurrence of **"World"** after the 10th character. | 20 | | **Find("Mars", "Hello World")** | Returns blank since the FindString is not in the WithinString | Blank() | diff --git a/power-platform/power-fx/reference/function-groupby.md b/power-platform/power-fx/reference/function-groupby.md index 0b859ef8e6..32e48ed895 100644 --- a/power-platform/power-fx/reference/function-groupby.md +++ b/power-platform/power-fx/reference/function-groupby.md @@ -46,7 +46,7 @@ You can also aggregate results based on a grouping: A table is a value in Power Apps, just like a string or a number. You can specify a table as an argument for a function, and a function can return a table. **GroupBy** and **Ungroup** don't modify a table; instead they take a table as an argument and return a different table. See [working with tables](/power-apps/maker/canvas-apps/working-with-tables) for more details. > [!NOTE] -> In Power Apps prior to version 3.24042, column names were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. Afer this version, all apps were automatically updated to the new syntax described in this article. +> In Power Apps prior to version 3.24042, column names were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. After this version, all apps were automatically updated to the new syntax described in this article. ## Syntax diff --git a/power-platform/power-fx/reference/function-iferror.md b/power-platform/power-fx/reference/function-iferror.md index 63e61307e9..431a8200c9 100644 --- a/power-platform/power-fx/reference/function-iferror.md +++ b/power-platform/power-fx/reference/function-iferror.md @@ -117,7 +117,7 @@ Error records include: | **Message** | Text string | Message about the error, suitable to be displayed to the end user. | | **Source** | Text string | Location in where the error originated, used for reporting. For example, for a formula bound to a control property, this will be in the form _ControlName.PropertyName_. | | **Observed** | Text string | Location in where the error is surfaced to the user, used for reporting. For example, for a formula bound to a control property, this will be in the form _ControlName.PropertyName_. | -| **Details** | Record | Details about the error. At present, details are provided only for network errors. This record includes **HttpStatusCode** whcih contains the HTTP status code and **HttpResponse** which contains the body of the response from the connector or service. | +| **Details** | Record | Details about the error. At present, details are provided only for network errors. This record includes **HttpStatusCode** which contains the HTTP status code and **HttpResponse** which contains the body of the response from the connector or service. | For example, consider the following formula as a [**Button**](/power-apps/maker/canvas-apps/controls/control-button) control's **OnSelect** property: @@ -218,7 +218,7 @@ If( StartDate > EndDate, Error( { Kind: ErrorKind.Validation, Message: "Start Date must be before End Date" } ) ) ``` -In this example, some errors are allowed to pass through while others are supressed and replaced with a value. In the first case, **b** will be in an error state because the **Value** function has an invalid argument. Because this is unexpected by the formula writer, it is passed through so the user will see it. In the second case, with the same formula, **b** will have the value 0, resulting in a division by zero. In this case, the formula writer may know that this is acceptable for this logic, suppress the error (no banner is shown), and return -1 instead. +In this example, some errors are allowed to pass through while others are suppressed and replaced with a value. In the first case, **b** will be in an error state because the **Value** function has an invalid argument. Because this is unexpected by the formula writer, it is passed through so the user will see it. In the second case, with the same formula, **b** will have the value 0, resulting in a division by zero. In this case, the formula writer may know that this is acceptable for this logic, suppress the error (no banner is shown), and return -1 instead. ```powerapps-dot With( {a: 1, b: Value("a")}, diff --git a/power-platform/power-fx/reference/function-remove-removeif.md b/power-platform/power-fx/reference/function-remove-removeif.md index c3747e407d..c49af7eae9 100644 --- a/power-platform/power-fx/reference/function-remove-removeif.md +++ b/power-platform/power-fx/reference/function-remove-removeif.md @@ -47,7 +47,7 @@ You can also use the **[Clear](function-clear-collect-clearcollect.md)** functio When used with a data source, these functions cannot be delegated. Only the first portion of the data source will be retrieved and then the function applied. This may not represent the complete story. A warning may appear at authoring time to remind you of this limitation. #### Delegation support (Experimental) -Delegation support for RemoveIf is now in Experimental Preview (default OFF) for data sources that support it. If a data source doesn't support this feature, Power Apps will send a query to the server and retrieve all data that matches the filter expression up to the maxium of either 500, 2000, or the data page size. Then, it will perform a delete operation on each of those records with individual calls to the server. +Delegation support for RemoveIf is now in Experimental Preview (default OFF) for data sources that support it. If a data source doesn't support this feature, Power Apps will send a query to the server and retrieve all data that matches the filter expression up to the maximum of either 500, 2000, or the data page size. Then, it will perform a delete operation on each of those records with individual calls to the server. ## Syntax diff --git a/power-platform/power-fx/reference/function-setfocus.md b/power-platform/power-fx/reference/function-setfocus.md index ccda37c26e..152cf15b94 100644 --- a/power-platform/power-fx/reference/function-setfocus.md +++ b/power-platform/power-fx/reference/function-setfocus.md @@ -67,7 +67,7 @@ You can use **SetFocus** only in [behavior formulas](/power-apps/maker/canvas-ap ### Focus on a newly exposed or enabled input control -Many shopping carts allow the customer to use the shipping address as the billing address, alleviating the need to enter the same information twice. If a different billing address is desired, the billing address text input boxes are enabled, and it is helpful to guide the customer to the these newly enabled controls for faster data entry. +Many shopping carts allow the customer to use the shipping address as the billing address, alleviating the need to enter the same information twice. If a different billing address is desired, the billing address text input boxes are enabled, and it is helpful to guide the customer to these newly enabled controls for faster data entry. ![Animation of choosing to use a custom Billing address, with focus moved to the Billing name input control as a result,turning off the automatic sync with the Shipping addresss.](media/function-setfocus/shipping-billing.gif) diff --git a/power-platform/power-fx/reference/function-table-shaping.md b/power-platform/power-fx/reference/function-table-shaping.md index b12c272792..80705e4490 100644 --- a/power-platform/power-fx/reference/function-table-shaping.md +++ b/power-platform/power-fx/reference/function-table-shaping.md @@ -69,7 +69,7 @@ However, the output of these functions is subject to the [non-delegation record If you use **AddColumns** in this manner, **Filter** must make separate calls to the data source for each of those first records in **RealEstateAgents**, which causes lots of network chatter. If **[dbo](.[AllListings]** is small enough and doesn't change often. You can call the **Collect** function in [**OnStart**](signals.md#app) to cache the data source in your app when it starts. As an alternative, you could restructure your app so that you pull in the related records only when the user asks for them. > [!NOTE] -> In Power Apps prior to version 3.24042, column names were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. Afer this version, all apps were automatically updated to the new syntax described in this article. +> In Power Apps prior to version 3.24042, column names were specified with a text string using double quotes, and if connected to a data source they also needed to be logical names. For example, the logical name **"cr43e_name"** with double quotes was used instead of the display name **Name** without quotes. For SharePoint and Excel data sources that contain column names with spaces, each space was specified with **"\_x0020\_"**, for example **"Column Name"** as **"Column_x0020_Name"**. After this version, all apps were automatically updated to the new syntax described in this article. ## Syntax diff --git a/power-platform/power-fx/reference/function-update-updateif.md b/power-platform/power-fx/reference/function-update-updateif.md index dba16e1101..fd5c6391f3 100644 --- a/power-platform/power-fx/reference/function-update-updateif.md +++ b/power-platform/power-fx/reference/function-update-updateif.md @@ -48,7 +48,7 @@ Both **Update** and **UpdateIf** return the modified data source as a [table](/p When used with a data source, these functions cannot be delegated. Only the first portion of the data source will be retrieved and then the function applied. This may not represent the complete story. A warning may appear at authoring time to remind you of this limitation. #### Delegation support (Experimental) -Delegation support for UpdateIf and RemoveIf is now in Experimental Preview (default OFF) for data sources that support it. If a data source does not support this feature, Power Apps will now send a query to the server and retrieve all data that matches the filter expression up to the maxium of either 500, 2000, or the data page size. Then, it will update those records and send each back to the server to be updated. +Delegation support for UpdateIf and RemoveIf is now in Experimental Preview (default OFF) for data sources that support it. If a data source does not support this feature, Power Apps will now send a query to the server and retrieve all data that matches the filter expression up to the maximum of either 500, 2000, or the data page size. Then, it will update those records and send each back to the server to be updated. ## Syntax diff --git a/power-platform/power-fx/reference/operators.md b/power-platform/power-fx/reference/operators.md index aad02992a6..0ad1eb3465 100644 --- a/power-platform/power-fx/reference/operators.md +++ b/power-platform/power-fx/reference/operators.md @@ -307,7 +307,7 @@ Behind the scenes, a mapping is maintained between the display names seen in for ## Name disambiguation -Since display names aren't unique, the same display name may appear more than once in the same table. When this happens, the logical name will be added to the end of the display name in parenthesis for one of more of the conflicting names. Building on the example above, if there was a second field with the same display name of **Custom Field** with a logical name of **cra3a_customfieldalt** then the suggestions would show: +Since display names aren't unique, the same display name may appear more than once in the same table. When this happens, the logical name will be added to the end of the display name in parentheses for one of more of the conflicting names. Building on the example above, if there was a second field with the same display name of **Custom Field** with a logical name of **cra3a_customfieldalt** then the suggestions would show: > [!div class="mx-imgBorder"] > ![Studio formula bar showing the use of the logical name cr5e3_customfieldalt to disambiguate the two versions of "Custom Field."](media/operators/customfield_suggest_alt.png) diff --git a/power-platform/well-architected/experience-optimization/design-standards.md b/power-platform/well-architected/experience-optimization/design-standards.md index 4b6ab3f9ff..0c40039ea7 100644 --- a/power-platform/well-architected/experience-optimization/design-standards.md +++ b/power-platform/well-architected/experience-optimization/design-standards.md @@ -126,7 +126,7 @@ Interaction is where accessibility matters the most. If a user can't navigate a - *Hyperlinks*. Usability and accessibility of hyperlinks can be improved by making them clear, concise, and meaningful out of context. Apply sufficient color contrast and visually differentiate from other content. - *Tables*. Relying on visual cues alone isn't sufficient to create an accessible table. Structural markup allows assistive technology to recognize headers and data cells. - *Forms*. Input fields, used for various web interactions, often raise accessibility concerns for individuals who use screen readers or keyboards. -- *Focus*. Focus visibility helps users who rely on the keyboard to navigate the page, by visually indicating the element they interact with next. Sometimes focus needs to be moved programatically or limited to a specific area to optimize the experience. +- *Focus*. Focus visibility helps users who rely on the keyboard to navigate the page, by visually indicating the element they interact with next. Sometimes focus needs to be moved programmatically or limited to a specific area to optimize the experience. - *State changes*. Specify text for any state change and announcements. Communicating error states and guiding users through error recovery (such as missing information or system issue) is critical. ## Power Platform facilitation