BC Observatoryunofficial, made by waldo
codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 2617 "Printer Setup Impl."

System Application · System.Device

Open in Claude2617.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 2616 "Printer Setup" (calls, 5 links)Printer SetupPage 2616 "Printer Management" (calls, 2 links)Printer Management

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

Properties

Property Value
Access Internal

Procedures

  • GetPrinterType(Printer: Record Printer): Enum "Printer Type"
  • OpenPrinterSettings(PrinterID: Text)
  • GetPrinterSelectionsPage(var PageID: Integer; var IsHandled: Boolean)
  • SetDefaultPrinterForCurrentUser(PrinterID: Text)
  • SetDefaultPrinterForAllUsers(PrinterID: Text)

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 2616 “Printer Setup” (4 calls: GetPrinterSelectionsPage → GetPrinterSelectionsPage, OpenPrinterSettings → OnOpenPrinterSettings, SetDefaultPrinterForAllUsers → OnSetAsDefaultPrinter, …)

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

Evidence 1 sources