Table extension 36961 "Setup - Subscription Billing"
PowerBIReports · Microsoft.SubscriptionBilling.PowerBIReports
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
PowerBIReports · Microsoft.SubscriptionBilling.PowerBIReports · BC29-30 · source at ea08af5e · facts from BC29
Extends PowerBI Reports Setup.
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 |
|---|---|---|---|---|
| 37000 | Subs. Billing Report Name | Text[200] | Specifies the Power BI Subscription Billing Report. via Page extension 8014 “SubBill PBI Assisted Setup” | obsolete Pending 28.0; DataClassification CustomerContent |
| 37001 | Subscription Billing Report Id | Guid | — | obsolete Pending 28.0; DataClassification CustomerContent |
Relations
Deprecations
- object: guarded (#if not CLEANSCHEMA31)
- field Subs. Billing Report Name: Pending 28.0, “Tableextension moved to the Subscription Billing app, please add it to your dependencies”
- field Subscription Billing Report Id: Pending 28.0, “Tableextension moved to the Subscription Billing app, please add it to your dependencies”
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: "tableextension", object_name: "Setup - Subscription Billing"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.