Hi,
I know I can change globally number of rows per listview.
In normal work we are using 20 or 50 records which increases the speed., but from time to time some users would like to see 200 or 500.
Is there a way to do it per user or on click…?
Yeah, even I set it before globally in the config file. I don’t know if it is possible to do user-wise. You may need to write a custom code for it.
Are you using suitecrm v7.x?
@masq LOL! Teach your users how to use the filter properly. There no reason I can think of to have 200 or 500 records on the screen. I really don’t understand why people even need more than 20. If you use your filters correctly and save meaningful filters, in a couple of clicks you find what you need to see whithout scrolling through 500 records.
Why do they need 500 records on the screen? Maybe I can help?
Well. maybe it is user related issue:)
I have added a coloring of each row depending of one field (custom code) what makes “taking a look” much simpler.
Yes, i know that filters whould do the same but with custom row color it is actually faster to go through records.
Thnka for help, it seems that if users will push, only filter lesson or custom code will help
HI,
To customize the number of rows displayed in the ListView of SuiteCRM, you will need to make some modifications to the code.
- Navigate to the custom/modules/{Module_Name}/ directory. Replace {Module_Name} with the actual name of your module.
- If the directory does not exist, you may need to create it.
- Inside this directory, you might need to create a new file if it doesn’t exist. The file you are looking for is usually called list.php in this file you need to override the list view query and set the paramter limit to controll the number of records to display
Hello Piotr,
why not use the setting for it in the admin area?
System Settings
the very first setting:
For 200 the load time become visible - compared to 20 or 50 which is almost instant.
And for 200 the disdvantage is, among others, the checkbox for the mass updates - your front end logic loads a lot of records + forms and the browser consumes a lot of CPU to render the records.
@pstevens For end users I’m with you - ideally use quick filters to see the few records that you really need to see for the current process.
For admin and data quality tasks, I often prefer more records because data patterns become obvious if you list more directly underneath each other.
For bigger data quality stuff I usually work with reports and ex- imports. For smaller things like updating 400 records, the mass updates would be perfect - unfortunately, the browser becomes quite CPU hungry there 