BC Observatoryunofficial, made by waldo
codeunitAssemblyofficial - Microsoftderived - from the source, no model text

Codeunit 904 "Whse.-Assembly Release"

Base Application · Microsoft.Assembly.Document

Open in Claude904.mdSource on GitHub

Across versions

  1. BC23-25present
  2. BC263 procedures added, 3 procedures removed
  3. BC27-30unchanged

Neighbourhood 3 connected objects and pages

Codeunit 903 "Release Assembly Document" (calls, 2 links)Release Assembly DocumentCodeunit 900 "Assembly-Post" (calls)Assembly-PostTable 901 "Assembly Line" (calls)Assembly Line

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.Assembly.Document · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnBeforeCreateWhseRqst(AssemblyHeader: Record "Assembly Header"; AssemblyLine: Record "Assembly Line"; var Location: Record Location) (integration)
  • OnDeleteLineOnBeforeDeleteWhseRqst(var AssemblyLine: Record "Assembly Line"; var KeepWhseRequest: Boolean) (integration)
  • OnBeforeWhseRequestInsert(var WarehouseRequest: Record "Warehouse Request"; AssemblyLine: Record "Assembly Line"; AssemblyHeader: Record "Assembly Header") (integration)

Procedures

  • Release(AssemblyHeader: Record "Assembly Header")
  • Reopen(AssemblyHeader: Record "Assembly Header")
  • DeleteLine(AssemblyLine: Record "Assembly Line")

Plus 6 local procedures.

Triggers

OnRun

Called by

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: "Whse.-Assembly Release"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources