Codeunit 1915 "MigrationQB Dashboard Mgt"
QBMigration
Across versions
- BC23-28not present
- BC29present
- BC30changed
Neighbourhood 3 connected objects and pages
QBMigration · BC29-30 · source at ea08af5e · facts from BC29
Event subscriptions
- OnAllStepsCompletedSubscriber subscribes to Codeunit “Data Migration Facade” OnMigrationCompleted
Procedures
InitMigrationStatus(TotalItemNb: Integer; TotalCustomerNb: Integer; TotalVendorNb: Integer; TotalChartOfAccountNb: Integer)
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” (4 calls:
InitMigrationStatus → GetMigrationTypeTxt,OnAllStepsCompletedSubscriber → CleanupIsolatedStorage,OnAllStepsCompletedSubscriber → CleanupStagingTables, …) - Codeunit 6101 “Data Migration Status Facade” (1 call:
InitMigrationStatus → InitStatusLine)
Called by
- Codeunit 1916 “MigrationQB Mgt” (1 call:
ApplySelectedData → InitMigrationStatus)
Recent changes
- 2026-10-02 #12167 Track QuickBooks migration usage consistently (main, BC30, feature)
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 Dashboard Mgt"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.