codeunitAdministration & Setupofficial - Microsoftderived - from the source, no model text

Codeunit 46864 "BC14 Historical Task Worker"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

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

Neighbourhood 4 connected objects and pages

Codeunit 46875 "BC14 Migration Runner" (calls, 4 links)BC14 Migration RunnerCodeunit 46858 "BC14 Migration Status Mgr." (calls, 2 links)BC14 Migration Status Mgr.Codeunit 46866 "BC14 Telemetry" (calls, 2 links)BC14 TelemetryCodeunit 46862 "BC14 Migration Orchestrator" (calls)BC14 Migration Orchestrator

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.

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Procedures

1 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.

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: "BC14 Historical Task Worker"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources