---
id: post/waldo-be/317951
type: post
title: Obsoleted and “no longer invoked” events in v26 Business Central
summary: Business Central v26 removed invocation of 82 obsoleted events from the legacy invoice posting system while keeping them in the codebase for backward compatibility. Code subscribing to these non-invoked events will compile and publish but fail silently at runtime, creating a hidden risk for developers upgrading from earlier versions.
tier: community
language: en
tags:
  - events
  - obsolescence
  - upgrade
  - invoice posting
  - extensibility
  - backward compatibility
  - code migration
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:00:31.053Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 36e37737dab9e08ff1832cb5ce3779d5425d3a57fb97b845a5f9c4f63fef55cb
evidence:
  - kind: blog
    url: https://waldo.be/2025/06/30/obsoleted-and-no-longer-invoked-events-in-v26-business-central/
    title: Obsoleted and “no longer invoked” events in v26 Business Central
    date: "2025-06-30"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://waldo.be/2025/06/30/obsoleted-and-no-longer-invoked-events-in-v26-business-central/
    title: Obsoleted and “no longer invoked” events in v26 Business Central
    date: "2025-06-30"
    commit: null
    t: null
    quote: I found 82 of such non-invoked events!
  - kind: blog
    url: https://waldo.be/2025/06/30/obsoleted-and-no-longer-invoked-events-in-v26-business-central/
    title: Obsoleted and “no longer invoked” events in v26 Business Central
    date: "2025-06-30"
    commit: null
    t: null
    quote: Be mindful! Use DevOps and fail your build pipelines when you are using obsoleted stuff. Manage that! Continuously!
links:
  learn: []
  objects:
    - object/table/49
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "317951"
source_id: waldo-be
source_name: waldo's blog
url: https://waldo.be/2025/06/30/obsoleted-and-no-longer-invoked-events-in-v26-business-central/
published_at: "2025-06-30T07:00:00.000Z"
author: waldo (Eric Wauters)
full_text: true
words: 1254
quotes:
  - text: I found 82 of such non-invoked events!
    why_it_matters: Quantifies the scope of the problem, showing this affects numerous events across the invoice posting system
  - text: Be mindful! Use DevOps and fail your build pipelines when you are using obsoleted stuff. Manage that! Continuously!
    why_it_matters: Provides the recommended preventive approach - catching obsolete event usage early in development rather than discovering failures in production
code_objects_mentioned:
  - table Invoice Post. Buffer
  - interface Invoice Posting Interface
systems:
  - development
  - integration
versions_mentioned:
  - v19
  - v25
  - v26
preview:
  embeddable: true
  frame_url: https://waldo.be/2025/06/30/obsoleted-and-no-longer-invoked-events-in-v26-business-central/embed/
  image: https://waldo.be/wp-content/uploads/2025/06/image-1.png
  image_alt: null
  image_w: 1131
  image_h: 600
  site_name: null
  favicon: https://waldo.be/wp-content/uploads/2019/06/waldo_logo_final_symbol_icon_Revised-150x150.ico
  probed_at: "2026-10-07T11:51:03.180Z"
---

# Obsoleted and “no longer invoked” events in v26 Business Central

[Read the post](https://waldo.be/2025/06/30/obsoleted-and-no-longer-invoked-events-in-v26-business-central/) · waldo's blog (waldo (Eric Wauters), MVP) · 2025-06-30 · 1254 words · tier community · reviewed (checked by Opus)

> Business Central v26 removed invocation of 82 obsoleted events from the legacy invoice posting system while keeping them in the codebase for backward compatibility. Code subscribing to these non-invoked events will compile and publish but fail silently at runtime, creating a hidden risk for developers upgrading from earlier versions.

## Key points

- The Extensible Invoice Posting Engine replaced the Invoice Post. Buffer system starting in v19, with v26 marking the end of the legacy events
- 82 events remain in code but are no longer invoked in v26, allowing apps to compile across versions but potentially failing at runtime
- Microsoft removed the validation check that previously prevented publishing apps subscribed to obsoleted events
- Developers should implement their own validation checks during upgrades to catch dependencies on non-invoked events before production issues occur
- Supporting multiple versions of an app across different BC releases without multiple AppSource versions creates this compatibility challenge

## Quotes

- "I found 82 of such non-invoked events!" (Quantifies the scope of the problem, showing this affects numerous events across the invoice posting system)
- "Be mindful! Use DevOps and fail your build pipelines when you are using obsoleted stuff. Manage that! Continuously!" (Provides the recommended preventive approach - catching obsolete event usage early in development rather than discovering failures in production)

## 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.

- [table 49 "Invoice Post. Buffer"](../../objects/table/49.md)
- interface "Invoice Posting Interface"

Not found in BC28-30: interface "Invoice Posting Interface".

## Context

- Features: Extensible Invoice Posting Engine, Event Subscribers, Feature Management, Upgrade Validation, Centralized Event Publishers
- Versions: v19, v25, v26

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