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

Codeunit 6334 "Power BI Upload Step Runner"

Base Application · System.Integration.PowerBI

Across versions

  1. BC23-27not present
  2. BC28added
  3. BC29-30unchanged

Neighbourhood 5 connected objects and pages

Codeunit 6301 "Power BI Service Mgt." (calls, 5 links)Power BI Service Mgt.Codeunit 6325 "Power BI Report Synchronizer" (calls, 2 links)Power BI Report SynchronizerCodeunit 457 "Environment Information" (calls)Environment InformationCodeunit 6300 "Azure AD Mgt." (calls)Azure AD Mgt.Codeunit 9005 "Url Helper" (calls)Url Helper

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

  • Configure(var NewReport: Interface "Power BI Uploadable Report"; var NewUploadTracker: Interface "Power BI Upload Tracker"; NewContext: Text[50]) (internal)

Plus 6 local procedures.

Triggers

OnRun

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

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 Upload Step Runner"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources