pagePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Page 9985 "Upgrade Tags"

System Application · System.Upgrade

Across versions

  1. BC23-24present
  2. BC252 procedures removed
  3. BC26declaration changed
  4. BC27-30unchanged

Neighbourhood 1 connected objects and pages

Table 9999 "Upgrade Tags" (relates to)Upgrade Tags

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.

System Application · System.Upgrade · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Upgrade Tags
Extensible false
SourceTable Upgrade Tags
PageType List
UsageCategory Lists
ApplicationArea All
Permissions tabledata “Upgrade Tags” = r

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
GroupName Tag Tag Specifies the tag that is used to identify the upgrade. from the table field
Tag Timestamp Tag Timestamp Specifies the date and time when the upgrade is executed. from the table field
Company Company Specifies the company where the upgrade is executed. from the table field
Skipped Upgrade Skipped Upgrade Specifies whether the upgrade is skipped. from the table field

Relations

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: "page", object_name: "Upgrade Tags"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources