What is difference between LOOK UP PAGE ID and DRILL DOWN PAGE ID in navision???

Business Central/NAV Technical Forum
1

request for answers

2

Hii
LookupPageID : This allows us to define which Page is the default for looking up data in this table.
DrillDownPageId :- this allows us to define which page is the default for drilling down into the supporting detail for the data that is summarized in this table.

1 Like
3

Hi ,
Whatever the page ID You Provide here that will be the default look for Lookup/drilldown page for that particular table . So Whenever the give table relation the respective page will appear there.

More In depth Detail

You want to run the page of a table but you didn’t know what might be the table so by defining above properties

the respective page can be run using CODE Like Below.

PAGE.RUN(0,varRecRef);

I Hope Info Helped you

4

LookupPageID is used a direct lookup on a table. Shortcut Key: Ctrl+F4.
Is used in e.g. Sales Invoice Header - when you hit Ctrl+F4 in field CustomerNo.
Or Sales Invoice Line, when you hit Ctrl+F4 i field “No.” (and Type=Item"

DrillDownPageID is used in a “relational-lookup”. Shortcut Key: F4.
E.g. in a Customer-page, pressing hyperlink in field “Balance” will open page “Customer Ledger Entries”.
And in Item Card, pressing hyperlink in field Inventory will open page “Item Ledger Entries”.

5

Anfinnur is correct, here’s some more information:

First you need to understand the difference between “look up” and “drill down”.

Look up is used to enter a value from a related table. For instance the customer number in a sales order. When you create the sales order, it does not have a customer yet, and to enter one you can use the dropdown arrow in the customer field, and that then opens the list of customers that you pick from. When you click on ‘Advanced’ then a new opens where you can see all the fields and actions. This page object is the page that is defined in the LookupPageID of the Customer table. All you need to do to be able to use this page is to set a table relationship to the customer table from another table, and the system will automatically use that page. Take a look at the “Bill-to Customer No.” field in the Sales Header table. All that is defined is the table relationship to the Customer table. Now take a look at the table properties of the Customer table, and note that the LookupPageID is “Customer List” which is page number 22. If you now open a sales order in the Windows client, and click advanced in the Customer field, then open ‘about this page’, you will see that the list page is number 22, the customer list.

So Look up for looking up a value to enter into a field with a table relationship.

Drill down is used to see the details of a flowfield, for instance the Balance field in the Customer table. The flowfield is defined as a calculated field into the Customer Ledger Entry table. You don’t select a value into this field, it is meant to provide you with a calculated value. Take a look at the “Qty on Porch order” field in the Item table, and note that the field class is flowfield, with a formula in the CalcFormula property that calculates a sum out of the Purchase Line table. Now look at the table properties of the Purchase Line table, and note that the DrillDownID is “Purchase Lines” which is page 518. Now in the Windows client, open an item card with a value in Qty on purchase order and click the value in there. You will see that the page that opens is page 518 and the filters on the page match the ones in the flowfield calc formula.

So drill down is looking at the details of the value of a flowfield.

It’s confusing sometimes when the same page is used for lookup and drill down, but there are differences that you can figure out yourself. The other part that is confusing is when the system overrides the definition of the flowfield and does something different. For instance, the Balance field in the customer table is a flowfield into the detailed customer ledger, but when you drill down into the balance on the customer card, it shows records from the customer ledger table instead. See if you can figure out how that works :slight_smile: