Skip to content

Commit 1f2d03e

Browse files
authored
Live publish
2 parents a2f49db + 4be56cf commit 1f2d03e

File tree

8 files changed

+24
-15
lines changed

8 files changed

+24
-15
lines changed

powerapps-docs/cards/card-requirements.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,11 @@ ms.collection:
1616

1717
[!INCLUDE[cards_preview_notice](includes/preview-include.md)]
1818

19-
This article contains information on requirements for cards to show up and work as expected.
19+
This article contains information about requirements for cards to show up and work as expected.
2020

2121
## Environment requirements
2222

23-
Cards are available in environments with Dataverse.
23+
Cards are available in environments with Microsoft Dataverse.
2424

2525
The table below shows the environment regions cards are supported in.
2626

powerapps-docs/cards/make-a-card/designer-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Legend:
4242

4343
### Main menu
4444

45-
Use the main menu to switch between the tools available in the card designer:
45+
Use the main menu to switch between the tools available in the card designer.
4646

4747
- **Tree View**: View card elements as a hierarchy and view the relationships between elements
4848
- **Insert**: Add controls
@@ -75,16 +75,16 @@ Each element also has advanced properties, such as:
7575

7676
- **Repeat for every**: Trigger whether or when an element should be repeated
7777
- **Show when**: Trigger when to show the element
78-
- **Requires**: Make the element dependent on certain features, with a corresponding minimum version
78+
- **Requires**: Make the element dependent on certain features with a corresponding minimum version
7979

8080
You can also enter Power Fx expressions in some properties, creating low-code solutions that make your card more powerful.
8181

8282
### Formula bar and Power Fx editor
8383

84-
Use the formula bar to enter a Power Fx expression as a property of the selected control; for example, to calculate a value when a button is clicked. The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
84+
Use the formula bar to enter a Power Fx expression as a property of the selected control (for example, to calculate a value when a button is clicked). The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
8585

8686
> [!NOTE]
87-
> Some expressions that are supported in Power Apps aren't available for cards. For more information, see [Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
87+
> Some expressions that are supported in Power Apps aren't available for cards. For more information, go to [Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
8888
8989
### Play button
9090

powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The [Power Fx documentation](/power-platform/power-fx/overview) is the main sour
2929

3030
## Known limitations of using Power Fx in cards
3131

32-
The following table lists the Power Fx formulas that don't work in cards, or have limitations. All other functions are fully supported.
32+
The following table lists the Power Fx formulas that don't work in cards or have limitations. All other functions are fully supported.
3333

3434
| Power Fx formula | Supported in cards |
3535
|---------|:---:|

powerapps-docs/cards/make-a-card/variables/variables.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ As an example, you've created a card that counts how many times the user presses
4141

4242
You can't change the name or type of a variable. If you need to change them, create a new variable.
4343

44-
You can also customize sender options and, under **Additional variable information**, the **Title** and **Description** of the variable. This information may be helpful for testing and debugging and using your variable with Power Automate flows and Power Virtual Agents bots.
44+
You can also customize sender options and, under **Additional variable information**, the **Title** and **Description** of the variable. This information may be helpful for testing, debugging, and using your variable with Power Automate flows and Power Virtual Agents bots.
4545

4646
:::image type="content" source="../../media/variables/new-variable.png" alt-text="Screenshot of the New variable window in the card designer.":::
4747

powerapps-docs/cards/manage-cards/manage-cards.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This section shows you how to manage cards using security roles.
2626

