You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The related problem is about the limitation of managing until 10,000 entities in two situations: CSV Export and Map View.
Describe the solution you'd like
Meanwhile these limitations are fixed, it would be usseful tu add a warning to the user, in two scenaries:
CSV Export: if the selected filter to be exported overcomes 10,000 entities, before creating the CSV file, to show a message warning that the file will include only the first 10k entities.
Map View: if the selected filter overcomes mora than 10k entities with geolocation, to show a message warning that the map only show 10k point.
Have you considered an alternative?
Hopefully, the best way to fix this is to avoid limitations with data export and geolocation views.
The text was updated successfully, but these errors were encountered:
After some discussions, we are going to try to:
a. Strip the data sent by the "geolocation" endpoint to only geolocation properties
b. try to use the same "pagination" approach as we are developing for the CSV export
c. have the client attempt to deal with all the geolocation data
We will evaluate how much impact this has on the client's machine.
Is your feature request related to a problem? Please describe.
The related problem is about the limitation of managing until 10,000 entities in two situations: CSV Export and Map View.
Describe the solution you'd like
Meanwhile these limitations are fixed, it would be usseful tu add a warning to the user, in two scenaries:
Have you considered an alternative?
Hopefully, the best way to fix this is to avoid limitations with data export and geolocation views.
The text was updated successfully, but these errors were encountered: