Secondary list pages allow us to display a subset of data without having to write a new list page, interaction class, or query. Typically, these are used to show data based on a status, for example, open purchase orders, sales orders for customers on hold, and so on.
We will create two types of secondary list pages: one for a status field on the vehicle, and the other to list vehicles that have an appointment.
An active vehicle is determined by the VehicleStatusId
field, so we will use this in order to filter the data in the list page. Prior to AX 2012, this was done by modifying the form to add a range to the form data source's query. This led to the code being written onto the form itself, which isn't possible on a list page. This is a good thing, as it forces us to use a better, more extendable practice.
Another method would be to simply duplicate the query, but this means duplication of effort and maintenance—always to be...