Share This Post

Business Central Pages Overview

In Dynamics 365 Business Central Pages Overview are the main way to display and organize data. Pages are the primary object that a user will connect with and have a different behavior depending on the type of page that you choose.

Pages are designed independently of the device they are to be rendered on and in this way the similar page can be used again across phone, tablet and web clients. Business Central Pages Overview is defined in code as an object composed of controls, properties, actions and triggers. You can also use Designer in MS Dynamics 365 Business Central to create a page.

Whether you are creating a new page, or extending an existing page, you will add a new .al file to your project and describe the page object in code.

The difference in Business Central Pages Overview is basically that for a new page, you need to define the entire page, whereas when modifying an existing page, you only add the extra functionality or modify the existing.

The structure of a page is hierarchical and breaks down in to three sections. The initial block consists of metadata for the overall page. The metadata explains the page type and the source table it is displaying data from.

The next section; the layout, describes the visual parts on the page. The final section details the actions that are published on the page.

Furthermore, the page has properties. Properties work in the same way for pages as they do for other Dynamics 365 Business Central objects.

Microsoft Dynamics 365 Business Central Pages Overview

1. Page Metadata

For a new page object, you must at least specify the type of page; PageType and the data source; SourceTable of the page. And you can also set other metadata at the beginning of the declaration of the page object.

page 50102 PageName
{
PageType = List;
SourceTable = TableName;
Editable = true;
ContextSensitiveHelpPage = ‘feature-overview’;

}

Types of Pages

Which page type you select depends on the application task that you want to support, the content that you want to display and how you want to display it. The Role Center page is the main or home page and it assists the user focus on the most important daily tasks and activities.

Other types of pages, such as list pages or card pages are usually linked from the home page for easy access. The following Business Central Pages Overview types are available:

Page type Description
RoleCenter The Role Center page is the main page.
Card A Card page is used to view and edit one record or entity from a table.
CardPart A Card Part page is used in a FactBox on another page to view or edit additional fields associated with a selected entity in the page.
List A List page shows content from a table in a list format.
ListPart Similar to a List page, a List Part page shows content from a table in a list format. The difference is that you use the List part page as another page in a FactBox or as a part of the Role Center page.
ListPlus Similar to a List page, a List Plus page shows content from a table in a list format. The difference is that the List Plus page type can contain two lists in one page, and can be used as a two-dimensional matrix.
Document A Document page usually contains two separate pages integrated into one, with one page nested in the other. A Document page is suitable for use when you want to display data from two tables that are linked together.
WorkSheet You use a Worksheet page type for creating worksheet or journal task pages.
ConfirmationDialog You use the ConfirmationDialog page to display messages or prompt users with a confirmation before they continue with the task that they are working on.
StandardDialog The StandardDialog is a simple page type that you use when users only need to input data and do not need to perform other actions from the page.
NavigatePage You use a Navigate page type to create a wizard that leads the user through a sequence of steps for completing a task.
HeadlinePart You use a HeadlinePart page type to display a set of changing headlines on a Role Center.
API Pages of this type are used to generate web service endpoints and cannot be shown in the user interface. This page type should not be extended by generating a page extension object. Instead, create a new API by adding a page object.

2. Page Layout

The page layout of the page object determines what the page will look like and is specified in the layoutsection. The layout contains one or more area sections that define a certain placement on the page.

You can choose between the following area categories:

Area type Placement on the page
Content The content area displays the content of a RoleCenter or a List page.
FactBoxes The factbox area is placed to the right-most side of a page.
Displays content related to an item on the main content page.
RoleCenter The RoleCenter is the main page of the application and is used for quick access to frequently used information and tasks.
Page Actions

Business Central Pages Overview contains menu items and navigation controls called actions. In MS D365 Business Central, actions are displayed at the top of each page in the ribbon or in the navigation pane.

The actions section of the page describes what the user is able to do on a page and must be designed with the users need for process support in mind.

Actions can be displayed in the ribbon of all pages and grouped together under the following actions tabs:

  • Home
  • Actions
  • Navigate
  • Report

Creating actions can include adding activity buttons/cues to a page, configuring navigation items on a user role center, or adding Reports to a page. To learn how you can enable users to quickly locate the actions they want to use.

3. Using Keywords to Place Actions and Controls

You can use the following keywords in the layout section to place and move fields and groups on the page. Similarly, in the actions section, you use these keywords to place actions in the ribbon.

Keywords Syntax Applies to
addfirst addfirst(Anchor) Anchor: areas and groups
addlast addlast(Anchor) Anchor: areas and groups
addafter addafter(Anchor) Anchor: controls, actions and groups
addbefore addbefore(Anchor) Anchor: controls, actions and groups
movefirst movefirst(Anchor; Target1, Target2) Anchor: area, group
Target: list of actions or list of controls
movelast movelast(Anchor; Target1, Target2) Anchor: area, group
Target: list of actions or list of controls
moveafter moveafter(Anchor; Target1, Target2) Anchor: controls, actions and groups
Target: list of actions or list of controls
movebefore movebefore(Anchor; Target1, Target2) Anchor: controls, actions and groups
Target: list of actions or list of controls
modify modify(Target) Target: controls, actions and groups

4. Adding Help to the Page Objects

The Business Central user assistance model expects your solution to include tool tips and links to context sensitive Help.

Context Sensitive Help

To apply context sensitive Help to your app, you define a URL to your Help library in the app.json file and you then set the relevant target Help files as property values for each of your page objects and page extension objects.

Tool Tips

In combination with descriptive captions and instructional text, tool tips are our current implementation of embedded user assistance, which is an important principle in today’s world of software design.

Instructional Text

The base application has applied instructional text to setup guides and certain other types of page objects. Your extensions are expected to also include instructional text to setup guides for the same reason. For more details on Microsoft Dynamics 365 Business Central Pages Overview, please contact us.

Share This Post

Leave a Reply

avatar
  Subscribe  
Notify of
Skip to toolbar