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/developer/model-driven-apps/clientapi/send-in-app-notifications.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Send in-app notifications within model-driven apps"
3
3
description: Learn how to configure notifications in model-driven apps by using a client API.
4
-
ms.date: 05/22/2023
4
+
ms.date: 06/23/2023
5
5
ms.reviewer: jdaly
6
6
ms.service: powerapps
7
7
ms.subservice: mda-developer
@@ -20,13 +20,13 @@ contributors:
20
20
21
21
Developers of model-driven apps can configure notifications to be displayed to app users as a toast or within the notification center. Your model-driven app automatically polls the system for new notifications and displays them to the user. The notification sender or your system administrator can configure how the notification is shown and how it can be dismissed. Notifications appear in the notification center until the recipient dismisses them or they expire. By default, a notification expires after 14 days but your administrator can override this setting.
22
22
23
-
Notifications are user-specific. Each notification is intended for a single user, identified as the recipient when the notification is sent. Sending a notification to a team is not supported. If a notification needs to be sent to multiple users, individual notifications must be created and sent for each recipient.
23
+
Notifications are user-specific. Each notification is intended for a single user, identified as the recipient when the notification is sent. Sending a notification to a team isn't supported. If you need to send notifications to multiple users, you must create notifications for each individual user.
24
24
25
25
This article outlines the steps for how to send in-app notifications to a specific user. To see how these notifications appear in applications, see [In-app notifications in model-driven apps](/powerapps/user/notifications).
26
26
27
27
## Enable the in-app notification feature
28
28
29
-
To use the in-app notification feature, you need to enable the **In-app notifications** setting. This setting is stored within the model-driven app.
29
+
To use the in-app notification feature, you need to enable the **In-app notifications** setting. This setting is stored within the model-driven app.
30
30
31
31
1. Sign in to [Power Apps](https://make.powerapps.com).
32
32
@@ -36,7 +36,7 @@ To use the in-app notification feature, you need to enable the **In-app notifica
36
36
37
37
1. Open **Settings** and switch to **Features**.
38
38
39
-
1. Enable "In-app notifications".
39
+
1. Enable **In-app notifications**.
40
40
41
41
> [!div class="mx-imgBorder"]
42
42
> 
@@ -162,7 +162,7 @@ Notifications sent using the `SendAppNotification` message are stored in the [No
162
162
|Display Name|Schema Name|Description|
163
163
|---|---|---|
164
164
|**Title**|`Title`|The title of the notification.|
165
-
|**Owner**|`OwnerId`|The user who receives the notification. This must be a user and not a team because notifications are only read for a user. |
165
+
|**Owner**|`OwnerId`|The *user* who receives the notification. While this column can be set to either a user or team, you must only set this to a user. The notification can't be set to a team.|
166
166
|**Body**|`Body`|Details about the notification.|
167
167
|IconType|`IconType`|The list of predefined icons. The default value is `Info`. For more information, go to [Changing the notification icon](#changing-the-notification-icon) later in this article.|
168
168
|**Toast Type**|`ToastType`|The list of notification behaviors. The default value is `Timed`. For more information, go to [Changing the notification behavior](#changing-the-notification-behavior) later in this article.|
0 commit comments