codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6326 "Power BI Customer Report"

Base Application · System.Integration.PowerBI

Across versions

  1. BC23-27not present
  2. BC28added
  3. BC291 procedures added
  4. BC30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 457 "Environment Information" (calls)Environment InformationCodeunit 6327 "Power BI Report Aggregator" (calls)Power BI Report Aggregator

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 · System.Integration.PowerBI · BC28-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Procedures

  • SetReportId(ReportId: Guid) (internal)
  • GetReportKey(): Text[100]
  • GetReportName(): Text[100]
  • GetStream(var InStr: InStream)
  • GetReportVersion(): Integer
  • GetUploadTracker(var UploadTracker: Interface "Power BI Upload Tracker")
  • FinalizeUpload(var UploadTracker: Interface "Power BI Upload Tracker"; Context: Text[50])
  • GetDatasetParameters(): Dictionary of [Text, Text]
  • GetTargetWorkspaceId(): Guid + BC29

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

Implements

Recent changes

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: "Power BI Customer Report"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources