BC Observatoryunofficial, made by waldo
community postAdministration & Setupcommunity - not Microsoftreviewed - checked by Opus

🔎 Change Log Blame View: View change history in a different way

The Change Log Blame View extension reorganizes standard Change Log Entry data for one record into a matrix, with fields as rows and change events as columns, showing change type, date, user and resulting value. It can be added to any page through a page extension action that passes the table and primary key to the CL Blame page.

Open in Claude15051.md

post Gerardo Rentería Blog

Gerardo Renteria · 2026-07-17 · 1,237 words · about 6 min

"This way, instead of reviewing isolated entries, you can read the history almost like a visual timeline."
Show the post hereRead on Gerardo Rentería Blog

Key points

  • Matrix layout displays change history with fields as rows and events as columns for easier timeline visualization
  • Filters and groups change log entries by table and primary key, excluding audit fields to reduce clutter
  • Reusable pattern via page extensions allows adding a ‘Change Log (Blame View)’ action to any record page
  • Helps quickly identify which field changed, when it changed, and which user made the change

Quotes

  • “This way, instead of reviewing isolated entries, you can read the history almost like a visual timeline.” (Explains the core benefit of the matrix layout for understanding record evolution visually)
  • “This is not a closed solution. The idea can be reused on any page where you can identify the current record.” (Shows the extension’s reusability across different pages and record types through a standardized pattern)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

  • page “CL Blame”
  • page “CLBlameMatrix”
  • codeunit “CLBlameMgmt”
  • table “CLBlameRowBuffer”
  • table “CLBlameCellBuffer”
  • page “CL Blame Customer Card Ext”
  • page “CL Blame Vendor Card Ext”
  • page “CL Blame Item Card Ext”
  • permissionset “CLBlamePermSet”

Not found in BC28-30: page “CL Blame”, page “CLBlameMatrix”, codeunit “CLBlameMgmt”, table “CLBlameRowBuffer”, table “CLBlameCellBuffer”, page “CL Blame Customer Card Ext”, page “CL Blame Vendor Card Ext”, page “CL Blame Item Card Ext”, permissionset “CLBlamePermSet”.

Context

  • Features: Change Log matrix view, Field change tracking, Event navigation, Page extension pattern, Visual timeline display, User change attribution, Audit field filtering

Source: Gerardo Renteria, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.