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

Table 4009 "Migration Table Mapping"

HybridBaseDeployment · Microsoft.DataMigration

Across versions

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

Neighbourhood 5 connected objects and pages

Page 40022 "Cloud Mig Table Mapping API" (pages and codeunits on it)Cloud Mig Table Mapping APIPage 4009 "Migration Table Mapping" (pages and codeunits on it)Migration Table MappingCodeunit 40022 "Telemetry Subscriber" (event subscribers, 4 links)Telemetry SubscriberCodeunit 4100 "Temp Blob" (calls, 2 links)Temp BlobCodeunit 2504 "Extension Management" (calls)Extension Management

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.

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

Properties

Property Value
Extensible false
DataClassification SystemMetadata

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 App ID Guid — TableRelation “Published Application”.ID
2 Table ID Integer Specifies the ID of the target table. via Page 4009 “Migration Table Mapping” NotBlank
3 Table Name Text[30] Specifies the name of the table for the mapping. via Page 4009 “Migration Table Mapping” NotBlank
4 Source Table Name Text[128] Specifies the name of the source table for the mapping. This is used in the case that the name of the table differs between the source and destination databases. via Page 4009 “Migration Table Mapping” NotBlank
5 Data Per Company Boolean Specifies if the table data is per company via Page 4009 “Migration Table Mapping”
6 Locked Boolean —
8 Extension Name Text[250] — FlowField: lookup(“Published Application”.Name where(ID = field(“App ID”)))
9 Extension Package ID Guid — FlowField: lookup(“Published Application”.“Package ID” where(ID = field(“App ID”)))
10 Target Table Type Enum “Migration Table Type” Specifies the type of the target table. via Page 4009 “Migration Table Mapping” enum Enum 4009 “Migration Table Type”

Keys

  • PK: App ID, Table ID (clustered)

Trigger event subscribers

Procedures

  • ValidateSourceTableName(var MigrationTableMapping: Record "Migration Table Mapping"; SourceTableName: Text) (internal)
  • InvalidExtensionPublishers(): Text
  • UpdateExtensionName(var ExtensionName: Text)
  • LookupApp(var PublishedApplication: Record "Published Application"): Boolean (internal)
  • GetSourceTableAppID(var MigrationTableMapping: Record "Migration Table Mapping"): Text (internal)
  • GetSourceTableAppID(SourceTableName: Text): Text (internal)
  • GetSourceTableName(var MigrationTableMapping: Record "Migration Table Mapping"): Text (internal)
  • ParseSourceTableName(SourcetableName: Text): Text (internal)
  • GetExtensionSeparatorCharacter(): Text (internal)
  • FilterOutBlacklistedPublishers(var PublishedApplication: Record "Published Application") (internal)
  • SetSourceTableName(SourceTableAppID: Text) (internal)
  • ImportMigrationTableMappings()
  • ImportFromJson(TableMappingsJsonObject: JsonObject)
  • DownloadMigrationTableMappings()
  • ExportMigrationTableMappings(): JsonObject
  • ExportFromJson(var MigrationTableMapping: Record "Migration Table Mapping"): JsonObject
  • TrimSourceTableName(SourceTableName: Text): Text (internal)
  • UpdateObjectsFilter(var PublishedApplication: Record "Published Application"; var AppFilter: Text; var ExtensionsFilter: Text) (internal)

Plus 2 local procedures.

Pages and codeunits on this table

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: "table", object_name: "Migration Table Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources