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

Codeunit 8705 "Feature Uptake Status Impl."

System Application · System.Telemetry

Open in Claude8705.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 8703 "Feature Uptake" (relates to)Feature UptakeCodeunit 8704 "Feature Telemetry Impl." (calls)Feature Telemetry 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
TableNo Feature Uptake
Permissions tabledata “Feature Uptake” = rimd

Procedures

  • UpdateFeatureUptakeStatus(FeatureName: Text; FeatureUptakeStatus: Enum "Feature Uptake Status"; IsPerUser: Boolean; PerformWriteTransactionsInASeparateSession: Boolean; Publisher: Text): Boolean

Plus 6 local procedures.

Triggers

OnRun

Relations

Called by

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.

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: "codeunit", object_name: "Feature Uptake Status Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources