Page 6320 "Upload Power BI Report"
Base Application · System.Integration.PowerBI
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.Integration.PowerBI · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Upload Power BI Report |
| SourceTable | Power BI Customer Reports |
| PageType | NavigatePage |
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 | File | FileName |
Specifies File Name |
| Report Name | ReportName |
Specifies Report Name |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Creation | Upload Report | — |
Triggers
OnInit, OnOpenPage, OnClosePage
Relations
- source table Table 6310 “Power BI Customer Reports”
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 6301 “Power BI Service Mgt.” (3 calls:
OnClosePage → SynchronizeReportsInBackground,OnOpenPage → IsUserAdminForPowerBI,OnOpenPage → IsUserReadyForPowerBI) - Codeunit 6325 “Power BI Report Synchronizer” (1 call:
OnClosePage → UserNeedsToSynchronize)
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: "Upload Power BI Report"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.