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

Report 5085 "Contact Cover Sheet"

Base Application · Microsoft.CRM.Reports

Open in Claude5085.mdSource on GitHub

Across versions

  1. BC23-28present
  2. BC29declaration changed
  3. BC30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 365 "Format Address" (calls)Format AddressCodeunit 9520 "Mail Management" (calls)Mail ManagementContact Cover Sheet report (Learn pages)Contact Cover Sheet reportRelationship management reports (Learn pages)Relationship management repo…

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

Properties

Property Value
Caption Contact Cover Sheet

Procedures

  • SetRunFromSegment()

Plus 1 local procedures.

Triggers

OnInitReport

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.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 3 sources