First question is why query? Lets see the advantage of queries.
1.First you can limit the amount of data you retrieve from the server by defining only the specific columns you need
2.You can join multiple tables into one query saving loop code pattern.
3.They are also light weight than Table Queries.
Below is the article which gives step wise procedure how to fetch data using a query and how to link it to a part page
Last year I blogged about how to use the Text.BetweenDelimiters() function to extract all the links from the href attributes in the source of a web page. The code was reasonably simple but there’s now an even easier way to solve the same problem using the new Html.Table() function.
In this blog we will see how we can modify standard page by adding few fields and modify property of existing fields.
For this I assume table extension is already created and now would like to add fields in page layout by creating page extension
Introduction:
◾The requirement was such that , the user will select a line in the subform.
◾The subform has fields like the Customer ID, Customer Name, and a field Recieved Crates.
◾On click of the action button in the Main form, a page opens which contains the details of the selected line in the subform like Customer ID and Customer Name also a field Crate recieved(Integer Datatype).
In Microsoft Dynamics NAV, Lookup Form on a field corresponding to a particular selected option of another field can be displayed in the Request page of a report using C/AL code. In this article we are going to see the procedure with the code required to achieve the same.
As we all know we have certain limitations while designing a Page in NAV, i.e. We deliberately cant design our NAV Page as we want to, Actions OR Buttons must be on the Top, We cant make buttons somewhere on the middle of the Page, We can’t design a page in which we can have multiple controls like Buttons, Radio Buttons and so on and possibly anywhere on the Page.