Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Indicates whether the value of the computed notification field is considered when grouping notifications for digest delivery.
Syntax
<NotificationClasses>
<NotificationClass>
<Schema>
<ComputedFields>
<ComputedField>
...
<DigestGrouping>
Element Characteristics
| Characteristic | Description |
|---|---|
Data type |
Boolean. |
Default value |
false. |
Occurrence |
Optional once per ComputedField element. |
Updates |
Can be added, deleted, and modified when updating the application. |
Element Relationships
| Relationship | Elements |
|---|---|
Parent element |
|
Child elements |
None. |
Remarks
If you want a notification field used to determine if notifications should be grouped when using digest delivery, set DigestGrouping to true. For example, if a calendar application notifies users of future events, you can set DigestGrouping to true on a computed DaysToEvent field so that only notifications for events on the same day are grouped into a single notification.
If you are using digest delivery but you do not set DigestGrouping to true on any fields, Microsoft SQL Server Notification Services will group messages within a notification batch that have the same SubscriberId, DeviceName, and SubscriberLocale values.
If you add, delete, or update a DigestGrouping element, updating the application deletes and re-creates the notification class to which it corresponds. This includes dropping and re-creating the SQL Server tables used by this notification class.
Example
The following example shows a DigestGrouping element set to true to indicate that the associated field should be used when determining whether to group notifications together for digest delivery.
<DigestGrouping>true</DigestGrouping>
See Also
Other Resources
Defining the Notification Schema
Configuring Content Formatters
Updating Instances and Applications