Codeunit 2507 "Dataverse Table Builder"
System Application · System.Apps.ExtensionGeneration
Across versions
- BC23-27not present
- BC28added
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
System Application · System.Apps.ExtensionGeneration · BC28-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Public |
Procedures
StartGeneration(OverwriteExisting: Boolean): Boolean: Starts the generation of Dataverse tables and table extensions.UpdateExistingTable(TableId: Integer; FieldsToAdd: List of [Text]; DataverseSchema: Text): Boolean: Updates an existing Dataverse table by adding new fields based on the provided Dataverse schema.CommitGeneration(): Boolean: Commits the generated Dataverse tables and table extensions to the system.ClearGeneration(): Clears any ongoing or incomplete generation of Dataverse tables and table extensions.
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.
- Codeunit 2508 “Dataverse Table Builder Impl.” (4 calls:
ClearGeneration → ClearGeneration,CommitGeneration → CommitGeneration,StartGeneration → StartGeneration, …)
Called by
- Codeunit 5391 “Man. Int. Field Mapping” (3 calls:
TryCreateRuntimeFields → CommitGeneration,TryCreateRuntimeFields → StartGeneration,TryCreateRuntimeFields → UpdateExistingTable)
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: "Dataverse Table Builder"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.