Codeunit 1918 "MigrationQB Data Loader"

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

Properties

Procedures

• FillStagingTables(var DataMigrationEntity: Record "Data Migration Entity")
• CleanupFiles()

Triggers

OnRun

Relations

• runs on Table 1801 “Data Migration Entity”

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.

• Codeunit 1917 “MigrationQB Helper Functions” (2 calls: FillStagingTables → GetMigrationTypeTxt, FillStagingTables → IsOnlineData)
• Codeunit 419 “File Management” (2 calls: CleanupFiles → DeleteServerFile, CleanupFiles → ServerRemoveDirectory)
• Codeunit 1912 “MigrationQB Customer Migrator” (1 call: FillStagingTables → GetAll)
• Codeunit 1913 “MigrationQB Vendor Migrator” (1 call: FillStagingTables → GetAll)
• Codeunit 1920 “MigrationQB Item Migrator” (1 call: FillStagingTables → GetAll)

Called by

• Codeunit 1916 “MigrationQB Mgt” (3 calls: ApplySelectedData → (object), ApplySelectedData → CleanupFiles, ImportQBData → CleanupFiles)

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