Number of records in detail grid must not be hardcoded

Activity

Show:
Carlos Ruiz
March 21, 2020, 10:54 AM

Hi , I committed a solution in master.

Please test.

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

Regards,

Carlos Ruiz

Deepak Pansheriya
March 27, 2020, 3:21 AM

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?

Carlos Ruiz
March 27, 2020, 9:18 AM

Hi , that was the first idea from here:
https://groups.google.com/d/msg/idempiere/pdTpRincFNo/5WGLJJpNBgAJ

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?

Regards,

Carlos Ruiz

Carlos Ruiz
March 27, 2020, 11:00 AM

Talking about cluttering configuration - triggered idea on

Deepak Pansheriya
March 27, 2020, 12:54 PM

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.

 

Assignee

Carlos Ruiz

Reporter

Nicolas Micoud

Labels

Tested By

None

Fix versions

Priority

Major
Configure