Pages- 2nd object type in Nav 2015

Pages

Why pages rather than forms since NAV 2013?

Pages Enables users to view, add, change, or delete records in a table.

In 2009 there was both pages(role tailored) and forms(classic client). Whereas since 2013 it is only role tailored client introduced and the role tailored client was renamed as windows client, web client and SharePoint client was an added addition here.

Forms object was removed in nav 2013 mainly because pages got all the features of forms and web services were introduced(we can view pages as web pages in internet browsers by giving address path, I mean URL to the internet browsers.)

Everything we write was exported in xml or text format which support internally the .Net feature.

As the technology raising Nav is getting adopted to IT fields recent technologies, It turned from

Form to pages, from normal native database to M.S Sql server and web client, I am sure by Microsoft will also replace C/AL language by C#(.Net) by end of 2017.

A brief overview about Pages

When it comes to pages let me now start discussing about a page called CustomerList which is already existing page in Nav.

Usually, Page tool bars at top will include

Action: Includes some action to be performed.

Ex: remainder action is used to remind the customer that he has to do some actions(transaction, sales etc.) in specified time.

Navigation: To give some additional information.

Ex: Comment provides some header information about what’s going on.

Report: previews the page summary.

Ex: summary

Home: frequently used action, navigation or report buttons are dragged to Home tool bar.

As per industrial standard it is to be noted that at least one action button should be present in Home tool bar.

Page Types and Characteristics

• It’s one of the most important page property where we need to specify which type the page belongs in the PageType property.

• Page type determines how the page is displayed in the client.

• It also controls certain behavioral characteristics of the page.

• Selecting the correct page type when you design pages is very important, because the pages are interpreted differently in the client, depending on their page type.

• Each pagetype also use d/f set of controls which become the important concept during page design.

1. Card Page

Why we need it?

Use a card page when there are too many fields to view on one line

·          Tables that use card pages only have one field in their primary key. (Primary key here is restricted to only one field)

·         This field always is displayed as the first field in the General FastTab.

·         They’re related to master table.

·         Primary key should be of length 20 and should be integer no. or code as data type. (name can be code/no.) where as no. should be integer.

·         A card page enables users to view and edit one record at a time.

In fact box,

