BeyondERP.Newsletter
Menu

Job page · System administration

Notification clean up

A periodic job that deletes old notification records from the EventInbox and EventInboxData tables.

Business process
Administer system features
Menu item
action:EventAlertCleanup
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic job that deletes old notification records from the EventInbox and EventInboxData tables.
What you do hereUse this task to periodically delete notification records, for example as a recurring batch job. Run it only after the business has confirmed that the data is no longer required.
ExampleFor example, BEAT schedules Notification clean up as a recurring batch job at night after the business confirms that notifications from both company and organization-wide alert rules older than the review period are no longer needed.
Notification clean up page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processAdminister system features
Menu pathSystem administration › Periodic tasks › Notification clean up
Set up firstAlert rules Microsoft Learn
Used next byBatch jobs (check the run) Microsoft Learn
Related pagesBatch job history clean-up. Microsoft Learn Batch job clean-up Microsoft Learn
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itAfter the business has confirmed that old notification records are no longer needed.
How oftenAs a recurring batch job; choose the interval by how many notifications your alert rules produce.
Batch settingsSchedule it as a recurring batch job outside business hours.
What the output showsOld records removed from EventInbox and EventInboxData. If recent notifications disappear too, the job's selection was wider than intended.

Source: Microsoft Learn

Setup steps on this page

Schedule the notification clean-up

Keep the notification tables small by deleting notifications the business no longer needs.

Steps from Microsoft

  1. Go to System administration > Periodic tasks > Notification clean up.
  2. Agree with the business which notifications can go. Microsoft advises running a cleanup routine only after the business confirms the data is no longer needed, and testing it in a test environment first.
  3. Set the job up as a recurring batch job, so the EventInbox and EventInboxData tables don't keep growing.
  4. If your company doesn't use alert rules at all, turn off the alert processing batch job too, instead of only cleaning up after it.
  5. After the first run, confirm that users no longer see the old notifications and that recent ones are still there.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Notifications based on organization-w… (label cut on screen)Includes notifications from alert rules set up as Organization-wide, which apply across legal entities. No in BEAT.Microsoft Learn No
Notifications based on company ruleIncludes notifications from alert rules that apply in one company. Yes in BEAT.Microsoft Learn Yes
Records to includeFilter on the notification records the run deletes.Checked in Dynamics 365
Run in the backgroundSet the job up as a recurring batch job so the EventInbox and EventInboxData tables don't keep growing.Microsoft Learn

Common errors and fixes

MessageWhat to do
The tables keep growing although nobody uses alertsLearn recommends turning off the alert batch job when alert functionality isn't used, instead of only cleaning up after it. Microsoft Learn

Test checklist

  1. Old notifications no longer appear for users.
  2. Notifications created after the cutoff are still there.
  3. The recurring batch job ends without errors.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Schedule the notification clean-upA recurring night batch job, set up only after the business confirms which notifications can go; if alerts aren't used at all, turn off the alert batch jobs insteadLearn says cleanup routines run only after the business confirms the data isn't needed, tested in a test environment first, and recommends turning off the alert batch job when alerts aren't used.How are notification records kept under control?Running the clean-up without agreeing on what may go; users lose notifications they still act on, and deleted notifications can't be restored.Test: Old notifications are removed, new ones stay

Feature management and licence

Licence or add-inOn this system the page opens for Information technology manager. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyShared: EventInbox and EventInboxData have no company key. The two dialog options choose notifications from company rules, organization-wide rules or both. Microsoft data model
Can it be undoneNo: Deleted notifications can't be restored. Run it only after the business confirms they are no longer needed. Microsoft Learn
If you change it laterDeletes notification records from the EventInbox and EventInboxData tables, so users no longer see those notifications. Microsoft Learn
Technical architect

6Technical

Menu itemaction:EventAlertCleanup Checked in Dynamics 365
Roles to set it up and use itTo use itInformation technology manager SysServerITManagerGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:EventAlertCleanup
Data migrationLoad order: Notification clean up has no data entity in Data management, so it can't be loaded from a file or a configuration template. It is a periodic job; set it up again as a recurring batch job in each environment.Checked in Dynamics 365
Everyone

8Sources