codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 5150 "Create FA Jnl. Setup"

ContosoCoffeeDemoDataset · Microsoft.DemoData.FixedAsset

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 4 connected objects and pages

Codeunit 5149 "Create FA Jnl. Template" (calls, 2 links)Create FA Jnl. TemplateCodeunit 5170 "Create FA Ins Jnl. Template" (calls, 2 links)Create FA Ins Jnl. TemplateCodeunit 4774 "FA Module" (calls)FA ModuleCodeunit 4776 "Contoso Fixed Asset" (calls)Contoso Fixed Asset

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.

ContosoCoffeeDemoDataset · Microsoft.DemoData.FixedAsset · BC29-30 · source at ea08af5e · facts from BC29

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.

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: "Create FA Jnl. Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources