codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 4107 "Temp Blob Impl."

System Application · System.Utilities

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 4100 "Temp Blob" (calls, 9 links)Temp Blob

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.

System Application · System.Utilities · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Procedures

  • CreateInStream(var InStream: InStream)
  • CreateInStream(var InStream: InStream; Encoding: TextEncoding)
  • CreateOutStream(var OutStream: OutStream)
  • CreateOutStream(var OutStream: OutStream; Encoding: TextEncoding)
  • HasValue(): Boolean
  • Length(): Integer
  • FromRecord(RecordVariant: Variant; FieldNo: Integer)
  • FromRecordRef(RecordRef: RecordRef; FieldNo: Integer)
  • ToRecordRef(var RecordRef: RecordRef; FieldNo: Integer)
  • FromFieldRef(BlobFieldRef: FieldRef)
  • ToFieldRef(var BlobFieldRef: FieldRef)

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 4100 “Temp Blob” (9 calls: CreateInStream → CreateInStream, CreateOutStream → CreateOutStream, FromFieldRef → FromFieldRef, …)

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

Evidence 1 sources