tableWarehouseofficial - Microsoftderived - from the source, no model text

Table 7700 "Miniform Header"

Base Application · Microsoft.Warehouse.ADCS

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC287 fields changed
  5. BC29-30unchanged

Neighbourhood 15 connected objects and pages

Page 7703 "Miniforms" (pages and codeunits on it, 2 links)MiniformsCodeunit 7705 "Miniform Logon" (pages and codeunits on it)Miniform LogonCodeunit 7706 "Miniform Logoff" (pages and codeunits on it)Codeunit 7707 "Miniform Mainmenu" (pages and codeunits on it)Miniform MainmenuCodeunit 7708 "Miniform Pick Activity List" (pages and codeunits on it)Miniform Pick Activity ListCodeunit 7709 "Miniform Put Activity List" (pages and codeunits on it)Miniform Put Activity ListCodeunit 7710 "Miniform Move Activity List" (pages and codeunits on it)Miniform Move Activity ListCodeunit 7711 "Miniform Whse. Activity Line" (pages and codeunits on it)Miniform Whse. Activity LineCodeunit 7712 "Miniform Phys. Journal List" (pages and codeunits on it)Miniform Phys. Journal ListCodeunit 7713 "Miniform Phys.-Inventory" (pages and codeunits on it)Miniform Phys.-InventoryPage 7700 "Miniform" (pages and codeunits on it)Codeunit 6224 "XML DOM Management" (calls)XML DOM ManagementTable 7701 "Miniform Line" (referenced by, 2 links)Miniform LineTable 7703 "Miniform Function" (referenced by)Miniform FunctionUse Automated Data Capture Systems (ADCS) foundation (Learn pages)Use Automated Data Capture S…

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

Learn documents this table through its pages: Page 7700 “Miniform” (1 Learn page), Page 7703 “Miniforms” (1).

Properties

Property Value
Caption Miniform Header
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 Δ BC28 Code[20] Specifies a unique code for a specific miniform. NotBlank
11 Description Δ BC28 Text[30] Specifies your description of the miniform with the code on the header.
12 No. of Records in List Δ BC28 Integer Specifies the number of records that will be sent to the handheld if the miniform on the header is either Selection List or Data List.
13 Form Type Δ BC28 Option Specifies the form type of the miniform. OptionCaption: ‘Card,Selection List,Data List,Data List Input’, Locked = true
15 Start Miniform Δ BC28 Boolean Specifies that this field is the first miniform that will be shown to the user when starting up a handheld.
20 Handling Codeunit Δ BC28 Integer Specifies the number of the codeunit containing the code that handles this miniform. TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Codeunit))
21 Next Miniform Δ BC28 Code[20] Specifies which form will be shown next when a selection is made in a Data List form or when the last field is entered on a Card form. TableRelation Table 7700 “Miniform Header” (Miniform Header)
25 XMLin BLOB —

Keys

  • Key1: Code (clustered)

Procedures

  • SaveXMLin(DOMxmlin: DotNet XmlDocument)
  • LoadXMLin(var DOMxmlin: DotNet XmlDocument)

Triggers

OnDelete

Relations

Referenced by

4 fields in 3 objects relate to this table (TableRelation or CalcFormula).

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: "Miniform Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources