Page 37071 "Revenue Development"
PowerBIReports · Microsoft.PowerBIReports
Across versionsobsolete pending since 28.0
- BC23-28not present
- BC29-30present
PowerBIReports · Microsoft.PowerBIReports · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Revenue Development |
| PageType | UserControlHost |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | All |
| ObsoleteState | Pending |
| ObsoleteTag | 28.0 |
| ObsoleteReason | Please use and extend page “Revenue Development Power BI” on the Subscription Billing app. |
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 |
|---|---|---|---|
| Content | PowerBIAddin | add-in PowerBIManagement | — |
Triggers
OnOpenPage
Deprecations
- object: Pending 28.0 (#if not CLEAN28), “Please use and extend page “Revenue Development Power BI” on the Subscription Billing app.”
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). 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: "Revenue Development"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.