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

Codeunit 46866 "BC14 Telemetry"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

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

Neighbourhood 14 connected objects and pages

Codeunit 46875 "BC14 Migration Runner" (calls, 13 links)BC14 Migration RunnerCodeunit 46862 "BC14 Migration Orchestrator" (calls, 8 links)BC14 Migration OrchestratorCodeunit 46853 "BC14 Company Upgrade Task" (calls, 3 links)BC14 Company Upgrade TaskCodeunit 46880 "BC14 Posted Sales Inv Migr." (calls, 3 links)BC14 Posted Sales Inv Migr.Codeunit 46860 "BC14 Migration Failure Handler" (calls, 2 links)BC14 Migration Failure HandlerCodeunit 46864 "BC14 Historical Task Worker" (calls, 2 links)BC14 Historical Task WorkerCodeunit 46881 "BC14 Old G/L Entry Migr." (calls, 2 links)BC14 Old G/L Entry Migr.Codeunit 46940 "BC14 Old Cust. Ledger Migr." (calls, 2 links)BC14 Old Cust. Ledger Migr.Codeunit 46944 "BC14 Old Vend. Ledger Migr." (calls, 2 links)BC14 Old Vend. Ledger Migr.Codeunit 46947 "BC14 Old Item Ledger Migr." (calls, 2 links)BC14 Old Item Ledger Migr.Codeunit 46851 "BC14 Migration Setup" (calls)BC14 Migration SetupCodeunit 46855 "BC14 Migration Loop" (calls)BC14 Migration LoopCodeunit 46896 "BC14 Journal Post Action" (calls)BC14 Journal Post ActionCodeunit 46949 "BC14 Item Journal Post Action" (calls)BC14 Item Journal Post Action

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

  • GetCategory(): Text
  • LogSubscriberContribution(PublisherName: Text; CountBefore: Integer; CountAfter: Integer): Emits telemetry capturing how a Populate / extension publisher event changed a list, so we can see in App Insights whether any partner / PTE subscribed and by how much they extended the list. Safe to call with delta = 0 (useful baseline data).

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

Evidence 1 sources