Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0021869
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformmajoralways2012-10-05 11:402016-03-23 16:24
ReporteregoitzView Statuspublic 
Assigned ToAugustoMauch 
PriorityurgentResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version3.0MP15SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0021869: When unsing on the grid a default view different than the standard, two requests are done to the datasource

DescriptionIf you define a new view on a window and you set is a default, when accessing to the window two requests are done to the datasource.
The first with the standard information of the view, and the second with the definition of the custom view.

Steps To Reproduce-Activate the instance as system administrator.
-As admin go to any window. for example goods receipt.
-Clean the standard filters
-Then save the views as a new view and set is as default.
-Glose the goodsreceipt window
-Openbravo developers tool.
-Open again goods receipt window
-See on the network panel of developers tool that two requests has been done to the datasource: MaterialMgmtShipmentInOut
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0053202)
AugustoMauch (administrator)
2012-10-10 13:38

This issue has been changed to design defect, because it is working the way it was designed.

The first call to the datasource is done right after receiving the view description, which is user and role independent. The second call is not done until the personalization info is received, because it is not known until then if the default view is a saved view. This issue could be solved by delaying the first datasource call until the personalization info is received, but then the load of all the windows would be slower, even if they do not have a saved view set as default.

- Issue History
Date Modified Username Field Change
2012-10-05 11:40 egoitz New Issue
2012-10-05 11:40 egoitz Assigned To => AugustoMauch
2012-10-05 11:40 egoitz Modules => Core
2012-10-05 11:45 egoitz Priority urgent => immediate
2012-10-08 14:05 AugustoMauch Assigned To AugustoMauch => shankarb
2012-10-08 18:00 shankarb Assigned To shankarb => AugustoMauch
2012-10-10 13:36 AugustoMauch Type defect => design defect
2012-10-10 13:38 AugustoMauch Note Added: 0053202
2012-10-10 16:55 jonalegriaesarte Priority immediate => urgent
2016-03-23 16:24 eugeni Issue Monitored: eugeni


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker