reportProjectsofficial - Microsoftderived - from the source, no model text

Report 1093 "Job Create Sales Invoice"

Base Application · Microsoft.Projects.Project.Planning

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-28unchanged
  4. BC29declaration changed
  5. BC30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 1005 "Job Calculate Batches" (calls, 2 links)Job Calculate BatchesCodeunit 1002 "Job Create-Invoice" (calls)Job Create-Invoice

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.Project.Planning · captioned “Project Create Sales Invoice” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Project Create Sales Invoice
UsageCategory Tasks
ApplicationArea Jobs

Events published

  • OnAfterPostReport(NoOfInvoices: Integer) (integration)
  • OnAfterPreReport() (integration)
  • OnBeforeOnOnInitReport(var JobChoice: Option Job,"Job Task") (integration)
  • OnBeforeJobTaskOnAfterGetRecord(JobTask: Record "Job Task"; var IsHandled: Boolean) (integration)
  • OnBeforePostReport() (integration)

Triggers

OnInitReport, OnPostReport, OnPreReport

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.

Recent changes

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: "report", object_name: "Job Create Sales Invoice"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources