Table 9994 "API Data Upgrade"
Base Application · Microsoft.API.Upgrade
Across versions
- BC23-28present
- BC293 fields changed
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.API.Upgrade · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| 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 | Upgrade Tag Δ BC29 | Text[250] | Specifies the name of the entity. | |
| 2 | Description Δ BC29 | Text[250] | Specifies the API endpoints of the entity. | |
| 3 | Status Δ BC29 | Option | Specifies the status of the API data upgrade. | OptionCaption: ,Scheduled,In Progress,Completed |
Keys
- Key1: Upgrade Tag (clustered)
Procedures
Load(): Boolean
Pages and codeunits on this table
- Page 9994 “API Data Upgrade List” (source 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.
- Codeunit 9994 “API Data Upgrade” (2 calls:
Load → GetAPIDataUpgradeEntities,Load → GetAPIUpgradeTags)
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: "API Data Upgrade"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.