You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/cards/manage-cards/delete-cards.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.collection:
13
13
14
14
# Delete a card
15
15
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.
17
17
18
18
1. Sign in to [Power Apps](https://make.powerapps.com).
19
19
1. From the [left navigation](../../maker/canvas-apps/intro-maker-portal.md#1--left-navigation-pane), select **Cards**.
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.
21
21
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.":::
- Create a [card](../tutorials/hello-world-card.md)
28
30
- 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
29
31
30
-
## Cards for Power Apps connector
32
+
## Use Cards for Power Apps connector in Power Automate
31
33
32
34
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:
33
35
@@ -36,20 +38,34 @@ The **Cards for Power Apps** connector is used to create instances of cards to s
36
38
37
39
:::image type="content" source="../media/send-a-card/cards-connector.png" alt-text="Screenshot of the cards for Power Apps connector.":::
38
40
39
-
## Send card in Teams using the Teams connector
41
+
## Send a card for Power Apps in Teams chat or channel
40
42
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.
42
44
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.
44
46
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.
46
48
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`.
48
50
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.
49
51
1. On the action, set **Card** to the `Card` dynamic content from the **Cards for Power Apps** connector action you added earlier.
50
52
51
53
:::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.":::
52
54
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
+
53
69
## Managing your flow in a solution
54
70
55
71
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).
Copy file name to clipboardExpand all lines: powerapps-docs/developer/component-framework/code-components-alm.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ When developing code components, you would follow the steps below:
38
38
39
39
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:
40
40
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.
42
42
43
43
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.
0 commit comments