BC Observatoryunofficial, made by waldo
tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 8703 "Feature Uptake"

System Application · System.Telemetry

Open in Claude8703.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 8705 "Feature Uptake Status Impl." (pages and codeunits on it)Feature Uptake Status Impl.

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.Telemetry · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

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 Feature Name Text[250] — NotBlank; DataClassification SystemMetadata
2 User Security ID Guid — DataClassification EndUserPseudonymousIdentifiers
3 Publisher Text[250] — DataClassification SystemMetadata
4 Feature Uptake Status Enum “Feature Uptake Status” — enum Enum 8703 “Feature Uptake Status”; DataClassification SystemMetadata

Keys

  • PrimaryKey: Feature Name, User Security ID, Publisher (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: "Feature Uptake"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources