Small and medium business | Business Central, N...

Analysis View not updating automatically for one G/L Entry

(2) Share

Report

Posted on by LB-23040845-0

We have an Analysis View in Business Central with Update on Posting enabled and Date Compression = Month.

For August, the Analysis View balance differs from the G/L balance by exactly one G/L Entry. The missing entry:

is posted in August
is on an account included in the Analysis View filter
was posted by the same user as other entries that updated correctly
is included correctly after running Update manually

Other August entries, including entries before and after this one, appear to have updated correctly.

Has anyone seen a case where Update on Posting skips a single transaction/entry, while a manual update later includes it? Could Date Compression, background update processing, permissions, locking, or something else cause this?

Categories:

Dynamics 365 Business Central

All responses (6)

Answers (0)

Sort by

Suggested answer

AndrewThomas81 3,013 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

I haven't experienced this, if you can replicate in a sandbox environment it could be reported to Microsoft via your partner for investigation further

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn
Suggested answer

Grigorios Mavrogeorgis 3,638 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, the Update on Posting is the reason. The view keeps a Last Entry No. and only reads forward from it. Two people posting at nearly the same moment, one commits before the other, the pointer jumps past your entry and there it stays. A manual update reads everything from the start again, which is why the entry suddenly appears.
Not date compression, that only groups amounts, it never drops an entry.
What I do is switch Update on Posting off and schedule Update Analysis Views in the job queue, nightly or every hour. Posting gets quicker as well, updating that view on every single post costs more than people think.
Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis
Suggested answer

YUN ZHU 103,656 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

I haven't run into this before—could it be that it wasn't enabled during posting?
If manual updates work fine, could you check if the same issue occurs again next time?
And, Please note that enabling this setting may impact system performance.
Suggested answer

OussamaSabbouh 20,124 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello,
With Update on Posting enabled, Microsoft states that the Analysis View should automatically update when an associated transaction is posted, so silently skipping one G/L Entry is not expected standard behavior. Date Compression = Month only controls the level at which Analysis View entries are aggregated; it should not exclude an otherwise qualifying G/L Entry. The fact that Update manually immediately brings the missing entry in is important because it confirms that the account/date/dimension filters and the G/L Entry itself are valid, so I would focus on what happened during the incremental update at posting time. Permissions are unlikely if the same user posted surrounding transactions successfully, and Microsoft doesn't document Update on Posting as a background/job-queue process that can simply catch up later. I would check whether that particular entry was subsequently affected by a dimension correction, whether any extension/custom posting logic is involved, and whether multiple posting sessions were running concurrently around that time. If it can be reproduced in a clean sandbox with Microsoft-only extensions, I would treat it as a potential product issue and raise a Microsoft support case with the Analysis View setup, missing G/L Entry No., posting timestamp, BC version/build, and reproduction steps. As a practical safeguard, you can also schedule the standard Update Analysis Views batch job periodically, but that should be a safety net rather than a requirement when Update on Posting is enabled.
Regards,
Oussama Sabbouh
LB-23040845-0 25 on at

Like (1)

Report
Copy link

Link copied!

Hi @OussamaSabbouh,
Thank you for the reply. There were no postings made around the time of the missing transaction, and no dimension corrections were made either.
If you have any other suggestions, they would be very helpful. :)
In the meantime, I will set up a job queue to update all entries.
Lisa
AndrewThomas81 3,013 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Let us know how you get on @LB-23040845-0

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn