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

Codeunit 9655 "Init. Server Printer Table"

Base Application · System.Device

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 4030 "Client Type Management" (calls)Client Type ManagementPage 683 "Server Printers" (calls)Server Printers

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

Properties

Property Value
TableNo Printer

Procedures

  • ValidatePrinterName(var PrinterName: Text[250])
  • FindClosestMatchToClientDefaultPrinter(ReportID: Integer): Text[250]

Plus 4 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.

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

Evidence 1 sources