BC Observatoryunofficial, made by waldo
tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 5447 "API Extension Upload"

Base Application · Microsoft.API

Open in Claude5447.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Page 20006 "APIV1 - Aut. Extension Upload" (pages and codeunits on it)APIV1 - Aut. Extension UploadPage 30006 "APIV2 - Aut. Extension Upload" (pages and codeunits on it)APIV2 - Aut. Extension Upload

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.

Base Application · Microsoft.API · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
DataClassification CustomerContent

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 Id Integer — not editable; DataClassification SystemMetadata
2 Schedule Enum “Extension Deploy To” — enum Enum 2504 “Extension Deploy To”; DataClassification SystemMetadata
3 Schema Sync Mode Enum “Extension Sync Mode” — enum Enum 2505 “Extension Sync Mode”; DataClassification SystemMetadata
20 Content Blob — DataClassification SystemMetadata

Keys

  • Key1: Id (clustered)

Pages and codeunits on this 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: "API Extension Upload"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources