Currently the data used for the dashboard view is stored using annotations. It is stored as a dict and to update a row the whole dictionary has to be loaded, adapted and then stored again.
This is not a good solution for more than one reason. The first one is that if two users are working in the dashboard they will overwrite each others changes (all of it) while this would be a lot less if it would only change one record each time. The second reason is that it will get very slow if there is a lot of data. I tested with around 30'000 rows and this became really slow.
Currently the data used for the dashboard view is stored using annotations. It is stored as a
dictand to update a row the whole dictionary has to be loaded, adapted and then stored again.This is not a good solution for more than one reason. The first one is that if two users are working in the dashboard they will overwrite each others changes (all of it) while this would be a lot less if it would only change one record each time. The second reason is that it will get very slow if there is a lot of data. I tested with around 30'000 rows and this became really slow.