Field monitoring in Business Central is a built-in feature that sends an email notification whenever a specific field changes. It targets administrators who need to know when sensitive data changes, without having to check logs manually.
Business Central has a change log that records activity across the system. However, reviewing it takes time. Instead, field monitoring acts immediately. If you want to know the moment something changes – not hours later – you need a more direct approach. Field monitoring provides exactly that. It watches specific fields and sends an email as soon as any of them change. Furthermore, it works with no custom development and uses tools already in standard BC.
What Is Field Monitoring in Business Central?
Field monitoring is available through the Field Monitoring Setup page in BC. It watches a list of fields you define. When any of those fields change in the system, BC sends an email to the person you have set up as the recipient. The email tells them which field changed, what the old value was, and what the new value is.
Indeed, this feature targets admins and super users. It is not intended for every user in the system. Also, Microsoft recommends using it only for sensitive fields. Monitoring too many fields at once can affect performance. So the intended use is targeted: a small number of fields that genuinely matter to the business. In short, it is a reactive alert tool rather than a full audit trail.
How to Set Up Field Monitoring
To get started, open Business Central and search for Field Monitoring Setup. The setup page has two main things to configure. First, set the recipient. However, only one user can receive the alerts. However, only one user can receive the alerts – so this should be an admin or a designated super user. Second, choose the email account BC will use to send the notifications. This is standard configuration.
Starting the Monitor
Once the setup is saved, start the monitor using the Start button at the top of the page. BC shows a performance warning – this is a reminder to keep the field list short. Then, click Yes to confirm. At this point, BC activates field monitoring and sends an activation email to the recipient. Therefore, you have a record of exactly when it was switched on.
Also, one important note: changes made before a session restart will not trigger a notification. The monitor only picks up changes after the user’s session is refreshed. So if you activate the feature and test it, log out and back in first. Otherwise, the test will not work. This is by design – BC applies the monitoring to active sessions only after they restart.
Adding Fields to the Monitored Fields Worksheet
After starting the monitor, open the Monitored Fields Worksheet. This is the list of fields BC will watch. By default, the list is empty. You add the fields you want to watch. To add a field, enter the table number or pick it from the list. BC shows all available tables. Then choose the specific field and turn on notification for that row.
For example, suppose you want to know if anyone changes the description on a payment term. You would select the Payment Terms table, pick the Description field, and enable the notify setting. From that point on, any change to a payment term description will trigger an alert email. Furthermore, you can add fields across multiple tables. However, keep the list focused. That keeps the performance impact low and the alerts meaningful. Consequently, when an alert arrives, it is genuinely worth acting on.
How Field Monitoring Alerts Work
When a monitored field changes, BC sends an email to the configured recipient. The email includes the table name, the field name, the old value, the new value, and the user who made the change. So the admin gets a clear picture of what happened and who did it. Also, they can do this without opening BC or running a report. Moreover, the email arrives within the same session, so there is very little delay.
This makes field monitoring most useful when you suspect a problem but cannot find the source. For example, if a value keeps changing and you are not sure why, the normal approach is to search the change log by hand. That takes time and can mean the issue is missed until the next day. If a payment term keeps changing, or a tax number looks different, add those fields and wait for the next alert. Consequently, the guesswork disappears. The email arrives as soon as the change happens. Also, it points directly at the field and the user responsible. Therefore, the time between an unwanted change and the admin being aware is very short.
Using the Add Sensitive Fields Option
The Monitored Fields Worksheet has an Add Fields action. When you use it, BC asks what type of fields to add. One option is Sensitive. If you choose this, BC adds a default set of fields that Microsoft considers sensitive – for example, tax registration numbers, social security numbers, and employment dates. This gives you a quick starting point without needing to know specific table numbers.
This is especially useful if you are new to field monitoring or need to set it up quickly. Also, it shows you what BC considers sensitive by default. You can then review the list and remove any fields that do not apply to your scenario. In short, it is a fast way to get a solid starting setup without manual research into every table in BC.
Wrapping Up: Field Monitoring for Sensitive Data in Business Central
Field monitoring in Business Central is a practical tool for admins who need to track changes to sensitive data. Also, it requires no development work. Indeed, it is part of the standard BC installation and takes only minutes to configure. Additionally, keep the monitored field list short to avoid performance issues, and use the Add Sensitive Fields option as a quick starting point.
If you are troubleshooting unexpected data changes, or simply want a safety net on key fields, this feature takes only a few minutes to configure. Also, once you solve the problem, you can stop the monitor. You can turn it back on at any time when needed again. So it works just as well for short-term use as for long-term use. NAV SEAL will continue covering admin tools in Business Central. Check the NAV SEAL YouTube channel and visit navseal.com for more BC guides.
For more Business Central guides and tutorials, visit NAV SEAL Blog and watch more videos on our YouTube Channel.
