Table 6325 "Power BI User Status"
Base Application · System.Integration.PowerBI
Across versionsobsolete removed since 26.0
- BC23present
- BC24declaration changed
- BC25unchanged
- BC26declaration changed
- BC27-30unchanged
Base Application · System.Integration.PowerBI · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Power BI User Status |
| DataClassification | CustomerContent |
| ObsoleteState | Removed |
| ObsoleteTag | 26.0 |
| ObsoleteReason | Check if the user has a pending job queue entry for codeunit “Power BI Report Synchronizer” instead and use the status from the job queue. |
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 | User Security ID | Guid | — | DataClassification EndUserPseudonymousIdentifiers |
| 10 | Is Synchronizing | Boolean | — | DataClassification SystemMetadata |
Keys
- Key1: User Security ID (clustered)
Deprecations
- object: Removed 26.0 (#if not CLEANSCHEMA26), “Check if the user has a pending job queue entry for codeunit “Power BI Report Synchronizer” instead and use the status from the job queue.”
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: "table", object_name: "Power BI User Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.