Number of records in detail grid must not be hardcoded
No, there is no such scenario. I get only one request for such configuration and only for single window. But once this feature is there, it may be used based on business requirements.
Talking about cluttering configuration - triggered idea on
Hi , that was the first idea from here:
I keep thinking the ability added in this ticket is not a good option for users from UX point of view - inconsistent experience.
So I dislike the idea of adding a new field in AD_Tab because that means cluttering more the tab configuration for a exceptional case that we don't want to encourage.
Do you have an scenario with so many exceptions?
isn’t it good idea to add PagingSize and DetailPagingSize field AD_Tab and we use sysconfig as default value, and this fields are used to override page size property?
Hi , I committed a solution in master.
The format of SysConfig ZK_PAGING_DETAIL_SIZE is as this:
list of components separated by semicolon (
first component is the wide default
further components (optional) are exceptions defined as pair of tab:size - where tab can be AD_Tab_ID, AD_Tab_UU or AD_TableName