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

Codeunit 328 "No. Series Upgrade"

Business Foundation · Microsoft.Foundation.NoSeries

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-26unchanged
  4. BC271 procedures added
  5. BC28-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 9999 "Upgrade Tag" (calls, 2 links)Upgrade TagCodeunit 332 "No. Series Upgrade Tags" (calls)No. Series Upgrade Tags

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
Subtype Upgrade

Procedures

  • SetupNoSeriesImplementation() + BC27 (internal)

Triggers

OnUpgradePerCompany

Calls

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

Evidence 1 sources