Page 6314 "PBI Sales Pipeline"
Base Application · Microsoft.Integration.PowerBI
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.PowerBI · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | PBI Sales Pipeline |
| SourceTable | Power BI Chart Buffer |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | ID | ID | Specifies the ID. from the table field |
| Stage | Row No. | Specifies the stage of the sales pipeline that this entry is at. from the table field | |
| Value | Value | Specifies the value. from the table field | |
| Measure Name | Measure Name | Specifies the name. from the table field | |
| Sales Cycle Code | Measure No. | Specifies a code for the sales process. |
Triggers
OnOpenPage
Relations
- source table Table 6305 “Power BI Chart Buffer”
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.
- Codeunit 6309 “PBI Sales Pipeline Chart Calc.” (1 call:
OnOpenPage → GetValues)
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: "page", object_name: "PBI Sales Pipeline"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.