Skip to content

Commit 31392a9

Browse files
committed
Merge branch 'main' into u/vilesyk/3034102_theming_doc
2 parents df6c678 + 3fb68ff commit 31392a9

File tree

71 files changed

+971
-488
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

71 files changed

+971
-488
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.collection:
1313

1414
# Delete a card
1515

16-
To delete a card, you need to be the app owner. An administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin can't delete card.
16+
To delete a card, you need to be the app owner. An administrator, such as Global admin, Microsoft Entra Global admin, or Dynamics 365 admin can't delete card.
1717

1818
1. Sign in to [Power Apps](https://make.powerapps.com).
1919
1. From the [left navigation](../../maker/canvas-apps/intro-maker-portal.md#1--left-navigation-pane), select **Cards**.
Loading
Loading

powerapps-docs/cards/send-a-card/send-card-with-flow.md

Lines changed: 26 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Send a card automatically with a flow (preview)
2+
title: Send a card automatically with a flow
33
description: Learn how to send a card automatically using a Power Automate flow.
44
keywords: "Card Designer, Power Apps, cards, send a card, Power Automate, flow"
55
author: anuitz
@@ -15,19 +15,21 @@ contributors:
1515
- anuitz
1616
---
1717

18-
# Send a card automatically with a flow (preview)
18+
# Send a card automatically with a flow
1919

20-
[!INCLUDE[cards_preview_notice](../includes/preview-include.md)]
20+
Use Power Automate to send cards for Power Apps from a flow. By setting up a flow that is triggered by an event, you can automate the process of sending cards in Teams. For instance, you can create a flow that requests the assigned individual to approve or reject an expense when a new record is added to Dataverse. Alternatively, you can create a flow that sends a daily status update in Teams every morning.
2121

22-
Use Power Automate to send cards. By setting up a flow that is triggered by an event, you can automate the process of sending cards. For instance, you can create a flow that requests the assigned individual to approve or reject an expense when a new record is added to Dataverse. Alternatively, you can create a flow that sends a daily status update every morning.
22+
You can use **Send from a flow** option in **Send** menu on the card's **Play** page to launch a Power Automate flow template for sending cards in Teams. You can modify and save this template as a new flow to post your card in Teams chat or channel or send it to a specific Teams user.
23+
24+
:::image type="content" source="../media/send-a-card/Send_from_flow.png" alt-text="Select Send from flow option to lauch a Power Automate template.":::
2325

2426
## Prerequisites
2527

2628
- [Power Automate](https://make.powerautomate.com) account
2729
- Create a [card](../tutorials/hello-world-card.md)
2830
- The [Power Apps Teams app](send-card-in-teams.md#add-power-apps-to-teams) installed in the chat, group chat, or channel that the card will be sent to
2931

30-
## Cards for Power Apps connector
32+
## Use Cards for Power Apps connector in Power Automate
3133

3234
The **Cards for Power Apps** connector is used to create instances of cards to send using a flow. The connector has no triggers and two actions:
3335

@@ -36,20 +38,34 @@ The **Cards for Power Apps** connector is used to create instances of cards to s
3638

3739
:::image type="content" source="../media/send-a-card/cards-connector.png" alt-text="Screenshot of the cards for Power Apps connector.":::
3840

39-
## Send card in Teams using the Teams connector
41+
## Send a card for Power Apps in Teams chat or channel
4042

41-
Sending a card in Teams requires a card instance. To get a card instance, use the **Cards for Power Apps** connector actions. The **Create card instance** action has `Card` dynamic content that can be used with the **Teams** connector **Post card in a chat or channel** action.
43+
Sending a card in Teams froma flow requires a card instance. To crearte a card instance, use the **Cards for Power Apps** connector actions. The **Create card instance** action has `Card` dynamic content that can be used with the **Teams** connector **Post card in a chat or channel** action.
4244

43-
1. Create or modify an existing flow
45+
1. Create or modify an existing flow, or use **Send** > **Send from a flow** on cards for Power Apps **Play** page to start with a template.
4446
1. Make sure the flow has a trigger. In the screenshot below, the trigger is when a new account record is created.
45-
1. Create or get the card instance you want to send using the **Cards for Power Apps** connector. In the screenshot, we created a card instance of the `Account Card` and setting the `Body` input variable to the `Account Name` of the newly created account record.
47+
1. Create a card instance you want to send using the **Cards for Power Apps** connector's **Create card instance** action. In the screenshot, we created a card instance of the `Account Card` and setting the `Body` input variable to the `Account Name` of the newly created account record.
4648
1. Add an action to **Post card in a chat or channel** using the **Teams** connector.
47-
1. On the action, set **Post as** to `Power Apps (Preview)`.
49+
1. On the action, set **Post as** to `Power Apps`.
4850
1. On the action, set **Post in**, **Team** & **Channel**, or **Group chat** to the conversation you want to send the card in. In the example screenshot, this is to the `Cards for Power Apps (Customer Channel)` Teams in the `General` channel.
4951
1. On the action, set **Card** to the `Card` dynamic content from the **Cards for Power Apps** connector action you added earlier.
5052

5153
:::image type="content" source="../media/send-a-card/card-in-flow-example.png" alt-text="Screenshot a flow that creates a card instance when an account record is created and sends it in Teams.":::
5254

55+
## Send a card for Power Apps to a Teams user
56+
You can send a card to a specific Teams user. In a Power Automate flow, use the **Create card instance** action in **Cards for Power Apps** connector actions to create a card instance as `Card` dynamic content. You can use the resulting `Card` dynamic content with the **Teams** connector **Post card in a chat or channel** action to send a card to a specific Teams user.
57+
58+
1. Create or modify an existing flow, or use **Send** > **Send from a flow** on cards for Power Apps **Play** page to start with a template.
59+
1. Make sure the flow has a trigger. In the screenshot below, the trigger is when a new account record is created.
60+
1. Create a card instance you want to send using the **Cards for Power Apps** connector's **Create card instance** action. In the screenshot, we created a card instance of the `Account Card` and setting the `Body` input variable to the `Account Name` of the newly created account record.
61+
1. Add an action to **Post card in a chat or channel** using the **Teams** connector.
62+
1. On the action, set **Post as** to `Power Apps`.
63+
1. On the action, set **Post in** to **Chat with Power Apps**.
64+
1. On the action, enter the **Teams user** you want to post the card to.
65+
1. On the action, set **Card** to the `Card` dynamic content from the **Cards for Power Apps** connector action you added earlier.
66+
67+
:::image type="content" source="../media/send-a-card/Send_card_to_a_Teams_user.png" alt-text="Screenshot a flow that creates a card instance when an account record is created and sends it to a specific Teams user.":::
68+
5369
## Managing your flow in a solution
5470

5571
For more details on managing your flow that uses the Card for Power Apps Connector, see [Manage cards in solutions](../manage-cards/manage-cards.md).

powerapps-docs/developer/component-framework/code-components-alm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ When developing code components, you would follow the steps below:
3838

3939
When your code component is ready for testing inside a model-driven app, canvas app, or portal, there are two ways to deploy a code component to Dataverse:
4040

41-
1. [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push): This deploys a single code component at a time to a temporary **PowerAppsTools** solution.
41+
1. [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push): This deploys a single code component at a time to a solution specified by the `--solution-unique-name` parameter, or a temporary **PowerAppsTools** solution when no solution is specified.
4242

4343
2. Using [pac solution init](/power-platform/developer/cli/reference/solution#pac-solution-init) and `msbuild` to build a `cdsproj` solution project that has references to one or more code components. Each code component is added to the `cdsproj` using [pac solution add-reference](/power-platform/developer/cli/reference/solution#pac-solution-add-reference). A solution project can contain references to multiple code components, whereas code component projects may only contain a single code component.
4444

powerapps-docs/developer/data-platform/TOC.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,11 @@
4848
href: ./search/legacy.md
4949
- name: Bulk Operation messages
5050
href: bulk-operations.md
51+
items:
52+
- name: Use UpsertMultiple (preview)
53+
href: upsertmultiple.md
54+
- name: Use DeleteMultiple (preview)
55+
href: deletemultiple.md
5156
- name: Create your own messages
5257
href: custom-actions.md
5358
items:

0 commit comments

Comments
 (0)