Codeunit 328 "No. Series Upgrade"
Business Foundation · Microsoft.Foundation.NoSeries
Across versions
- BC23not present
- BC24added
- BC25-26unchanged
- BC271 procedures added
- BC28-30unchanged
Neighbourhood 2 connected objects and pages
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.
- Codeunit 9999 “Upgrade Tag” (2 calls:
SetupNoSeriesImplementation → HasUpgradeTag,SetupNoSeriesImplementation → SetUpgradeTag) - Codeunit 332 “No. Series Upgrade Tags” (1 call:
SetupNoSeriesImplementation → GetImplementationUpgradeTag)
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.