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

Codeunit 332 "No. Series Upgrade Tags"

Business Foundation · Microsoft.Foundation.NoSeries

Across versions

  1. BC23not present
  2. BC24added
  3. BC251 procedures removed
  4. BC26unchanged
  5. BC27declaration changed
  6. BC28-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 328 "No. Series Upgrade" (calls)No. Series Upgrade

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.

Business Foundation · Microsoft.Foundation.NoSeries · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Event subscriptions

  • RegisterPerCompanyTags subscribes to Codeunit “Upgrade Tag” OnGetPerCompanyUpgradeTags

Procedures

  • GetImplementationUpgradeTag(): Code[250]

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.

Deprecations

  • object: guarded (#if not CLEANSCHEMA27)

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

Evidence 1 sources