Table 9999 "Upgrade Tags"
System Application · System.Upgrade
Across versions
- BC23-24present
- BC254 fields changed
- BC26-30unchanged
Neighbourhood 1 connected objects and pages
System Application · System.Upgrade · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Upgrade Tags |
| Access | Internal |
| 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 | Tag Δ BC25 | Code[250] | Specifies the tag that is used to identify the upgrade. | |
| 2 | Tag Timestamp Δ BC25 | DateTime | Specifies the date and time when the upgrade is executed. | |
| 3 | Company Δ BC25 | Code[30] | Specifies the company where the upgrade is executed. | |
| 4 | Skipped Upgrade Δ BC25 | Boolean | Specifies whether the upgrade is skipped. |
Keys
- Key1: Tag, Company (clustered)
Pages and codeunits on this table
- Page 9985 “Upgrade Tags” (source table)
Ask your agent
Procedure bodies are not stored here (D10). 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: "Upgrade Tags"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.