Page 8036 "Usage Data Blobs"
Subscription Billing · Microsoft.SubscriptionBilling
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Usage Data Blobs |
| SourceTable | Usage Data Blob |
| PageType | List |
| ApplicationArea | All |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| General | Entry No. | Entry No. | Specifies the sequential number assigned to the record when it was created. |
| Usage Data Import Entry No. | Usage Data Import Entry No. | Specifies the sequential number of the related import that was assigned to it when it was created. | |
| Supplier No. | UsageDataImport."Supplier No." |
Specifies the number of the supplier to which this usage data refers. | |
| Supplier Description | UsageDataImport."Supplier Description" |
Specifies he description of the supplier to which this usage data refers. | |
| Description | Description | Specifies the description of the import. | |
| Import Date | Import Date | Specifies the date of the import. | |
| Import Status | Import Status | Specifies the status of the import. | |
| Reason (Preview) | Reason (Preview) | Specifies the preview why the import failed. | |
| Source | Source | Specifies the file name of the import file. | |
| Data Hash Value | Data Hash Value | Specifies the hash value of the file. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Export Data | Exports the blob data to a file. |
Triggers
OnAfterGetRecord
Relations
- source table Table 8011 “Usage Data Blob”
Pages and codeunits on this table
- Table 8011 “Usage Data Blob” (drill-down page)
- Table 8011 “Usage Data Blob” (lookup page)
Documented on Microsoft Learn
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: "page", object_name: "Usage Data Blobs"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.