Working with the Log
The Business Portals - Log helps administrators review messages about portal activity and investigate problems. Entries can contain errors, warnings, or information about completed processes.
Opening the Log
- Open the Business Portals Administrator Role Center in Business Central.
- In Activities, find Business Portals Logs.
- Choose a cue under Business Portals Logs, or the Logs action tile alongside it:
| Cue or Action | Description |
|---|---|
| Logs action tile | Opens all read and unread entries in the current company without showing a count. |
| Unread Logs cue | Shows the number of all unread entries, including errors, warnings, and information, and opens only those entries in the current company. |
| Error Logs cue | Shows the number of unread errors and opens only those entries in the current company. Its red indicator highlights errors that need attention. |
You can also use the Business Central search to open Business Portals - Log. The newest entries appear first. Refresh the page to see the latest counts and messages.
Info
Access to diagnostic logs requires administrator permissions. If you cannot open the page, contact your Business Central administrator.
Using the Log Cues and Action
The log cues and the Logs action tile appear together in Activities in the Administrator Role Center. The cues give you a quick overview of messages that have not yet been acknowledged. All counts and lists apply to the company you are currently working in.
Unread Logs: Review All Unacknowledged Messages
The Unread Logs cue shows the number of unread entries of every type: errors, warnings, and information. Use this cue when reviewing all new messages, including status information that may not require a correction.
- Select the Unread Logs cue or its number.
- The Business Portals - Log page opens with Read filtered to No.
- Check Type and Source to understand what happened and which process reported it.
- Select a message and choose Details to read the full information where available.
- After reviewing the message, use Read Status to mark it as read or leave it unread for further investigation.
Error Logs: Focus on Unread Errors
The Error Logs cue shows only entries that are both unread and of type Error. Its red indicator draws attention to this category. Use this cue to focus on reported failures before reviewing warnings and information.
- Select Error Logs or its number.
- The log page opens with Read filtered to No and Type filtered to Error.
- Review Source, User, Portal User, and the descriptions to identify the affected process and user. Not every process supplies a portal username.
- Choose Details for the complete message. For entries that track repeated events, check Occurrence Count and Last Occurred to see how often and how recently the problem was reported.
- Investigate the problem or share the details with your support contact, then acknowledge the message when appropriate.
Info
Error Logs is a subset of Unread Logs. For example, if there are 5 unread entries, including 2 errors, Unread Logs shows 5 and Error Logs shows 2. These are not seven separate entries. A count of 0 means there are no entries matching that cue; it does not confirm that every portal process is working correctly.
Logs: Open the Complete History
Logs is an action tile alongside the log cues, without a separate heading or a count. Choose it to open all entries in the current company, including those already marked as read. Use it to look up an older message, check whether another administrator has acknowledged an error, or return to the complete list after using an unread-only view.
To open the history, return to Activities in the Administrator Role Center and select the Logs tile. It has an icon instead of a number and does not have a separate group heading. Depending on the available screen width, Business Central may place the tile beside or below the numbered cues.
The complete list includes the same entry information as the cue views. Opening it does not change any entry's read status. You can also find this page by searching for Business Portals - Log in Business Central.
Understanding Changes to the Counts
- Opening a cue or Details does not mark messages as read.
- When any administrator marks an entry as read, it no longer contributes to either unread cue. Marking an unread error as read therefore reduces both counts.
- Marking a read entry as unread adds it back to Unread Logs and, if its type is Error, to Error Logs.
- Cue counts represent entries, not the sum of their occurrence counts. One unread error with 20 occurrences contributes 1 to each cue.
- For entries that track repeated occurrences, the same entry may become unread again under the 30-minute rule.
Refresh the Role Center to see updated cue counts after reviewing messages or when another administrator has changed their read status. Refresh an open log page to see updated entry details.
Understanding the Entries
| Field | Description |
|---|---|
| Read | Shows whether an administrator has acknowledged the entry. This status is shared by all administrators. |
| Date and Time | Shows when the entry was first created. |
| Occurrence Count | Shows how many matching occurrences have been reported for this entry, where occurrence tracking is used. |
| Last Occurred | Shows when the matching event was most recently reported, where occurrence tracking is used. |
| Type | Identifies the message as an error, warning, or information. |
| Source | Identifies the part of Business Portals that reported the message, such as Power BI. |
| User | Shows the Business Central user or service account that recorded the entry. |
| Portal User | Shows the portal user associated with the message, where available. This can differ from User. |
| Description 1–5 | Shows the message across several columns. Choose Details to read the full message where available. |
The log is shared by different Business Portals processes. Read status and the read actions apply to all entries. Some processes track repeated occurrences in one entry, while others record separate messages. Entries without occurrence tracking and older entries can show a count of 0 and an empty Last Occurred field.
Investigating a Message
- Select the entry you want to investigate.
- Choose Details to read the full message. Opening details does not mark the entry as read.
- Check the Source, User, Portal User, and description to identify the affected area and user. The available details depend on the process that reported the message.
- Investigate the problem or pass the details to your administrator or support contact.
- When you have reviewed the message, choose Read Status, then Mark as Read.
Important
Marking an entry as read acknowledges the message. It does not correct the problem or confirm that the affected process is working again.
For a report that cannot be displayed in the portal, see Power BI Report Cannot Be Displayed.
Handling Repeated Messages
When a process tracks repeated occurrences together, Business Portals updates the matching entry instead of creating a new row each time:
- Occurrence Count increases.
- Last Occurred changes to the latest reported occurrence.
- Date and Time and the original message remain unchanged.
Example: Repeated Power BI Errors
Power BI is one example of a process that uses occurrence tracking. Refreshing a dashboard can cause the same report error to be reported again. Errors are grouped when the portal user, affected dataset and table, and error are the same. Changing request references or timestamps alone does not create a new entry. A different error, a different portal user, or a different dataset or table can create a separate unread entry immediately.
The occurrence count measures reported failures, not dashboard visits. It increases only when another matching error is reported to Business Central. Refresh the log page to see updates.
The 30-Minute Rule
For entries that track repeated occurrences, the following acknowledgement rule applies. While an entry is unread, matching occurrences continue to update it without creating more entries.
When an administrator marks the entry as read, a 30-minute period starts from that acknowledgement. During this period, matching occurrences still increase the occurrence count and update Last Occurred, but the entry stays read. This gives administrators time to investigate without the same message immediately returning to the unread list.
If the same event is reported again 30 minutes or more after acknowledgement, the existing entry becomes unread again. The count continues increasing; a new entry is not created.
| Example time | What happens | Result |
|---|---|---|
| 09:00 | An error is reported for the first time by a process that tracks repeated occurrences. | An unread entry is created with a count of 1. |
| 09:05 | An administrator chooses Mark as Read. | The entry becomes read. The 30-minute period starts. |
| 09:10 | The same error is reported again. | The count becomes 2 and Last Occurred is updated. The entry stays read. |
| 09:35 | No further error has been reported. | The entry stays read. There is no automatic change just because 30 minutes have passed. |
| 09:36 | The same error is reported again. | The count becomes 3 and the entry becomes unread again. |
Info
The 30-minute rule applies only to matching occurrences of an entry that has been marked as read. It never delays a different error or message. Processes that record each event separately do not combine entries under this rule. Marking an entry as read again starts a new 30-minute period.
Managing Read Status
Choose Read Status to access the following actions:
| Action | Description |
|---|---|
| Mark as Read | Acknowledges the selected entries for all administrators. For entries that track repeated occurrences, this starts the 30-minute period described above. |
| Mark as Unread | Returns the selected entries to the unread list for all administrators. |
| Mark All as Read | Asks for confirmation, then acknowledges all entries in the current company, including entries hidden by the current filters. |
Opening Unread Logs, selecting a row, or viewing Details does not acknowledge entries automatically.
Clearing Read Entries
- Review the entries you want to acknowledge and mark them as read.
- Choose Clear History.
- Read the confirmation and confirm only if those read entries are no longer needed.
Clear History deletes all read entries in the current company, including entries outside your current selection or filters. Unread entries are kept. The action is available only to users with permission to delete log entries.
Warning
Deleted entries are no longer available for investigation. Keep any details needed by support before clearing the history. If the same event is reported again after its entry has been deleted, it is recorded as a new entry.