From 45b89b8cd2da863d73102df7849e7b9a347fb0e0 Mon Sep 17 00:00:00 2001 From: Blake-Madden <66873089+Blake-Madden@users.noreply.github.com> Date: Fri, 7 Jun 2024 11:59:20 -0400 Subject: [PATCH] Fix a few typos --- power-platform/admin/analytics-common-data-service.md | 2 +- power-platform/admin/configure-default-sync-filters.md | 2 +- power-platform/admin/create-users.md | 2 +- power-platform/admin/environment-groups.md | 2 +- power-platform/admin/get-recommendations-licensing.md | 2 +- ...-field-security-affects-synchronization-between-outlook.md | 2 +- power-platform/admin/how-record-access-determined.md | 2 +- power-platform/admin/manage-encryption-key.md | 2 +- .../power-automate-licensing/when-flows-are-turned-off.md | 2 +- power-platform/admin/settings-features.md | 2 +- power-platform/admin/sync-logic.md | 2 +- power-platform/admin/trial-environments.md | 2 +- power-platform/admin/view-license-consumption-issues.md | 2 +- power-platform/alm/solution-api.md | 2 +- .../developer/cli/reference/includes/copilot-list-intro.md | 2 +- power-platform/guidance/adoption/training-strategy.md | 2 +- power-platform/guidance/coe/power-bi-nurture.md | 2 +- power-platform/guidance/coe/starter-kit-explained.md | 2 +- power-platform/guidance/creator-kit/picker.md | 2 +- power-platform/power-fx/reference/function-first-last.md | 4 ++-- power-platform/power-fx/reference/function-iferror.md | 2 +- .../power-fx/reference/function-send-app-notification.md | 2 +- power-platform/power-fx/reference/function-setfocus.md | 4 ++-- power-platform/power-fx/reference/object-app.md | 2 +- power-platform/power-fx/reference/object-host.md | 2 +- power-platform/power-fx/working-with-json.md | 2 +- 26 files changed, 28 insertions(+), 28 deletions(-) diff --git a/power-platform/admin/analytics-common-data-service.md b/power-platform/admin/analytics-common-data-service.md index 9d4184d33..bb67a457f 100644 --- a/power-platform/admin/analytics-common-data-service.md +++ b/power-platform/admin/analytics-common-data-service.md @@ -149,7 +149,7 @@ For more information on the different roles for managing your tenant across the > | Workflow Executions | This chart shows how many workflows have been executed in the environment with a Dataverse database over the specified time. | > | System Jobs Pass Rate | This chart shows the system job's pass rate as percentage of system jobs that were executed in the environment with a Dataverse database over the specified time. | > | System Jobs Throughput/Minute | This chart shows the average system jobs that have been executed per hour in the environment with a Dataverse database over the specified time. | -> | Executions and Backlog | This chart shows the number of executions and the backlog for system jobs in the environment with a Dataverse databaset over the specified time. | +> | Executions and Backlog | This chart shows the number of executions and the backlog for system jobs in the environment with a Dataverse database over the specified time. | > | Most Active Workflows | This chart shows top 10 most executed workflows in the environment with a Dataverse database over the specified time. | > | Top Workflows by Failures | This chart shows top 10 most failing workflows in the environment with a Dataverse database over the specified time. Click on a workflow to see the failures and their number of occurrences. | diff --git a/power-platform/admin/configure-default-sync-filters.md b/power-platform/admin/configure-default-sync-filters.md index 2d6e30873..9ce56b931 100644 --- a/power-platform/admin/configure-default-sync-filters.md +++ b/power-platform/admin/configure-default-sync-filters.md @@ -46,7 +46,7 @@ Open XrmToolBox and connect to your organization. On the **Configuration** tab, ## Step 1. Check the current default sync filter -1. In [XrmToolBox](https://www.xrmtoolbox.com/), go to the the **Tools** menu and open **Sync Filter Manager.** +1. In [XrmToolBox](https://www.xrmtoolbox.com/), go to the **Tools** menu and open **Sync Filter Manager.** > [!div class="mx-imgBorder"] > ![Open the Sync Filter Manager.](media/default-sync-filter-5.png "Sync filter manager") diff --git a/power-platform/admin/create-users.md b/power-platform/admin/create-users.md index 5d462d753..28a1c21b8 100644 --- a/power-platform/admin/create-users.md +++ b/power-platform/admin/create-users.md @@ -372,7 +372,7 @@ We are in the process of moving application user management from the legacy web A stub user is a user record that has been created as a placeholder. For example, records have been imported that refer to this user but the user doesn't exist in customer engagement apps. This user can't sign in, can't be enabled, and can't be synchronized to Microsoft 365. This type of user can only be created through data import. > [!CAUTION] -> To prevent creating duplicate user records with the same UPN or throw errors during data import workflows, ensure that users exist in Entra ID and are sufficiently licensed for pre-provisioning. Office licenses aren't supported for pre-provisioning, but any Power Apps Premium or Dynamics 365 licenses are supported for pre-provisioning. Once users meet these requirements, they are syncronized with Dataverse environments. +> To prevent creating duplicate user records with the same UPN or throw errors during data import workflows, ensure that users exist in Entra ID and are sufficiently licensed for pre-provisioning. Office licenses aren't supported for pre-provisioning, but any Power Apps Premium or Dynamics 365 licenses are supported for pre-provisioning. Once users meet these requirements, they are synchronized with Dataverse environments. > If you must reassign records from a stub user to another user, use the [Add-BulkRecordsToUsers](https://github.com/microsoft/PowerApps-Samples/tree/master/powershell/UserManagement/Microsoft.PowerPlatform.Administration.UserManagement#command-add-bulkrecordstousers). A default security role is automatically assigned to these imported users. The **Salesperson** security role is assigned in an environment and the **Basic User** security role is assigned in a Power Apps environment. diff --git a/power-platform/admin/environment-groups.md b/power-platform/admin/environment-groups.md index 46e8d3fe4..ad969f60f 100644 --- a/power-platform/admin/environment-groups.md +++ b/power-platform/admin/environment-groups.md @@ -32,7 +32,7 @@ Admins can apply various rules to groups to govern many environments in bulk, re There are many ways to manage pockets of environments within your tenant using environment groups. For example, global organizations can create an environment group for all environments in each geographic region to ensure compliance with legal and regulatory requirements. You can also organize environment groups by department or other criteria. -:::image type="content" source="media/environment-groups-strategy.png" alt-text="Diagram depicting one strategy for using environment groups and aligning it to your existing orgnizational structure."::: +:::image type="content" source="media/environment-groups-strategy.png" alt-text="Diagram depicting one strategy for using environment groups and aligning it to your existing organizational structure."::: This article covers how to augment your _default environment strategy_ by combining _environment groups_ with [_default environment routing_](default-environment-routing.md). Default environment routing gives makers their own personal developer environment. This environment is a secure space to build with Microsoft Dataverse and is similar to [OneDrive](https://www.microsoft.com/microsoft-365/onedrive/online-cloud-storage) for personal productivity. diff --git a/power-platform/admin/get-recommendations-licensing.md b/power-platform/admin/get-recommendations-licensing.md index 23cffc546..096c6df46 100644 --- a/power-platform/admin/get-recommendations-licensing.md +++ b/power-platform/admin/get-recommendations-licensing.md @@ -54,7 +54,7 @@ Complete the following steps to assign Power Apps premium licenses to users. 8. Select the license you want to assign to the users. Click **Assign**. -## View recently assiged licenses +## View recently assigned licenses Near the bottom of the page, admins can see the history of license assignment, including a summary of users who were assigned licenses and the date of assignment. [!INCLUDE[footer-include](../includes/footer-banner.md)] diff --git a/power-platform/admin/how-field-security-affects-synchronization-between-outlook.md b/power-platform/admin/how-field-security-affects-synchronization-between-outlook.md index 606db4d20..74bc56218 100644 --- a/power-platform/admin/how-field-security-affects-synchronization-between-outlook.md +++ b/power-platform/admin/how-field-security-affects-synchronization-between-outlook.md @@ -69,7 +69,7 @@ Securing a field with field-level security can impact synchronization between cu 6. Select the new profile > **Users** > **Add** -7. Select users and then celect **Select** > **Add**. +7. Select users and then select **Select** > **Add**. ### Set field permissions With a field security profile created and users added to the profile, John can now set permissions on the fields to match the organization's requirements. diff --git a/power-platform/admin/how-record-access-determined.md b/power-platform/admin/how-record-access-determined.md index 8289eb23f..88533a098 100644 --- a/power-platform/admin/how-record-access-determined.md +++ b/power-platform/admin/how-record-access-determined.md @@ -106,7 +106,7 @@ In this case, the user would have access to the record if both of the following ## Record access check -For each record that is displayed in the web client, the user has the ability to see how they were granted access to the record through the [**Check Access**](/power-apps/user/access-checker) option on the command bar. The user can also see other users who have accecss to the record and their respective access level. +For each record that is displayed in the web client, the user has the ability to see how they were granted access to the record through the [**Check Access**](/power-apps/user/access-checker) option on the command bar. The user can also see other users who have access to the record and their respective access level. There are two environment database settings to configure to use the **Who has access** feature. [Install the **OrganizationSettingsEditor** tool](environment-database-settings.md#install-the-organizationsettingseditor-tool) and set the following to true: diff --git a/power-platform/admin/manage-encryption-key.md b/power-platform/admin/manage-encryption-key.md index 7aadb9eca..9aab888ae 100644 --- a/power-platform/admin/manage-encryption-key.md +++ b/power-platform/admin/manage-encryption-key.md @@ -21,7 +21,7 @@ All environments of Microsoft Dataverse use [!INCLUDE[pn_MS_SQL_Server](../inclu By default, [!INCLUDE[cc_Microsoft](../includes/cc-microsoft.md)] stores and manages the database encryption key for your environments so you don't have to. The manage keys feature in the Microsoft Power Platform admin center gives administrators the ability to self-manage the database encryption key that is associated with the Dataverse tenant. > [!IMPORTANT] -> - As of June 2, 2023, this service is upgraded to [Customer-managed encryption key](customer-managed-key.md). New customers who need to manage their own encryption key will use the upgraded service as this service is no longer offerred. +> - As of June 2, 2023, this service is upgraded to [Customer-managed encryption key](customer-managed-key.md). New customers who need to manage their own encryption key will use the upgraded service as this service is no longer offered. > - Self-managed database encryption keys are only available for customers who have more than 1000 Power Apps per user licenses, or more than 1000 Dynamics 365 Enterprise licenses, or more than 1000 licenses from a combination of both in a single tenant. To opt in to this program, submit a [support request](./support-overview.md#using-support). Encryption key management is only applicable to Azure SQL environment databases. The following features and services continue to use the Microsoft-managed encryption key to encrypt their data and can't be encrypted with the self-managed encryption key: diff --git a/power-platform/admin/power-automate-licensing/when-flows-are-turned-off.md b/power-platform/admin/power-automate-licensing/when-flows-are-turned-off.md index f9f7d0600..f4b4b7e8b 100644 --- a/power-platform/admin/power-automate-licensing/when-flows-are-turned-off.md +++ b/power-platform/admin/power-automate-licensing/when-flows-are-turned-off.md @@ -31,7 +31,7 @@ To ensure compliance and prevent surprises, admins should keep up-to-date with t - Admins are encouraged to enable Auto-claim so license assignment is automated. - Admins should periodically review the Power Automate license reporting, which now includes both tenant and environment level reporting views. To learn more, go to [View license consumption for Power Apps and Power Automate (preview)](../view-license-consumption-issues.md). - The report identifies flows that require a license for a subset of scenarios that are in scope of the power platform licensing guide. This subset of scenarios constitues the current scope of enforcement. We expect customers to ensure compliance with all licensing requirements covered in the [Power Platform Licensing Guide](https://go.microsoft.com/fwlink/?linkid=2085130). We expect to add more scenarios to this report to help administrators identify flows that require their attention. We might broaden the scope of enforcements at such time. + The report identifies flows that require a license for a subset of scenarios that are in scope of the power platform licensing guide. This subset of scenarios constitutes the current scope of enforcement. We expect customers to ensure compliance with all licensing requirements covered in the [Power Platform Licensing Guide](https://go.microsoft.com/fwlink/?linkid=2085130). We expect to add more scenarios to this report to help administrators identify flows that require their attention. We might broaden the scope of enforcements at such time. ## Types of enforcements diff --git a/power-platform/admin/settings-features.md b/power-platform/admin/settings-features.md index 107137d03..97a9546e9 100644 --- a/power-platform/admin/settings-features.md +++ b/power-platform/admin/settings-features.md @@ -144,7 +144,7 @@ Allow canvas editors to insert the Copilot answer component, which allows users | Enable Finance and Operations user impersonation in Dataverse | When enabled, the Finance and Operations application in this environment has permissions to impersonate Dataverse users. This allows users of Finance and Operations to make calls to Dataverse which run as that same user in Dataverse, using the Dataverse permissions assigned to that user. Only select this option if the Finance and Operations administrator is trusted with the same level of permissions in Dataverse as the Dataverse administrator. | Off | > [!IMPORTANT] -> Beginning March 1, 2024 the **Enable Finance and Operations user impersonation in Dataverse** toggle will be removed. With continued efforts to unify finance and operations apps with the Power Platform through the [Power Platform integration](/dynamics365/fin-ops-core/dev-itpro/power-platform/overview) and [unified admin exeriences](unified-experience/finance-operations-apps-overview.md), finance and operations apps are now considered applications within the Power Platform environment. In a unified environment, the capabilities granted by the toggle are now assumed to be true for any environment with finance and operations apps installed with the same level of governance, oversight and scrutiny as all other apps in a Power Platform environment. +> Beginning March 1, 2024 the **Enable Finance and Operations user impersonation in Dataverse** toggle will be removed. With continued efforts to unify finance and operations apps with the Power Platform through the [Power Platform integration](/dynamics365/fin-ops-core/dev-itpro/power-platform/overview) and [unified admin experiences](unified-experience/finance-operations-apps-overview.md), finance and operations apps are now considered applications within the Power Platform environment. In a unified environment, the capabilities granted by the toggle are now assumed to be true for any environment with finance and operations apps installed with the same level of governance, oversight and scrutiny as all other apps in a Power Platform environment. ## Data validation | Setting | Description | Default value | diff --git a/power-platform/admin/sync-logic.md b/power-platform/admin/sync-logic.md index 420755342..5933ffd8f 100644 --- a/power-platform/admin/sync-logic.md +++ b/power-platform/admin/sync-logic.md @@ -63,7 +63,7 @@ How appointments sync between Dynamics 365 and Exchange depends on the sync dire ### Appointment organizer -The appointment organizer is a key field for appointment synchronization. It drives different synchronization behaviors. For example, only the Dynaamics 365 appointment organizer can synchronize and distribute appointments from Dynamics 365 to Exchange attendees. When you create appointments using customizations such as Power Automate or custom code, make sure the organizer is specified correctly. The organizer field isn't exposed on the appointment form by default. You can add it to forms, views, or advanced find queries, as needed, to confirm the value is present and correct. +The appointment organizer is a key field for appointment synchronization. It drives different synchronization behaviors. For example, only the Dynamics 365 appointment organizer can synchronize and distribute appointments from Dynamics 365 to Exchange attendees. When you create appointments using customizations such as Power Automate or custom code, make sure the organizer is specified correctly. The organizer field isn't exposed on the appointment form by default. You can add it to forms, views, or advanced find queries, as needed, to confirm the value is present and correct. If an appointment organizer is changed in Dynamics 365 after it has been synchronized to Exchange, this may cause the original organizer to issue a cancellation. This can happen because the appointment no longer meets the conditions of the user’s sync filters. Additionally, the new organizer may synchronize the appointment as a new meeting in Exchange. The behavior of sending a cancellation from the previous organizer can be modified using the [OrgDBOrgSetting](https://support.microsoft.com/en-us/topic/orgdborgsettings-tool-for-microsoft-dynamics-crm-20a10f46-2a24-a156-7144-365d49b842ba) named DistinctPhysicalAndLogicalDeletesForExchangeSync. diff --git a/power-platform/admin/trial-environments.md b/power-platform/admin/trial-environments.md index 7a2010ce5..f78e7f1a0 100644 --- a/power-platform/admin/trial-environments.md +++ b/power-platform/admin/trial-environments.md @@ -155,7 +155,7 @@ Your trial will be extended 30 days from the original expiration date. ## Extend a trial (subscription-based) environment -The expiration of subscription-based trial (also know as an admin trial) environments is tied to the expiration of the subscription. Therefore, subscription-based trial environments cannot be independently extended. There are limited options for extending admin trial subscriptions which affects extending the expiration of any associated trial environments. +The expiration of subscription-based trial (also known as an admin trial) environments is tied to the expiration of the subscription. Therefore, subscription-based trial environments cannot be independently extended. There are limited options for extending admin trial subscriptions which affects extending the expiration of any associated trial environments. **To extend a subscription-based (admin) trial:** diff --git a/power-platform/admin/view-license-consumption-issues.md b/power-platform/admin/view-license-consumption-issues.md index 84acad239..577d26f71 100644 --- a/power-platform/admin/view-license-consumption-issues.md +++ b/power-platform/admin/view-license-consumption-issues.md @@ -134,7 +134,7 @@ The **Environments** tab on the **Licenses (preview)** page displays licensing i | Premium feature | Indicates if a premium feature, such as a premium connector, custom connector, or Dataverse connector, was used in the flow. | | Flow type | Indicates if the flow is scheduled, instant, or automated. | | Download | Downloads the information in CSV format. Select a specific license type to start the download. After a CSV file is generated, you can download the same file again within five days without having to start a new download. | -| Attention needed | Summary count of flows requiring licensing attention, which includes:
| +| Attention needed | Summary count of flows requiring licensing attention, which includes:
| ## Other ways to view licensing pages diff --git a/power-platform/alm/solution-api.md b/power-platform/alm/solution-api.md index 424775724..89ce9065c 100644 --- a/power-platform/alm/solution-api.md +++ b/power-platform/alm/solution-api.md @@ -484,7 +484,7 @@ public void DependencyReport(Dependency dependency) requiredComponentTypeName = opt.Label.UserLocalizedLabel.Label; } } - // The name or display name of the compoent is retrieved in different ways depending on the component type + // The name or display name of the component is retrieved in different ways depending on the component type dependentComponentName = getComponentName(dependency.DependentComponentType.Value, (Guid)dependency.DependentComponentObjectId); requiredComponentName = getComponentName(dependency.RequiredComponentType.Value, (Guid)dependency.RequiredComponentObjectId); diff --git a/power-platform/developer/cli/reference/includes/copilot-list-intro.md b/power-platform/developer/cli/reference/includes/copilot-list-intro.md index 4dc88d94b..4546744d2 100644 --- a/power-platform/developer/cli/reference/includes/copilot-list-intro.md +++ b/power-platform/developer/cli/reference/includes/copilot-list-intro.md @@ -10,6 +10,6 @@ The command returns output like the following: ```Text Name Bot ID Component State Is Managed Solution ID Status Code State Code -Ask Me Anytyhing Copilot 584e012c-dc95-46d6-af5a-1263b6a44342 Published Unmanaged 285af946-6383-49a0-8615-4e2afafeaf38 Active Provisioned +Ask Me Anything Copilot 584e012c-dc95-46d6-af5a-1263b6a44342 Published Unmanaged 285af946-6383-49a0-8615-4e2afafeaf38 Active Provisioned New Test Copilot 9ee3f7aa-ab79-4cf6-a726-d85c8c18cc3e Published Unmanaged 285af946-6383-49a0-8615-4e2afafeaf38 Active Provisioned ``` diff --git a/power-platform/guidance/adoption/training-strategy.md b/power-platform/guidance/adoption/training-strategy.md index 949d3fffd..11dd68ba6 100644 --- a/power-platform/guidance/adoption/training-strategy.md +++ b/power-platform/guidance/adoption/training-strategy.md @@ -35,7 +35,7 @@ Look for people with skills and strengths in the following roles: - **Citizen developers**: Continue to bring their day-to-day experience to how their job is done; when provided the right tools and training, can create apps to drive value. -- **Pro developers**: Will design advanced interfaces using [Power Apps componenet framework](/powerapps/developer/component-framework/overview) in addition to building complex relationships or integrations with other applications, when the out-of-the-box limits have been reached, and the app needs to be extended. +- **Pro developers**: Will design advanced interfaces using [Power Apps component framework](/powerapps/developer/component-framework/overview) in addition to building complex relationships or integrations with other applications, when the out-of-the-box limits have been reached, and the app needs to be extended. - **Trainers**: Are necessary to train others on how to use the apps that are built and made available across the organization, in addition to providing training on how to build apps. diff --git a/power-platform/guidance/coe/power-bi-nurture.md b/power-platform/guidance/coe/power-bi-nurture.md index e9818ccae..b62133d9b 100644 --- a/power-platform/guidance/coe/power-bi-nurture.md +++ b/power-platform/guidance/coe/power-bi-nurture.md @@ -43,7 +43,7 @@ The **Power Apps Adoption** page shows you further insights into how Power Apps ### Desktop flows usage -The **Desktop flows usage** page provides an overview of UI-based robotic process automateion (RPA) flow runs in your environment: +The **Desktop flows usage** page provides an overview of UI-based robotic process automation (RPA) flow runs in your environment: - Number of runs per date and desktop flow type - Total number of runs diff --git a/power-platform/guidance/coe/starter-kit-explained.md b/power-platform/guidance/coe/starter-kit-explained.md index ab171709e..51a1bd72a 100644 --- a/power-platform/guidance/coe/starter-kit-explained.md +++ b/power-platform/guidance/coe/starter-kit-explained.md @@ -50,7 +50,7 @@ Admin tasks are defined in a model-driven app and insights provided in a Power B Set up your own SharePoint Hub or Teams site to share success stories, upcoming events, rules of engagement and guidelines with your maker community. -The Power Platform communication site is a SharePoint Online template, designed to provide a starting point of content and page templates as your're setting up your internal Power Platform wiki and community site. +The Power Platform communication site is a SharePoint Online template, designed to provide a starting point of content and page templates as you're setting up your internal Power Platform wiki and community site. More information: [Get starter with the Power Platform communication site template](../adoption/wiki-community.md#get-started-with-the-power-platform-communication-site-template) diff --git a/power-platform/guidance/creator-kit/picker.md b/power-platform/guidance/creator-kit/picker.md index 02fe319b9..0b4d7ec3a 100644 --- a/power-platform/guidance/creator-kit/picker.md +++ b/power-platform/guidance/creator-kit/picker.md @@ -63,7 +63,7 @@ Search(colSuggestions,TagPicker.SearchTerm,"name") | `Items` | A collection (table) of tags. The app is responsible for adding or removing tags in response to the component's raising Add or Remove events (described in the following [OnChange event section](#onchange-event)). | | `Suggestions_Items` | A collection (table) of suggestions. | | `TagMaxWidth` | The maximum width of the tags when rendering. Overflow text will be truncated with ellipsis's and a hover tooltip shows the full text. | -| `AllowFreeText` | When typing a value, do not not automatically select the first suggestion so that a free text entry can be provided rather than selecting from a pre-defined list. | +| `AllowFreeText` | When typing a value, do not automatically select the first suggestion so that a free text entry can be provided rather than selecting from a pre-defined list. | | `SearchTermToShortMessage` | The message to display when the Search Term is less than the `MinimumSearchTermLength`. | `HintText` | The message to display inside the Picker when no search term is provided. | | `NoSuggestionsFoundMessage` | The message to display when the Suggestions collection contains no results. | diff --git a/power-platform/power-fx/reference/function-first-last.md b/power-platform/power-fx/reference/function-first-last.md index 8137424d2..4ff85044a 100644 --- a/power-platform/power-fx/reference/function-first-last.md +++ b/power-platform/power-fx/reference/function-first-last.md @@ -80,8 +80,8 @@ Collect( IceCream, Table( { Flavor: "Chocolate", Quantity: 100 }, | **Last( IceCream )** | Returns the last record of **IceCream**. | { Flavor: "Pistachio", Quantity: 200 } | | **Index( IceCream, 3 )** | Returns the third record of **IceCream**. | { Flavor: "Strawberry", Quantity: 300 } | | **FirstN( IceCream, 2 )** | Returns a table containing the first two records of **IceCream**. | ![Table containing the records for Chocolate and Vanilla](media/function-first-last/icecream-first2.png) | -| **LastN( IceCream, 2 )** | Returns a table containt the last two records of **IceCream**. | ![Table containing the records for Mint Chocolate and Pistachio](media/function-first-last/icecream-last2.png) | -| **Index( IceCream, 4 ).Quantity** | Returns the fourth record of the table, and extracts the Quanity column. | 60 | +| **LastN( IceCream, 2 )** | Returns a table containing the last two records of **IceCream**. | ![Table containing the records for Mint Chocolate and Pistachio](media/function-first-last/icecream-last2.png) | +| **Index( IceCream, 4 ).Quantity** | Returns the fourth record of the table, and extracts the Quantity column. | 60 | | **Index( IceCream, 10 )** | Returns an error since the record requested is beyond the bounds of the table. | _Error_ | [!INCLUDE[footer-include](../../includes/footer-banner.md)] diff --git a/power-platform/power-fx/reference/function-iferror.md b/power-platform/power-fx/reference/function-iferror.md index 95f3458c7..63e61307e 100644 --- a/power-platform/power-fx/reference/function-iferror.md +++ b/power-platform/power-fx/reference/function-iferror.md @@ -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 unexpcted 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 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. ```powerapps-dot With( {a: 1, b: Value("a")}, diff --git a/power-platform/power-fx/reference/function-send-app-notification.md b/power-platform/power-fx/reference/function-send-app-notification.md index b6d8322a3..f9f915d84 100644 --- a/power-platform/power-fx/reference/function-send-app-notification.md +++ b/power-platform/power-fx/reference/function-send-app-notification.md @@ -130,7 +130,7 @@ XSendAppNotification( -The following example formula can be used with an automated plugin when a a new Task record is created. The formula is designed to send an in-app notification to the owner of the task record. The notification card contains two actions that the owner can take: +The following example formula can be used with an automated plugin when a new Task record is created. The formula is designed to send an in-app notification to the owner of the task record. The notification card contains two actions that the owner can take: - A **side pane** action, opens the new task record in a side pane. - A **Teams chat** action, initiates a Teams chat with the owner of the account record that is assigned as the **Regarding** table record for the new task. It's important to note that this assumes an account record has been selected in the task field. diff --git a/power-platform/power-fx/reference/function-setfocus.md b/power-platform/power-fx/reference/function-setfocus.md index 8d7988fe3..ccda37c26 100644 --- a/power-platform/power-fx/reference/function-setfocus.md +++ b/power-platform/power-fx/reference/function-setfocus.md @@ -45,7 +45,7 @@ The control with focus may be visually different based on the [**FocusedBorderCo - [**Label**](/power-apps/maker/canvas-apps/controls/control-text-box) control - [**TextInput**](/power-apps/maker/canvas-apps/controls/control-text-input) control -You cannot set the focus to controls that are within a [**Gallery**](/power-apps/maker/canvas-apps/controls/control-gallery) control, [**Edit form**](/power-apps/maker/canvas-apps/controls/control-form-detail) control, or [Component](/power-apps/maker/canvas-apps/create-component). **SetFocus** can be used with a control in a scrollbale screen. +You cannot set the focus to controls that are within a [**Gallery**](/power-apps/maker/canvas-apps/controls/control-gallery) control, [**Edit form**](/power-apps/maker/canvas-apps/controls/control-form-detail) control, or [Component](/power-apps/maker/canvas-apps/create-component). **SetFocus** can be used with a control in a scrollable screen. You cannot set the focus to controls that are within a [**Container**](/power-apps/maker/canvas-apps/controls/control-container) control. @@ -140,7 +140,7 @@ To create this example: ### Focus when displaying a screen > [!NOTE] -> Although this example appears to be an **Edit form** control, unforutnatley **SetFocus** is not yet supported by that control. Instead, this example uses a scrollable screen to host the input controls. +> Although this example appears to be an **Edit form** control, unfortunately **SetFocus** is not yet supported by that control. Instead, this example uses a scrollable screen to host the input controls. Similar to exposing an input control, when displaying a data entry screen it is helpful to focus the first input control for faster data entry. diff --git a/power-platform/power-fx/reference/object-app.md b/power-platform/power-fx/reference/object-app.md index dd3f8e4ca..b54b93288 100644 --- a/power-platform/power-fx/reference/object-app.md +++ b/power-platform/power-fx/reference/object-app.md @@ -117,7 +117,7 @@ In a browser, the confirmation dialog box might appear with a generic message fr To export system-generated application logs to [Application Insights](/power-apps/maker/canvas-apps/application-insights), you need to set up the **Instrumentation Key** for your canvas app. -1. Open your app for [editing](/power-apps/maker/canvas-apps/edit-app) in Power Apps Stuido. +1. Open your app for [editing](/power-apps/maker/canvas-apps/edit-app) in Power Apps Studio. 2. Select the **App** object in the left navigation tree view. 3. Enter the **Instrumentation Key** in the properties pane. diff --git a/power-platform/power-fx/reference/object-host.md b/power-platform/power-fx/reference/object-host.md index 35dc4f94e..755fa411a 100644 --- a/power-platform/power-fx/reference/object-host.md +++ b/power-platform/power-fx/reference/object-host.md @@ -45,7 +45,7 @@ For example, a browser user agent string might be: - Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.78 > [!NOTE] -> If you're running Power Apps in a native app or using the [the wrap](/power-apps/maker/common/wrap/wrap-how-to) feature in Power Apps, the app is presented via a browser control, which supplies a user agent string. +> If you're running Power Apps in a native app or using the [wrap](/power-apps/maker/common/wrap/wrap-how-to) feature in Power Apps, the app is presented via a browser control, which supplies a user agent string. ## OSType property diff --git a/power-platform/power-fx/working-with-json.md b/power-platform/power-fx/working-with-json.md index 38e403516..491b7abb2 100644 --- a/power-platform/power-fx/working-with-json.md +++ b/power-platform/power-fx/working-with-json.md @@ -56,7 +56,7 @@ Label1.Text: untyped.Quantity InputText1.Default: untyped.ItemName ``` -And finally, when [using operators](./operators.md) such as **&** or **+**, an **Untyped object** will be coerced if there is no ambigiuty on the expected type. +And finally, when [using operators](./operators.md) such as **&** or **+**, an **Untyped object** will be coerced if there is no ambiguity on the expected type. ```powerapps-dot untyped.Quantity + 1 // result is a number