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

Table 6317 "Power BI Deployment State"

Base Application · System.Integration.PowerBI

Across versions

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

Neighbourhood 1 connected objects and pages

Page 6348 "Power BI Deployment Steps" (pages and codeunits on it)Power BI Deployment Steps

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
Caption Power BI Deployment State
DataClassification SystemMetadata

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Entry No. Integer — AutoIncrement
2 Report Id Enum “Power BI Deployable Report” — enum Enum 6316 “Power BI Deployable Report”
3 Status Reached Enum “Power BI Upload Status” Specifies the upload stage that had been reached when this record was created. via Page 6348 “Power BI Deployment Steps” enum Enum 6305 “Power BI Upload Status”
4 Reached At DateTime Specifies the date and time when this status was reached. via Page 6348 “Power BI Deployment Steps”
6 Failed At DateTime Specifies the date and time when this step failed, if applicable. via Page 6348 “Power BI Deployment Steps”
7 Failed Reason Blob —
8 Failed Callstack Blob —

Keys

  • PK: Entry No. (clustered)
  • Key1: Report Id, Status Reached

Procedures

  • SetFailedReason(FailedReason: Text)
  • GetFailedReason(): Text
  • SetFailedCallstack(FailedCallstack: Text)
  • GetFailedCallstack(): Text

Pages and codeunits on this table

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: "table", object_name: "Power BI Deployment State"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources