Codeunit 3013 "DotNet_XmlDocument"
Base Application · System.Xml
Across versions
- BC23-27present
- BC28declaration changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · System.Xml · BC23-30 · source at ea08af5e · facts from BC29
Procedures
InitXmlDocument()PreserveWhitespace(PreserveWhitespace: Boolean)Load(InStream: InStream)OuterXml(): TextGetXmlDocument(var DotNetXmlDocument2: DotNet XmlDocument)SetXmlDocument(DotNetXmlDocument2: DotNet XmlDocument)
Triggers
OnRun
Called by
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 6224 “XML DOM Management” (8 calls:
CreateXslTransformFromBlob → InitXmlDocument,CreateXslTransformFromBlob → Load,TryGetXMLAsText → InitXmlDocument, …) - Codeunit 3038 “DotNet_XslCompiledTransform” (2 calls:
Load → GetXmlDocument,Transform → GetXmlDocument)
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_XmlDocument"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.