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

Codeunit 1913 "MigrationQB Vendor Migrator"

QBMigration

Across versions

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

Neighbourhood 4 connected objects and pages

Table 1914 "MigrationQB Vendor" (relates to)MigrationQB VendorCodeunit 6111 "Vendor Data Migration Facade" (calls, 19 links)Vendor Data Migration FacadeCodeunit 1917 "MigrationQB Helper Functions" (calls, 16 links)MigrationQB Helper FunctionsCodeunit 1918 "MigrationQB Data Loader" (calls)MigrationQB Data Loader

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 Vendor

Event subscriptions

  • OnMigrateVendor subscribes to Codeunit “Vendor Data Migration Facade” OnMigrateVendor
  • OnMigrateVendorPostingGroups subscribes to Codeunit “Vendor Data Migration Facade” OnMigrateVendorPostingGroups
  • OnMigrateVendorTransactions subscribes to Codeunit “Vendor Data Migration Facade” OnMigrateVendorTransactions

Procedures

  • MigrateVendorPostingGroups(var Sender: Codeunit "Vendor Data Migration Facade"; RecordIdToMigrate: RecordId; ChartOfAccountsMigrated: Boolean)
  • MigrateVendorDetails(MigrationQBVendor: Record "MigrationQB Vendor"; VendorDataMigrationFacade: Codeunit "Vendor Data Migration Facade")
  • GetAll(IsOnline: Boolean)
  • PopulateStagingTable(JArray: JsonArray)
  • DeleteAll()

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

Evidence 1 sources