--- id: post/gerardorenteria-blog/15051 type: post title: "馃攷 Change Log Blame View: View change history in a different way" summary: 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. tier: community language: en tags: - change log - audit trail - data history - extension - page extension - matrix view - record tracking system: administration review: state: reviewed by: opus at: "2026-10-08T01:54:08.942Z" flags: [] generated: at: "2026-10-08T01:26:53.141Z" pipeline: 0.2.0 prompts: extract-post: 1 input_hash: 8958c31bcb05a0cf6f0d39269198d9cc247587ad8b12aabd5faa42aac9d49c2f evidence: - kind: blog url: https://gerardorenteria.blog/2026/07/17/%f0%9f%94%8e-change-log-blame-view-view-change-history-in-a-different-way/ title: "馃攷 Change Log Blame View: View change history in a different way" date: "2026-07-17" commit: null t: null quote: null - kind: blog url: https://gerardorenteria.blog/2026/07/17/%f0%9f%94%8e-change-log-blame-view-view-change-history-in-a-different-way/ title: "馃攷 Change Log Blame View: View change history in a different way" date: "2026-07-17" commit: null t: null quote: This way, instead of reviewing isolated entries, you can read the history almost like a visual timeline. - kind: blog url: https://gerardorenteria.blog/2026/07/17/%f0%9f%94%8e-change-log-blame-view-view-change-history-in-a-different-way/ title: "馃攷 Change Log Blame View: View change history in a different way" date: "2026-07-17" commit: null t: null quote: This is not a closed solution. The idea can be reused on any page where you can identify the current record. links: learn: [] objects: [] features: [] topics: [] localizations: [] videos: [] posts: [] guidelines: [] post_id: "15051" source_id: gerardorenteria-blog source_name: Gerardo Renteria url: https://gerardorenteria.blog/2026/07/17/%f0%9f%94%8e-change-log-blame-view-view-change-history-in-a-different-way/ published_at: "2026-07-17T20:12:38.000Z" author: Gerardo Renteria full_text: false words: 1237 quotes: - text: This way, instead of reviewing isolated entries, you can read the history almost like a visual timeline. why_it_matters: Explains the core benefit of the matrix layout for understanding record evolution visually - text: This is not a closed solution. The idea can be reused on any page where you can identify the current record. why_it_matters: Shows the extension's reusability across different pages and record types through a standardized pattern code_objects_mentioned: - 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 systems: - administration - development versions_mentioned: [] preview: embeddable: true frame_url: https://gerardorenteria.blog/2026/07/17/%f0%9f%94%8e-change-log-blame-view-view-change-history-in-a-different-way/embed/ image: https://gerardorenteria.blog/wp-content/uploads/2026/07/designer-1.png image_alt: null image_w: 1024 image_h: 1024 site_name: Gerardo Renter铆a Blog favicon: https://gerardorenteria.blog/wp-content/uploads/2020/11/cropped-wolficon.jpg?w=32 probed_at: "2026-10-07T11:50:21.979Z" --- # 馃攷 Change Log Blame View: View change history in a different way [Read the post](https://gerardorenteria.blog/2026/07/17/%f0%9f%94%8e-change-log-blame-view-view-change-history-in-a-different-way/) 路 Gerardo Renteria (Gerardo Renteria) 路 2026-07-17 路 1237 words 路 tier community 路 reviewed (checked by Opus) > 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. ## 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.