tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 5433 "Tenant Config. Package File"

Base Application · System.IO

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC26declaration changed
  5. BC27-30unchanged

Neighbourhood 3 connected objects and pages

Page 20054 "APIV1 - Aut. Conf. Pack. File" (pages and codeunits on it)APIV1 - Aut. Conf. Pack. FilePage 30057 "APIV2 - Aut. Conf. Pack. File" (pages and codeunits on it)APIV2 - Aut. Conf. Pack. FileCodeunit 4100 "Temp Blob" (calls)Temp Blob

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.IO · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Tenant Config. Package File
DataClassification CustomerContent

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 Code Code[20] Specifies a code for the configuration package. via Page 30057 “APIV2 - Aut. Conf. Pack. File” NotBlank; DataClassification SystemMetadata
2 Content BLOB Specifies a contect package. via Page 30057 “APIV2 - Aut. Conf. Pack. File” DataClassification SystemMetadata

Keys

  • Key1: Code (clustered)

Procedures

  • SetContentFromBlob(TempBlob: Codeunit "Temp Blob")

Pages and codeunits on this table

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Tenant Config. Package File"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources