codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 3038 "DotNet_XslCompiledTransform"

Base Application · System.Xml

Across versions

  1. BC23-27present
  2. BC28declaration changed
  3. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Codeunit 6224 "XML DOM Management" (calls, 3 links)XML DOM ManagementCodeunit 3013 "DotNet_XmlDocument" (calls, 2 links)DotNet_XmlDocumentCodeunit 3040 "DotNet_XsltArgumentList" (calls)DotNet_XsltArgumentList

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 · System.Xml · BC23-30 · source at ea08af5e · facts from BC29

Procedures

  • XslCompiledTransform()
  • Load(var DotNet_XmlDocument: Codeunit DotNet_XmlDocument)
  • Transform(var DotNet_XmlDocument: Codeunit DotNet_XmlDocument; DotNet_XsltArgumentList: Codeunit DotNet_XsltArgumentList; var DestinationStream: OutStream)
  • GetXslCompiledTransform(var DotNetXslCompiledTransform2: DotNet XslCompiledTransform)
  • SetXslCompiledTransform(DotNetXslCompiledTransform2: DotNet XslCompiledTransform)

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

Evidence 1 sources