0004577: Access via Edit Mode instead to access to grid

Notes
(0008754) pjuvara (reporter) 2008-08-26 14:01	Please restate the issue as a problem and not a suggested solution. Are you experiencing too long of a delay opening a window in edit mode? If so, which one? How long are you waiting for? What is your data distribution, etc?

(0009317) pjuvara (reporter) 2008-10-02 13:51	We know that the issue reproduces, we still need to figure out possible solution before scheduling the fix.

(0010060) pnuding (reporter) 2008-11-07 08:57	Issue is scheduled for resolution in Sprint 3 of the Performance project - as discussed with PJuvara reduced priority to urgent to avoid confusion

(0010409) shuehner (administrator) 2008-11-19 14:43	I did review the code involved in the access an entity via Edit mode. If this is the first access in the session either an empty window is shown and the search popup is opened (example: Business Partner). In Grid mode (example: Sales Orders) either all record are displayed or a filter to find "recent"/unprocessed transaction is applied (for windows marked as transactional). When a entity is accessed in Edit mode the last shown record is already saved in the session and used when the window is opened again. I could not find a case where all records are loaded and only one is shown. But, related to the navigation buttons and switching to grid mode a different query is used to get the index/position of the current record inside the selected records. This query does return multiple/lots of records, but only the id-field for each of them. In the current sprint we are working on performance improvements for this navigation and the transactional filters, which improve the response time very much. Can you please recheck this bug and give me an example of where all records are loaded for displaying a single one in Edit Mode, because i could not find a reproducible case where this happens. Or is the bug about the navigation issue above which loads many records (but only the id-column).

(0010601) opablo (reporter) 2008-11-25 10:14	I have not been able to reproduce this issue again, so I suppose it is already solved. Sorry for the inconvenience

(0010652) shuehner (administrator) 2008-11-25 16:56	Close issue after info from reporter that he cannot reproduce the bug anymore.

Issue History
Date Modified	Username	Field	Change
2008-08-05 10:23	opablo	New Issue
2008-08-05 10:23	opablo	Assigned To	=> cromero
2008-08-05 10:23	opablo	sf_bug_id	0 => 2038572
2008-08-05 10:23	opablo	Issue Monitored: opablo
2008-08-14 09:08	psarobe	Severity	major => minor
2008-08-14 09:08	psarobe	Status	new => scheduled
2008-08-14 09:08	psarobe	fix_in_branch	=> trunk
2008-08-26 14:01	pjuvara	Note Added: 0008754
2008-08-26 14:01	pjuvara	Status	scheduled => feedback
2008-09-16 17:22	cromero	Assigned To	cromero => shuehner
2008-10-02 13:50	pjuvara	Status	feedback => new
2008-10-02 13:50	pjuvara	Status	new => acknowledged
2008-10-02 13:51	pjuvara	Note Added: 0009317
2008-10-02 13:58	pjuvara	Priority	normal => high
2008-10-30 15:15	pjuvara	Priority	high => immediate
2008-11-03 10:37	rafaroda	Tag Attached: Performance
2008-11-07 08:57	pnuding	Note Added: 0010060
2008-11-07 08:57	pnuding	Priority	immediate => urgent
2008-11-07 08:57	pnuding	fix_in_branch	trunk =>
2008-11-19 13:09	iperdomo	Tag Attached: performance2.40scrum
2008-11-19 13:09	iperdomo	Tag Attached: Sprint-3
2008-11-19 14:33	shuehner	Status	acknowledged => scheduled
2008-11-19 14:33	shuehner	fix_in_branch	=> trunk
2008-11-19 14:43	shuehner	Note Added: 0010409
2008-11-19 14:43	shuehner	Status	scheduled => feedback
2008-11-25 10:14	opablo	Note Added: 0010601
2008-11-25 16:56	shuehner	Regression testing	=> No
2008-11-25 16:56	shuehner	Status	feedback => closed
2008-11-25 16:56	shuehner	Note Added: 0010652
2008-11-25 16:56	shuehner	Resolution	open => unable to reproduce

Relationships [ Relation Graph ] [ Dependency Graph ]