codeunitRelationship Managementofficial - Microsoftderived - from the source, no model text

Codeunit 782 "Opportunity Chart Mgt."

Base Application · Microsoft.CRM.Analysis

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Page 782 "Opportunity Chart" (calls, 4 links)Opportunity ChartPage 5123 "Opportunity List" (calls)Opportunity List

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

Events published

  • OnAfterGetOppCount(var Opportunity: Record "Opportunity"; var NumberOfOpp: Integer) (integration)
  • OnDrillDownOnBeforeRunPage(var Opportunity: Record "Opportunity") (integration)

Procedures

  • DrillDown(var BusinessChartBuffer: Record "Business Chart Buffer"; Period: Record Date; OpportunityStatus: Option)
  • SetDefaultOppStatus(var Opportunity: Record Opportunity)
  • SetDefaultPeriod(var Period: Record Date)
  • SetNextPeriod(var Period: Record Date)
  • SetPrevPeriod(var Period: Record Date)
  • SetPeriodRange(var Period: Record Date)
  • UpdateData(var BusinessChartBuffer: Record "Business Chart Buffer"; Period: Record Date; OpportunityStatus: Option)

Plus 1 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

  • Page 782 “Opportunity Chart” (4 calls: OnOpenPage → SetDefaultOppStatus, OnOpenPage → SetDefaultPeriod, SetPeriodAndUpdateChart → SetPeriodRange, …)

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: "Opportunity Chart Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources