{"title":"Designing card and document pages","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-designing-card-pages/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-designing-card-pages, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-designing-card-pages","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn how to design Business Central card and document pages with clear FastTabs, fields, actions, subpages, FactBoxes, and mobile layouts.","date":"2026-11-05","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Designing card and document pages","slug":"designing-card-and-document-pages","at":0,"chars":8493},{"level":2,"title":"Overview<#tab/about>","slug":"overviewtababout","at":242,"chars":1437},{"level":3,"title":"Card pages","slug":"card-pages","at":266,"chars":138},{"level":3,"title":"Document pages","slug":"document-pages","at":404,"chars":337},{"level":3,"title":"Associate with a list page","slug":"associate-with-a-list-page","at":741,"chars":403},{"level":3,"title":"Customizing pages from the client","slug":"customizing-pages-from-the-client","at":1144,"chars":535},{"level":2,"title":"#tab/structure","slug":"tabstructure","at":1679,"chars":4025},{"level":3,"title":"General definition","slug":"general-definition","at":1697,"chars":427},{"level":3,"title":"Structure","slug":"structure","at":2124,"chars":3580},{"level":2,"title":"Behavior points<#tab/behavior>","slug":"behavior-pointstabbehavior","at":5704,"chars":350},{"level":2,"title":"Developer tips<#tab/tips>","slug":"developer-tipstabtips","at":6054,"chars":853},{"level":3,"title":"Card pages","slug":"card-pages-1","at":6183,"chars":104},{"level":3,"title":"Document pages","slug":"document-pages-1","at":6287,"chars":145},{"level":3,"title":"General page design","slug":"general-page-design","at":6432,"chars":475},{"level":2,"title":"Designing for devices<#tab/targets>","slug":"designing-for-devicestabtargets","at":6907,"chars":1246},{"level":3,"title":"Promote frequently used actions","slug":"promote-frequently-used-actions","at":7159,"chars":144},{"level":3,"title":"Designing the subpage lists","slug":"designing-the-subpage-lists","at":7303,"chars":850},{"level":4,"title":"Choose the tile fields","slug":"choose-the-tile-fields","at":7335,"chars":379},{"level":4,"title":"Configure line-item shortcut actions","slug":"configure-line-item-shortcut-actions","at":7714,"chars":238},{"level":4,"title":"Configure gestures for actions","slug":"configure-gestures-for-actions","at":7952,"chars":201},{"level":2,"title":"Related information","slug":"related-information","at":8153,"chars":340}],"text":"# Designing card and document pages\nThe card page type displays details for an individual record. The document page type has a similar structure and typically includes a part that embeds another page, called a subpage, for transaction lines.\n## Overview<#tab/about>\n### Card pages\nDesign card pages so users can view, create, and modify master or reference records, such as customers, vendors, or items.\n### Document pages\nDesign document pages when you want to represent a transaction or other important event in the domain of business. Document pages are the computerized counterpart to paper-based documents, such as quotes, invoices, orders, and so on. As such, document pages often have associated workflow or audit trail requirements.\n### Associate with a list page\nBoth page types are typically associated with list pages that use the same source table, such as customer or sales order lists. Users select a record in the list and open its card or document page. Set the properties/devenv-cardpageid-property on the list page to associate it with the detail page. See List page structure<devenv-designing-list-pages#general-definition>.\n### Customizing pages from the client\nUsers can personalize card and document pages by rearranging or hiding content. See Personalizing your workspace</ui-personalization-user>.\nDevelopers and administrators can use Designer to create an extension with page changes. After you deploy the extension, its changes apply in environments where it is installed. To customize pages for a particular role, use profile customization instead. See Use Designer<devenv-inclient-designer> and Customizing for user roles<devenv-role-customization>.\n## #tab/structure\n### General definition\nA card page has the properties/devenv-pagetype-property set to Card. For a code example, see devenv-simple-card-page-example.\nA document page is defined by a page that has the properties/devenv-pagetype-property set to Document. A document page also includes a `part()` control that embeds another page into the document page. This typically displays line items from the associated transaction or event.\n### Structure\nThe following illustration identifies the main areas of card and document pages. Action placement can differ by version and configuration.\n![Annotated card and document pages showing system actions, FastTabs, fields, subpages, and FactBoxes.]\nThe following table describes the elements of the page.\n|No.|Area|Description|Usage guidelines|\n|1|System actions|The client provides actions to edit, create, or delete records. Availability depends on the page mode, user permissions, and properties such as properties/devenv-editable-property, InsertAllowed, ModifyAllowed, and DeleteAllowed.|You can't add custom actions to this system-action area. The actions shown depend on the page type, properties, mode, and user permissions.|\n|2|Action bar|Define the action bar in the actions section and individual actions with `action()` controls. Actions can open pages, run reports, or execute codeunits. The resulting interface depends on the action and its target.<br /><br /> Actions can appear on menus such as Actions, Navigate, and Report, or in promoted categories. Arrange them at the top level or in submenus.<br /><br /> See devenv-adding-actions-to-a-page.|Include actions that users need for the task, such as posting, running a report, or opening related information. Place important actions at the top level and group closely related actions.|\n|3|Promoted actions|Promoted actions appear prominently on the action bar. Define action references with actionref controls in `area(Promoted)`. Existing pages can also use legacy Promoted-related action properties.<br /><br /> See devenv-promoted-actions.|Promote important actions so users can find them easily. The placement of other actions depends on the action-bar layout and client. Older layouts use More options to show actions that aren't promoted.|\n|4|FastTab|A FastTab groups fields under a common heading. Define it with a `group()` control in `area(Content)`. A page can have multiple FastTabs. The page definition provides their initial order; extensions, profile customizations, and personalization can change it.|FastTabs help users find information in separate groups. The client arranges fields into columns according to available space. Use `grid()` and `fixed()` controls when a specific arrangement is needed. See Field arrangement on FastTabs<devenv-arranging-fields-on-fasttab>.|\n|5|Field|A page field displays a source-table field, an AL variable, or an expression. Add it with a `field()` control. The page definition provides the initial order; extensions, profile customizations, and personalization can change it.||\n|6|Show more/less|Users can show more or fewer fields in a FastTab. Set the properties/devenv-importance-property to choose which fields appear by default and which values appear in the collapsed FastTab heading.|For pages with many fields, show the most important fields by default and let users show more fields as needed.|\n|7|Subpage|Displays line items associated with a transaction. A `part(Name; Page)` control identifies the embedded page. In the illustration, a ListPart page displays sales order lines.||\n|8|Subpage action bar|Displays actions defined on the subpage. Define these actions in the same way as actions on the main page.||\n|9|FactBoxes|The pane on the right contains vertically arranged parts. They can display pages, charts, or system parts such as Notes and Record Links.<br /><br /> See devenv-adding-a-factbox-to-page.|Show information related to the current record. For example, show sell-to customer sales history for the selected sales order.|\n## Behavior points<#tab/behavior>\n The client adds system actions based on the page and its available capabilities. For example, Show Attached provides access to attached information.\n Search depends on the page and client capabilities. Open in Excel applies to supported list-based pages and list parts, not to the card or document page as a whole.\n## Developer tips<#tab/tips>\nFrom the user's perspective, the following are qualities of a well-designed card and document page:\n### Card pages\n Use it for master or reference data.\n Give the page a title that identifies the record.\n### Document pages\n Use it for a transaction or other important business event.\n Give the page a title that identifies the transaction or event.\n### General page design\n Organize data in FastTabs and show or hide fields by default based on their importance.\n Place the most important fields in the first FastTab, typically General, in a natural order for users.\n Include one or two FactBoxes with useful statistics and links to related documents.\n Use `group()` controls within FastTabs to organize fields into subgroups.\n Use the properties/devenv-visible-property to show or hide fields dynamically based on AL logic.\n## Designing for devices<#tab/targets>\nMobile devices generally display the same content as the web client. The layout adapts to the device and how users interact with it.\nYou can preview how your page will look on mobile devices directly in Designer.\n### Promote frequently used actions\nPromote the authored page actions that users need on phone and tablet clients. See devenv-promoted-actions.\n### Designing the subpage lists\n#### Choose the tile fields\nOn phones, line items display as tiles. Tablet clients can display line items in a grid. Define a `fieldgroup(Brick; <Field>)` in the source table to choose the tile fields. If you don't define Brick, the client uses DropDown. If you don't define either field group, the client uses the first five available repeater columns. See devenv-field-groups.\n#### Configure line-item shortcut actions\nUse the properties/devenv-scope-action-property to configure actions in the shortcut menu for a line item. This property is useful for actions related to the selected line, such as Line Comments.\n#### Configure gestures for actions\nUse the properties/devenv-gesture-property to configure the swipe direction for running actions on a touch device. See devenv-implementation-tips-gestures-property.\n## Related information\nAL development environment<devenv-reference-overview>\ndevenv-page-types-and-layouts\nPage extension object<devenv-page-ext-object>\ndevenv-actions-overview\nAdding pages and reports to search<devenv-al-menusuite-functionality>\nPersonalizing your workspace</ui-personalization-user>\nUse Designer<devenv-inclient-designer>"}