I was just informed by my users that a UX, that's used every day, without issue, slows to a crawl (causing data entry errors) after more than 9 or 10 rows are added to the Repeating Section. The slowdown impacts the data entry and the "save/submit" process.
Here's some background information that might help:
I can't think of any reason why adding 15-20 rows in the Repeating Section would cause such a dramatic slowdown for the user OR any settings that I might be able to adjust in order to prevent this from happening.
If you have any thoughts or ideas, I'd love to hear them. Perhaps, I'm missing something basic.
Phil
Here's some background information that might help:
- Typically, during data entry, the user will enter only 1-6 items in the Repeating Section (no slowdown or other issues). Because this is a "Customer Quote" form, occasionally, the quotes (e.g. the Repeating Section items) can become quite large (I've seen a couple of quotes with 20-25 lines);
- The Repeating Section has several fields and is quite complex... That might be part of the problem (see the image below, showing the entries for only 2 Repeating Section records);
- When submitting the data, the back-end table is a SQL Server table. The SQL Server database is on a VERY fast server, with lots of bandwidth... I don't have any other "speed" issues (at least, none that anyone has told me about). AND... the table that holds that Repeating Section data has only 7,300 records (after 2 1/2 years in production), so it's not a huge table;
I can't think of any reason why adding 15-20 rows in the Repeating Section would cause such a dramatic slowdown for the user OR any settings that I might be able to adjust in order to prevent this from happening.
If you have any thoughts or ideas, I'd love to hear them. Perhaps, I'm missing something basic.
Phil
Comment