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

Codeunit 1911 "MigrationQB Account Migrator"

QBMigration

Across versions

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

Neighbourhood 5 connected objects and pages

Table 1911 "MigrationQB Account" (relates to)MigrationQB AccountCodeunit 6110 "GL Acc. Data Migration Facade" (calls, 21 links)GL Acc. Data Migration FacadeCodeunit 1917 "MigrationQB Helper Functions" (calls, 9 links)MigrationQB Helper FunctionsCodeunit 1914 "MigrationQB Wizard Integration" (calls, 2 links)MigrationQB Wizard IntegrationPage 1830 "MS - QBO Data Migration" (calls, 2 links)MS - QBO Data Migration

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 Account

Event subscriptions

  • OnMigrateGlAccount subscribes to Codeunit “GL Acc. Data Migration Facade” OnMigrateGlAccount
  • OnCreateOpeningBalanceTrx subscribes to Codeunit “GL Acc. Data Migration Facade” OnCreateOpeningBalanceTrx
  • OnMigratePostingGroups subscribes to Codeunit “GL Acc. Data Migration Facade” OnMigratePostingGroups

Procedures

  • MigrateAccountDetails(MigrationQBAccount: Record "MigrationQB Account"; GLAccDataMigrationFacade: Codeunit "GL Acc. Data Migration Facade")
  • MigratePostingGroups(var Sender: Codeunit "GL Acc. Data Migration Facade"; RecordIdToMigrate: RecordId)
  • GetAll(IsOnline: Boolean)
  • PopulateStagingTable(JArray: JsonArray)
  • DeleteAll()
  • PreDataIsValid(): Boolean

Plus 2 local procedures.

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

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

Evidence 1 sources