Openbravo Issue Tracking System - Retail Modules
View Issue Details
0031808Retail ModulesWeb POSpublic2015-12-30 23:472016-02-01 16:15
mtaal 
migueldejuana 
normalminorhave not tried
closedinvalid 
5
 
RR16Q1 
mtaal
No
0031808: [16Q1.1] Remote data queries for product and business partner show one more than the data limit
See description and files related to linked issue:

Remaining topic:
I see the noted behavior still for customer search, so showing one too many and no message is displayed.

See the attachment. I set data limit for customers to 1 and remote customers to Y.

For products it works fine, although I don't like the message is too technical..

Please change the message to:
There is more data in the search results than can be displayed, narrow your search to get more precise results.
(or something similar, although this message is much longer so might give spacing issues, I don't think we should spend to much time on it)
Set the limit data preferences for product and business partner to a value of 1. Search for products/bps, 2 are shown.

https://issues.openbravo.com/view.php?id=31212 [^] [^]

http://wiki.openbravo.com/wiki/Retail:Configuration_Guide#Querying_performance [^] [^]
No tags attached.
blocks defect 0031807RR16Q2 closed migueldejuana Remote data queries for product and business partner show one more than the data limit 
Issue History
2015-12-30 23:49mtaalTypedefect => backport
2015-12-30 23:49mtaalTarget VersionRR16Q2 => RR16Q1
2015-12-30 23:50mtaalTarget VersionRR16Q1 =>
2015-12-30 23:50mtaalSummaryRemote data queries for product and business partner show one more than the data limit => [16Q1.1] Remote data queries for product and business partner show one more than the data limit
2015-12-31 07:35mtaalTarget Version => RR16Q1.1
2016-01-15 12:50OrekariaTarget VersionRR16Q1.1 => RR16Q1
2016-02-01 16:15mtaalReview Assigned To => mtaal
2016-02-01 16:15mtaalNote Added: 0083793
2016-02-01 16:15mtaalStatusscheduled => closed
2016-02-01 16:15mtaalResolutionopen => invalid

Notes
(0083793)
mtaal   
2016-02-01 16:15   
Issue is not serious enough to warrant a backport, will be done in Q2