BC Observatoryunofficial, made by waldo
codeunitFixed Assetsofficial - Microsoftderived - from the source, no model text

Codeunit 5674 "FADimensionManagement"

Base Application · Microsoft.FixedAssets.FixedAsset

Open in Claude5674.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 408 "DimensionManagement" (calls, 5 links)DimensionManagementReport 5696 "Date Compress FA Ledger" (calls)Date Compress FA Ledger

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.

Base Application · Microsoft.FixedAssets.FixedAsset · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnBeforeCheckFAAllocDim(var FAAlloc: Record "FA Allocation"; DimSetID: Integer; var IsHandled: Boolean) (integration)

Procedures

  • GetSelectedDim(var SelectedDim: Record "Selected Dimension")
  • GetDimensions(var DimBuf: Record "Dimension Buffer")
  • CheckFAAllocDim(var FAAlloc: Record "FA Allocation"; DimSetID: Integer)
  • GetFALedgEntryDimID(Type: Integer; DimSetID: Integer)
  • TestEqualFALedgEntryDimID(DimSetID: Integer): Boolean

Triggers

OnRun

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.

Called by

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

Evidence 1 sources