Codeunit 1081 "Fin. Report Default Upgrade"
Base Application · Microsoft.Finance.FinancialReports
Across versionsobsolete pending since 29.0
- BC23-27not present
- BC28added
- BC29declaration changed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Finance.FinancialReports · BC28-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Subtype | Upgrade |
| ObsoleteState | Pending |
| ObsoleteTag | 29.0 |
| ObsoleteReason | This upgrade code will be removed in a future release. |
Procedures
UpdateData()SetUpgradeTag(DataUpgradeExecuted: Boolean)
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” (3 calls:
SetUpgradeTag → SetSkippedUpgrade,SetUpgradeTag → SetUpgradeTag,UpdateData → HasUpgradeTag) - Codeunit 9998 “Upgrade Tag Definitions” (2 calls:
SetUpgradeTag → GetFinancialReportDefaultsUpgradeTag,UpdateData → GetFinancialReportDefaultsUpgradeTag)
Called by
- Codeunit 1080 “Feature - Fin. Report Default” (2 calls:
IsDataUpdateRequired → SetUpgradeTag,UpdateData → UpdateData)
Deprecations
- object: Pending 29.0 (#if not CLEAN29), “This upgrade code will be removed in a future release.”
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: "Fin. Report Default Upgrade"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.