2727
Cards are stored as rows in Dataverse within the **Card** table. Administrators can use [security roles to control who can create, read, and update cards](/power-platform/admin/wp-security-cds#tablerecord-ownership).
2828

29-
For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user will not be able to create cards.
29+
For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user won't be able to create cards.
3030

3131
Note that a user will still be able to receive and use cards sent in Teams, regardless of the security role assigned to the user, as those cards are accessed by the Cards for Power Apps service.
3232

@@ -57,4 +57,4 @@ This section shows you how to delete a card.
5757

5858
### Delete a card as the administrator
5959

60-
If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We are working on enabling this capability.
60+
If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We're working on enabling this capability.

powerapps-docs/developer/data-platform/includes/cc-legacy-update-messages.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,11 @@
88
|<xref:Microsoft.Crm.Sdk.Messages.SetBusinessEquipmentRequest>|[Equipment](/dynamics365/customer-engagement/developer/entities/equipment).[BusinessUnitId](/dynamics365/customer-engagement/developer/entities/equipment#BKMK_BusinessUnitId)|
99
|<xref:Microsoft.Crm.Sdk.Messages.SetBusinessSystemUserRequest>|[SystemUser](../reference/entities/systemuser.md).[BusinessUnitId](../reference/entities/systemuser.md#BKMK_BusinessUnitId)|
1010

11-
*&lt;entity>* refers to any entity that provides this attribute.
11+
*&lt;entity>* refers to any entity that provides this attribute.
12+
13+
> [!IMPORTANT]
14+
> When you update the `StateCode` column, it is important to always set the desired `StatusCode`.
15+
>
16+
>`StateCode` and `StatusCode` have dependent values. There can be multiple valid `StatusCode` values for a given `StateCode` value, but each `StateCode` column has a single [DefaultStatus](xref:Microsoft.Xrm.Sdk.Metadata.StateOptionMetadata.DefaultStatus) value configured. When you update `StateCode` without specifying a `StatusCode`, the default status value will be set by the system.
17+
>
18+
> Also, when auditing is enabled on the table and the `StatusCode` column, the changed value for the `StatusCode` column will not be captured in the audit data unless it is specified in the update operation.

powerapps-docs/developer/data-platform/webapi/update-delete-entities-using-web-api.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Update and delete table rows using the Web API (Microsoft Dataverse)| Microsoft Docs"
33
description: "Read how to perform update and delete operations on tables using the Web API"
4-
ms.date: 08/01/2022
4+
ms.date: 12/14/2022
55
author: divka78
66
ms.author: dikamath
77
ms.reviewer: jdaly
@@ -30,6 +30,8 @@ The `If-Match: *` header ensures you don't create a new record by accidentally p
3030

3131
> [!IMPORTANT]
3232
> When updating an entity, only include the properties you are changing in the request body. Simply updating the properties of an entity that you previously retrieved, and including that JSON in your request, will update each property even though the value is the same. This can cause system events that can trigger business logic that expects that the values have changed. This can cause properties to appear to have been updated in auditing data when in fact they haven't actually changed.
33+
>
34+
> When you update the `statecode` property, it is important to always set the desired `statuscode`. `statecode` and `statuscode` have dependent values. There can be multiple valid `statuscode` values for a given `statecode` value, but each `statecode` column has a single [DefaultStatus](xref:Microsoft.Xrm.Sdk.Metadata.StateOptionMetadata.DefaultStatus) value configured. When you update `statecode` without specifying a `statuscode`, the default status value will be set by the system. Also, when auditing is enabled on the table and the `statuscode` column, the changed value for the `statuscode` column will not be captured in the audit data unless it is specified in the update operation.
3335
3436
> [!NOTE]
3537
> The definition for attributes includes a `RequiredLevel` property. When this is set to `SystemRequired`, you cannot set these attributes to a null value. More information: [Attribute requirement level](../entity-attribute-metadata.md#column-requirement-level)

powerapps-docs/teams/add-app-notifications.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ contributors:
1616

1717
# Add notifications to make your apps collaborative
1818

19-
Apps in Microsoft Teams are designed to enable collaboration between people in your organization. When you have an app that has a hand-off of information, such as group A doing something that group B then needs to process, if everything happens in the app, users may miss important updates and processes might stall.
19+
Apps in Microsoft Teams are designed to enable collaboration between people in your organization. When you have an app that has a hand-off of information, such as group A doing something that group B then needs to process, if everything happens in the app, users may miss important updates, and processes might stall.
2020

21-
Using notifications for critical events in your apps in Teams enhances collaboration by proactively letting users know that there's something that needs their attention, or needs to be done.
21+
Using notifications for critical events in your apps in Teams enhances collaboration by proactively letting users know that something needs their attention or needs to be done.
2222

2323
Teams and Power Platform give you many options in the ways that you can notify people.
2424

@@ -33,7 +33,7 @@ Watch this video to learn how to add notifications to make your apps collaborati
3333
3434
## Choose the right notification type
3535

36-
How should you decide what type of notification to use? Many people default to email notifications, but many people also complain that they receive too many emails. Email is an acceptable type of notification, but it should be used sparingly. Especially for urgent notifications, as frequently emails aren't seen immediately.
36+
How should you decide what type of notification to use? Many people default to email notifications, but many people also complain that they receive too many emails. Email is an acceptable type of notification, but it should be used sparingly. Especially for urgent notifications, as frequent emails are only seen after a period of time.
3737

3838
Here are some questions to ask when defining the appropriate type of notification:
3939

0 commit comments

Comments
 (0)