Short answer to your question: In that menu list, set the number of records to -1. That will solve your problem in that case.
Long answer and explanation:
By default, the number of records (in all lists) is set to 0. Value 0 means that it will follow the general configuration of the application, which is by default set to 15 elements, through the variable defaultDBeditRows present in Configuracoes.xml file.
Configuracoes.xml file is written and mantained by WebAdmin solution (but this is not an available option, it must be set mannually, opening the file and changing this variable).
If you set anything that differs 0, it will not follow general configuration and will use that value to the number of records per page, yet, there is a special value that will not page and retrieve all records, and that value is -1.
Besides everything you do, while modelling, you should consider the performance downfall in your model when listing objects without any limit. By absurd, imagine how would your system react if you model a menu list of "Persons" without any limit, with a dozen columns from a table with the entire world population, and even worse, order it by date of birth... it would be a mess.
So, use it wisely.
About This Community
|Asked: 12/18/19, 5:39 PM|
|Seen: 309 times|
|Last updated: 4/22/20, 9:30 AM|