Opened 6 years ago

Last modified 5 years ago

#280 new Issue

Graph values table too big

Reported by: Kim Neerings Owned by:
Priority: Unknown Milestone: Needs Analysis
Component: Admin-App Version: 3.0
Severity: Unknown Keywords: graph values, data table


A graph is setup using a category with a large number of values (i.e. Counties) and a data series with a large number of values (i.e. Years), the system seems to have a hard time dealing with such a large table. It will allow the users to initially view the table, but once any change is made, if the user attempts to save, an error message is received (see attached).

Attachments (1)

Ticket280.png (112.0 KB) - added by Kim Neerings 6 years ago.
error message

Download all attachments as: .zip

Change History (7)

Changed 6 years ago by Kim Neerings

Attachment: Ticket280.png added

error message

comment:1 Changed 6 years ago by Garth Braithwaite

This ticket does not provide enough details. Think about what you would need if you were trying to troubleshoot something. We know it's the admin app but which version of the app - trunk dev code or released code? What IP and which view? Is it only when you create a new view? Is it when you have 5, 10, 15, 18, 37 rows? What are the specific steps to recreate the problem? This information will be required in the ticket or via a call. If it's not in the ticket then how can a tester adequately test? They also won't know the steps to reproduce etc.

comment:2 Changed 6 years ago by Garth Braithwaite

Additional info: Garth running latest code locally can create large views and edit without issue. Is app running locally? What privs does the user have? Are they admin, owner, editor?

comment:3 Changed 5 years ago by Kim Neerings

See User was unable to save data once entered. He could enter the data, but when attempted to "save", the system timed out. Therefore, he had to send me the file in Excel so I could copy/paste in the backend DB.

comment:4 Changed 5 years ago by Kim Neerings

Milestone: UnassignedNeeds Analysis

comment:5 Changed 5 years ago by Kim Neerings

Milestone: Needs AnalysisUnassigned

comment:6 Changed 5 years ago by Garth Braithwaite

Milestone: UnassignedNeeds Analysis
Version: Unknown3.0

This issue likely goes away with 3.0 as editing datasets either within the DB enviro or XML will be broken down into more manageable chunks based on likely editing 1 series at a time etc.

Note: See TracTickets for help on using tickets.