codeunitAssemblyofficial - Microsoftderived - from the source, no model text

Codeunit 901 "Assembly-Post (Yes/No)"

Base Application · Microsoft.Assembly.Posting

Across versions

  1. BC23present
  2. BC241 procedures added
  3. BC25-30unchanged

Neighbourhood 5 connected objects and pages

Table 900 "Assembly Header" (relates to)Assembly HeaderCodeunit 900 "Assembly-Post" (calls, 4 links)Assembly-PostCodeunit 19 "Gen. Jnl.-Post Preview" (calls, 2 links)Gen. Jnl.-Post PreviewPage 902 "Assembly Orders" (calls, 2 links)Assembly OrdersPage 900 "Assembly Order" (calls)Assembly Order

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

Properties

Property Value
TableNo Assembly Header

Event subscriptions

  • OnRunPreview subscribes to Codeunit “Gen. Jnl.-Post Preview” OnRunPreview

Procedures

  • Preview(var AssemblyHeaderToPreview: Record "Assembly Header")
  • MessageIfPostingPreviewMultipleDocuments(var AssemblyHeaderToPreview: Record "Assembly Header"; DocumentNo: Code[20]) + BC24

Plus 1 local procedures.

Triggers

OnRun

Relations

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.

Called by

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: "Assembly-Post (Yes/No)"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources