BC Observatoryunofficial, made by waldo
codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 4112 "Image Helpers"

Base Application · System.Media

Open in Claude4112.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 3971 "Image" (calls, 4 links)ImageCodeunit 2114 "O365 HTML Templ. Mgt." (calls, 2 links)O365 HTML Templ. Mgt.

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

Procedures

  • GetHTMLImgSrc(InStream: InStream): Text
  • GetImageType(InStream: InStream): Text

Plus 1 local procedures.

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.

  • Codeunit 3971 “Image” (4 calls: GetHTMLImgSrc → GetFormatAsText, GetHTMLImgSrc → ToBase64, GetImageType → GetFormatAsText, …)

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

Evidence 1 sources