BC Observatoryunofficial, made by waldo
enumextensionAdministration & Setupofficial - Microsoftderived - from the source, no model text

Enum extension 2611 "Feature To Update - BaseApp"

Base Application · System.Environment.Configuration

Open in Claude2611.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25declaration changed
  4. BC26declaration changed
  5. BC27declaration changed
  6. BC28declaration changed
  7. BC29declaration changed
  8. BC30unchanged

Neighbourhood 1 connected objects and pages

Enum 2611 "Feature To Update" (relates to)Feature To Update

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

Extends Feature To Update.

Values

Ordinal Name Caption Notes
7049 SalesPrices
8200 FinancialReportDefaults obsolete Pending 28.0

Relations

Deprecations

  • value FinancialReportDefaults: Pending 28.0 (#if not CLEAN28), “Financial Report defaults feature will be always enabled in version 29.0”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "enumextension", object_name: "Feature To Update - BaseApp"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources