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

Codeunit 9075 "Check Res. Jnl. Line. Backgr."

Base Application · Microsoft.Projects.Resources.Journal

Open in Claude9075.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 211 "Res. Jnl.-Check Line" (calls)Res. Jnl.-Check LineCodeunit 28 "Error Message Management" (calls)Error Message 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.

Base Application · Microsoft.Projects.Resources.Journal · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnAfterCheckResJnlLine(var ResJnlLine: Record "Res. Journal Line"; var TempErrorMessage: Record "Error Message" temporary) (integration)

Procedures

  • RunCheck(Args: Dictionary of [Text, Text]; var TempErrorMessage: Record "Error Message" temporary)
  • CollectErrors(ResJnlLine: Record "Res. Journal Line"; var TempLineErrorMessage: Record "Error Message" temporary)

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

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: "Check Res. Jnl. Line. Backgr."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources