Skip to:
problem: when admin setup Max Query Records - e.g. for 2 then:
1. related info window is not limited to 2 records2. strange popup - if the limited info window is running.
screens are attached.
remark: original idea of this max records was limit related records where too much records are slow-down info windows.
Solution is to create a specific related infowindow with specifi where/filter
mark as resolved
Hi Carlos,
Yes the max records apply to the header and it works .
Another max record on the tab of related to manage how many record of the subtab ..
Scenario : Joe Block with 3000 sales order ( related tab) .. setup only last 10 sales order
You could achieve solution by creating a specific related infow with a specif where/filter
Close ticket ?
Hi, I disagree about this one.
The max records apply to the header, not intended for detail tab as the tab is always filtered by the record selected on header.
This is similar to how normal windows behave, the max query applies to the query, not to the details that are filtered by the join with the header.
If the details has many records, then pagination is intended to manage the performance issues.
Regards,
Carlos Ruiz
triaged by Marco Longo
still in 7.1
Max Record IMHO should be set on the related infowindow
a) should be better create parameter of maxrecord on the related infowindow tab
set as minor priority
problem: when admin setup Max Query Records - e.g. for 2 then:
1. related info window is not limited to 2 records
2. strange popup - if the limited info window is running.
screens are attached.
remark: original idea of this max records was limit related records where too much records are slow-down info windows.