---
id: change/bcquality/152
type: change
title: "#152 knowledge(events): ChangeCompany leaves triggers and trigger-event subscribers running in the calling company"
summary: A knowledge article documents that ChangeCompany does not move trigger execution context to the target company; triggers and trigger-event subscribers still run in the calling company. StartSession is recommended for cross-company operations that require proper trigger handling.
tier: official
language: en
tags:
  - feature
  - main
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:05:03.351Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: b7617fb48a01c9f41116e37edaede3daed424236
evidence:
  - kind: code
    url: https://github.com/microsoft/BCQuality/pull/152
    title: "microsoft/BCQuality#152: knowledge(events): ChangeCompany leaves triggers and trigger-event subscribers running in the calling company"
    date: "2026-09-15"
    commit: b7617fb48a01c9f41116e37edaede3daed424236
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 152
repo: microsoft/BCQuality
source_id: bcquality-prs
url: https://github.com/microsoft/BCQuality/pull/152
kind: pr
base_branch: main
major: null
merged_at: "2026-09-15T10:34:29Z"
author: waldo1001
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: feature
behavior_change: false
breaking: false
files:
  count: 4
  additions: 219
  deletions: 1
  al: 4
apps: []
objects_touched: []
objects_unjoined:
  - path: microsoft/knowledge/events/changecompany-runs-triggers-in-the-calling-company.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/events/changecompany-runs-triggers-in-the-calling-company.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/events/changecompany-runs-triggers-in-the-calling-company.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/skills/review/al-events-review.md
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues: []
work_items: []
systems:
  - development
quote: null
joined_against:
  major: null
  commit: null
---

# #152 knowledge(events): ChangeCompany leaves triggers and trigger-event subscribers running in the calling company

> A knowledge article documents that ChangeCompany does not move trigger execution context to the target company; triggers and trigger-event subscribers still run in the calling company. StartSession is recommended for cross-company operations that require proper trigger handling.

[Pull request](https://github.com/microsoft/BCQuality/pull/152) · merged into `main` on 2026-09-15 by waldo1001 · 4 files (+219 -1), 4 AL · feature · tier official · reviewed (checked by Opus)

## What changed

- ChangeCompany redirects only the data access of a record variable
- Triggers, field validation and database trigger-event subscribers keep running in the calling company
- Passing RunTrigger false skips trigger code, but subscribers still receive the trigger events
- The recommended approach is StartSession with the company parameter, so the code runs in the target company
- Direct cross-company writes should be limited to trigger-free hand-off tables owned by the extension

## AL objects touched

- `microsoft/knowledge/events/changecompany-runs-triggers-in-the-calling-company.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/events/changecompany-runs-triggers-in-the-calling-company.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/events/changecompany-runs-triggers-in-the-calling-company.md`: added, not in the BC? snapshot yet
- `microsoft/skills/review/al-events-review.md`: modified, not in the BC? snapshot

## Context

- Systems: development

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).