Page 37016 "Purchases by Item"
PowerBIReports · Microsoft.PowerBIReports
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 5 connected objects and pages
PowerBIReports · Microsoft.PowerBIReports · captioned “Purchases by Item (Power BI)” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Purchases by Item (Power BI) |
| PageType | UserControlHost |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | All |
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
Recent changes
- 2026-08-06 #9896 Rename PBI embedded pages (main, BC30, refactor)
Documented on Microsoft Learn
- Using key performance indicators (KPIs) to meet your business goals
- Power BI Purchase app
- Purchases by Item (Power BI Report)
- Analytics in purchasing
- Analytics, business intelligence, and reporting overview
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: "Purchases by Item"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.
Evidence 6 sources
- codesrc/Apps/W1/PowerBIReports/app/Purchasing/Embedded/PurchasesbyItem.Page.alreleases/29.x @ ea08af5e
- learnUsing key performance indicators (KPIs) to meet your business goals
- learnPower BI Purchase app
- learnPurchases by Item (Power BI Report)
- learnAnalytics in purchasing
- learnAnalytics, business intelligence, and reporting overview