codeunitAdministration & Setupofficial - Microsoftderived - from the source, no model text

Codeunit 4018 "GP Customer Migrator"

HybridGP · Microsoft.DataMigration.GP

Across versions

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

Neighbourhood 6 connected objects and pages

Table 4093 "GP Customer" (relates to)GP CustomerCodeunit 6112 "Customer Data Migration Facade" (calls, 39 links)Customer Data Migration FacadeCodeunit 4037 "Helper Functions" (calls, 19 links)Helper FunctionsCodeunit 1796 "Data Migration Error Logging" (calls, 4 links)Data Migration Error LoggingCodeunit 1797 "Data Migration Facade Helper" (calls)Data Migration Facade HelperPage 456 "No. Series" (calls)No. Series

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.

HybridGP · Microsoft.DataMigration.GP · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo GP Customer
Permissions tabledata “Standard Sales Code” = RIM, tabledata “Standard Sales Line” = RIM, tabledata “Standard Customer Sales Code” = RIM

Event subscriptions

  • OnMigrateCustomer subscribes to Codeunit “Customer Data Migration Facade” OnMigrateCustomer
  • OnMigrateCustomerPostingGroups subscribes to Codeunit “Customer Data Migration Facade” OnMigrateCustomerPostingGroups
  • OnMigrateCustomerTransactions subscribes to Codeunit “Customer Data Migration Facade” OnMigrateCustomerTransactions

Procedures

  • PopulateStagingTable(JArray: JsonArray)
  • PopulateRMTRxStagingTable(JArray: JsonArray)

Plus 13 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.

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

Evidence 1 sources