1.       Link address is used to give web path ( URL for setup table.

2.      Notes is used to notify any particular/ regular customer (to give some additional benefits and discounts)

Ex: a person who is regular to sales gets his discount of 10% than other customer and his delay time will be also extended.

In ERP, invoice is nothing but bill, condition and rules given to customer, I’ll be often using this word from hereon to indicate some transactions topic.

Naming Card Page

Use the associated table name to name card pages, followed by the word “Card”. For example, the card page that is associated with the Customer table is named Customer Card.       

 2.  List Page

·         A list page is a multi-record page that enables users to view multiple records from a table at the same time (provides brief information about the page).

·         The primary key fields of the associated table are displayed in the left-most columns.

·         Every master table should’ve list, card and statistical page data(brief detail like amount, balance)

Naming List Pages

If you cannot edit the list page the list page that is associated with the Customer table is named Customer List. 

If you can edit the list page then the list page associated with the Currency table is named Currencies (plural name).

3. RoleCentered Page

·         Page represents a customized user home page displays the parts or controls that are relevant to a user’s role.

·         Role centers may also include the ListParts with the most relevant information for the user, such as My Customers or My Items. A developer can add system parts, such as Outlook, My Notifications, and charts, during design time. Users can add these system parts during run time.

Naming Role Center Pages

The role center page that is associated with the Order Processor role is named Order Processor Role Center.

4. CardPart Page

·         This is related to particular customer. 

·         CardPart page is used to create a single-column FactBox.

·         They are used  to display fields or a special control like a picture viewer.

Naming CardPart Page

CardPart pages are named with the associated information, followed by the word FactBox. For example, the CardPart page that displays the sales history of the sell-to customer is named Sales Hist. Sell-to FactBox.

5. ListPart Page

·          Use a ListPart page to display subpages for documents.

·          You can also used a ListPart page as a FactBox to display multiple rows and columns from a single table

Difference b/w List page, card part page and listpart page.

List page: displays multiple record with info.

Card page: to display only 1 record.

Card part: to display 1 record/ single column fact box.

List part: to display multiple records/ multiple row, column fact boxes. 

Naming ListPart Pages

The ListPart page that displays the Dimensions is named Dimensions FactBox. When you use ListPart pages as subpages for documents, name them with the associated document name, followed by the word “Subform” or “Subpage”. For example, the ListPart page that displays the lines for the Sales Order is named Sales Order Subform.

6. Worksheet Page

·         This page is used very frequently.

·         It is a multi-record page that enables users to view multiple records from a table and edit them.

·         Worksheet pages let users set filters or options that are shown over the repeater control.

·         Worksheet pages may include a footer which summarizes information from the worksheet or shows detailed information about the currently selected line.

·         You can use worksheet pages as journals.(D.T uses line no. of type integer.

·         Worksheet are related to journal table. They ‘re used to distinguish b/w different records.

·          The primary key fields of the associated table do not show on the worksheet page.

·         Worksheet pages differ from ordinary list pages. 

·         When a user inserts a new record in a Worksheet page, the record does not jump to another position within the page, but remains in the same order in which the user inserted it. 

·         The AutoSplitKey property of the page, combined with an integer as the last field in the table's primary key enables this order.

·         Implicitly adds +1 to the document no. if AutoSplitKey is yes. If it is no there’s no automatic increment and it raises an error to give document no.

Naming Worksheet Pages

Worksheet pages are named according to the purpose of the associated table. For Journal tables, the name of the Worksheet page ends with the word Journal. For example, the main journal for the General area of the Financial Management application area is called General Journal.

7. Document Page

·           A document page is a page that contains a series of FastTabs and a page part with lines on the same page. It displays information from two tables with the master-detail relationship, such as Sales Header and Sales Line, or Purchase Header and Purchase Line tables.

·            They can’ve 1 line page.

·             Except line tab in the below diagram all other tabs are related to document header.

·            As, I discussed in document table here also there’ r two types.

1.       Document header: contains main information

2.      Document line: Contains detailed information(In below fig of line tab it includes line document table information.

Naming Document Pages

The name of a document page is the function that it represents, such as, Sales Order.

8. NavigatePage page

·         As, the word says it is used to navigate to some other information. You can achieve this by clicking on the navigation bar.

·         It display only posted information(ex. Posted sales)

·         We cannot edit in this page only display.

·         This page is used for searches that are based on individual posting transactions, such as page 344, Navigate

·         Navigate page type supports showing multiple tabs of information, changing visibility of tabs during run time, and positioning actions in the footer bar.

·         This layout makes NavigatePage pages good candidates for wizards because they show actions as command buttons, and enable toggling visibility of tabs during run time. For example, page 5077, Create Interaction, shows a wizard-like interface that moves the user through a series of questions, before it makes changes to the database.

Naming Navigate Pages

There is no specific requirement for naming NavigatePage pages. Page 344 is named simply Navigate, while typical wizards may be named according to the task they accomplish, such as page 5077, Create Interaction.

9. ListPlus Page

·         A ListPlus page resembles a document page, because it also contains FastTabs and a ListPart named Lines.

·         Whereas document pages typically allow for inserting and deleting lines, and use on the AutoSplitKey property,

·         Document line can’ve only 1 line page, whereas listplus can’ve more than one document line.

·         This page is used very rarely

·         ListPlus pages typically only allow for viewing, or editing existing lines.

·           ListPlus pages do not allow insertion or deletion of lines from the subpage. For example, page 397, Sales Invoice Statistics is a ListPlus page. Because ListPlus pages do not allow the insertion of lines, and show fixed, or pre-determined information in the lines, they may be used instead of card pages for master data management, such as, page 5050, Contact Card.

   

Naming ListPlus Pages

There is no specific convention regulating the naming of the ListPlus pages. If you use a ListPlus page instead of a card page, such as in the example of page 5050, Contact Card, then it should follow the naming conventions for the card pages.

10. ConfirmationDialog Page

·         A confirmation dialog asks the user a question that can be answered with minimal data input, and requires the user to click Yes or No. Pages of this type contain a question, and may contain a single FastTab named Details. This provides the necessary information for the user to make a choice.

·         It’s used for user confirmation we can write code and call this page.

Naming ConfirmationDialog Pages

There is no strict convention for naming confirmation dialog boxes. However, you may want to consider using the object of the confirmation preceded by the word Check or Confirm. For example, the confirmation dialog that requires the user to confirm a transaction for a customer who is over the credit limit is named Check Credit Limit.

11. StandardDialog Page

·         Its used to display information after result(ex. Posted

·         A standard dialog page is a simple page type that you use when users only input data and do not perform any other actions from the page.

·         Standard dialog boxes do not contain ribbon, FastTabs, or FactBoxes.

Naming StandardDialog Pages

Users cannot customize the appearance and behavior of these pages.

For example, page 511, Change Exchange Rate is of the StandardDialog page type.

There is no strict convention for naming standard dialog boxes. You may name them according to the task that they perform. 

For example, the standard dialog for changing the currency exchange rate on documents is named Change Exchange Rate.