codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 20157 "Script Action Execution"

INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 7 connected objects and pages

Codeunit 20134 "Script Symbol Store" (calls, 41 links)Script Symbol StoreCodeunit 20132 "Script Data Type Mgmt." (calls, 3 links)Script Data Type Mgmt.Codeunit 20161 "Condition Mgmt." (calls, 3 links)Condition Mgmt.Codeunit 20133 "Script Symbols Mgmt." (calls, 2 links)Script Symbols Mgmt.Codeunit 20143 "Lookup Serialization" (calls)Lookup SerializationCodeunit 20293 "Use Case Execution" (calls)Use Case ExecutionCodeunit 20344 "Tax Posting Execution" (calls)Tax Posting Execution

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.

INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler · BC29-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnGetSymbolDataType subscribes to Codeunit “Lookup Mgmt.” OnGetSymbolDataType
  • OnIsSourceTypeSymbolType subscribes to Page “Script Symbol Lookup Dialog” OnIsSourceTypeSymbolType

Procedures

  • ExecuteScript(var SymbolStore: Codeunit "Script Symbol Store"; var SourceRecRef: RecordRef; CaseID: Guid; ScriptID: Guid)

Plus 27 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.

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

Evidence 1 sources