Table 6205 "Trans. Storage Export Data"
TransactionStorage · System.DataAdministration
Across versions
- BC23-28not present
- BC29-30present
TransactionStorage · System.DataAdministration · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| DataClassification | OrganizationIdentifiableInformation |
| Permissions | tabledata “Trans. Storage Export Data” = rimd |
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 | Table ID | Integer | — | |
| 2 | Part | Integer | — | |
| 3 | Content | Blob | — | |
| 4 | Record Count | Integer | — |
Keys
- PK: Table ID, Part (clustered)
Procedures
Add(var NewPart: Integer; var JsonArray: JsonArray; TableID: Integer; RecordCount: Integer)(internal)
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: "Trans. Storage Export Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.