Codeunit 5892 "Feature-ManualFlushingMethod"
Base Application · System.Environment.Configuration
Across versionsobsolete pending since 26.0
- BC23-25not present
- BC26added
- BC27-28unchanged
- BC29-30not present
Neighbourhood 3 connected objects and pages
Base Application · System.Environment.Configuration · BC26-28 · source at d6dc01d0 · facts from BC28
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Permissions | TableData “Feature Data Update Status” = rm |
| ObsoleteState | Pending |
| ObsoleteTag | 26.0 |
| ObsoleteReason | Feature ‘Manual Flushing Method without requiring pick’ will be enabled by default in version 29.0. |
Procedures
IsDataUpdateRequired(): BooleanReviewData()UpdateData(FeatureDataUpdateStatus: Record "Feature Data Update Status")AfterUpdate(FeatureDataUpdateStatus: Record "Feature Data Update Status")GetTaskDescription(): Text
Plus 11 local procedures.
Calls
From the extracted call graph of BC28 (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 → HasUpgradeTag,SetUpgradeTag → SetSkippedUpgrade,SetUpgradeTag → SetUpgradeTag) - Codeunit 2614 “Feature Data Update Mgt.” (1 call:
UpdateData → LogTask) - Codeunit 9998 “Upgrade Tag Definitions” (1 call:
SetUpgradeTag → GetManufacturingFlushingMethodActivateManualWithoutPickUpgradeTag)
Implements
Deprecations
- object: Pending 26.0 (#if not CLEAN26), “Feature ‘Manual Flushing Method without requiring pick’ will be enabled by default 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). The call sections above are our own, per object, from the BC28 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: "Feature-ManualFlushingMethod"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.