codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 9003 "Team Member Action Manager"

Base Application · Microsoft.RoleCenters

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 9027 "Plan Ids" (calls, 2 links)Plan IdsCodeunit 9016 "Azure AD Plan" (calls)Azure AD Plan

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.RoleCenters · BC23-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnBeforeSalesHeaderInsert subscribes to Table “Sales Header” OnBeforeInsertEvent
  • OnBeforeSalesHeaderDelete subscribes to Table “Sales Header” OnBeforeDeleteEvent
  • OnBeforeSalesDocPost subscribes to Codeunit “Sales-Post” OnBeforePostSalesDoc
  • OnBeforePurchaseDocPost subscribes to Codeunit “Purch.-Post” OnBeforePostPurchaseDoc
  • OnBeforePurchaseHeaderInsert subscribes to Table “Purchase Header” OnBeforeInsertEvent
  • OnBeforePurchaseHeaderDelete subscribes to Table “Purchase Header” OnBeforeDeleteEvent

Procedures

3 local procedures, no public ones.

Triggers

OnRun

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Team Member Action Manager"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources