Page 7700 "Miniform"
Base Application · Microsoft.Warehouse.ADCS
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Warehouse.ADCS · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Miniform |
| SourceTable | Miniform Header |
| PageType | ListPlus |
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 | Code | Code | Specifies a unique code for a specific miniform. from the table field |
| Description | Description | Specifies your description of the miniform with the code on the header. from the table field | |
| Form Type | Form Type | Specifies the form type of the miniform. from the table field | |
| No. of Records in List | No. of Records in List | 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. from the table field | |
| Handling Codeunit | Handling Codeunit | Specifies the number of the codeunit containing the code that handles this miniform. from the table field | |
| Next Miniform | Next Miniform | 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. from the table field | |
| Start Miniform | Start Miniform | Specifies that this field is the first miniform that will be shown to the user when starting up a handheld. from the table field | |
| Content | Control9 | part Page 7701 “Miniform Subform” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Mini Form | Functions | Access functions to set up the ADCS interface. | Page 7705 “Miniform Functions” |
Relations
- source table Table 7700 “Miniform Header”
Pages and codeunits on this table
- Page 7703 “Miniforms” (card 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: "Miniform"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.