codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 7238 "Master Data Mgt. Upgrade"

MasterDataManagement · Microsoft.Integration.MDM

Across versions

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

Neighbourhood 5 connected objects and pages

Codeunit 9999 "Upgrade Tag" (calls, 4 links)Upgrade TagCodeunit 7230 "Master Data Mgt. Setup Default" (calls, 3 links)Master Data Mgt. Setup DefaultCodeunit 7243 "Master Data Mgt. Install" (calls)Master Data Mgt. InstallCodeunit 9750 "Web Service Management" (calls)Web Service ManagementPage 7233 "Master Data Synch. Tables" (calls)Master Data Synch. Tables

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.

MasterDataManagement · Microsoft.Integration.MDM · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Subtype Upgrade
Permissions tabledata “Integration Field Mapping” = rimd, tabledata “Integration Table Mapping” = rimd, tabledata “Tenant Web Service” = rimd

Event subscriptions

  • RegisterPerCompanyTags subscribes to Codeunit “Upgrade Tag” OnGetPerCompanyUpgradeTags

Procedures

  • RegisterCrossEnvSourceWebService() (internal)
  • CrossEnvSourceWebServiceName(): Text[240] (internal)
  • UpgradeJobQueueEntryFrequencies() (internal)
  • UpgradeSynchTableCaptions() (internal)

Plus 2 local procedures.

Triggers

OnUpgradePerCompany, OnUpgradePerDatabase

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

Recent changes

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: "Master Data Mgt. Upgrade"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources