codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 1919 "MigrationQB Data Reader"

QBMigration

Across versions

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

Neighbourhood 5 connected objects and pages

Table 1917 "MigrationQB Config" (relates to)MigrationQB ConfigCodeunit 1916 "MigrationQB Mgt" (calls, 5 links)MigrationQB MgtCodeunit 1917 "MigrationQB Helper Functions" (calls, 5 links)MigrationQB Helper FunctionsCodeunit 419 "File Management" (calls, 5 links)File ManagementCodeunit 9170 "Conf./Personalization Mgt." (calls)Conf./Personalization Mgt.

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.

QBMigration · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo MigrationQB Config

Events published

Event subscriptions

  • OnZipFileMissingSubscriber subscribes to Codeunit “MigrationQB Data Reader” OnZipFileMissing
  • OnExtractFolderMissingSubscriber subscribes to Codeunit “MigrationQB Data Reader” OnExtractFolderMissing
  • OnEmptyZipFileSubscriber subscribes to Codeunit “MigrationQB Data Reader” OnEmptyZipFile
  • OnFileMissinggSubscriber subscribes to Codeunit “MigrationQB Data Reader” OnFileMissing

Procedures

  • GetNumberOfAccounts(): Integer
  • GetNumberOfItems(): Integer
  • GetNumberOfCustomers(): Integer
  • GetNumberOfVendors(): Integer

Plus 3 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

  • Codeunit 1916 “MigrationQB Mgt” (5 calls: CreateDataMigrationEntites → GetNumberOfAccounts, CreateDataMigrationEntites → GetNumberOfCustomers, CreateDataMigrationEntites → GetNumberOfItems, …)

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

Evidence 1 sources