Codeunit 20161 "Condition Mgmt."
INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 8 connected objects and pages
INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler · BC29-30 · source at ea08af5e · facts from BC29
Procedures
OpenConditionsDialog(CaseID: Guid; ScriptID: Guid; ID: Guid)CheckCondition(var SymbolStore: Codeunit "Script Symbol Store"; var SourceRecRef: RecordRef; CaseID: Guid; ScriptID: Guid; ActionID: Guid): BooleanCalculateVariants(LHS: Variant; RHS: Variant; Operator: Enum "Arithmetic Operator"; var OutputValue: Variant)
Plus 11 local procedures.
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 20134 “Script Symbol Store” (2 calls:
CheckCondition → GetConstantOrLookupValueOfType,CheckCondition → GetLookupValue) - Codeunit 20132 “Script Data Type Mgmt.” (1 call:
CheckCondition → GetLookupOptionString) - Codeunit 20142 “Lookup Mgmt.” (1 call:
CheckCondition → GetLookupDatatype)
Called by
- Codeunit 20157 “Script Action Execution” (3 calls:
ExecuteIfCondition → CheckCondition,ExecuteLoopWithCondition → CheckCondition,ExecuteNumberCalculation → CalculateVariants) - Codeunit 20156 “Action Dialog Mgmt.” (2 calls:
OpenIfConditionDialog → OpenConditionsDialog,OpenLoopWithConditionDialog → OpenConditionsDialog) - Codeunit 20283 “Switch Statement Execution” (1 call:
GetActionID → CheckCondition) - Codeunit 20293 “Use Case Execution” (1 call:
CanExecuteUseCase → CheckCondition) - Codeunit 20344 “Tax Posting Execution” (1 call:
ExecuteUseCaseOutput → CheckCondition)
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: "Condition Mgmt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.