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
{{ message }}
This repository was archived by the owner on Nov 7, 2024. It is now read-only.
This worked as expected for small data sets, but for a large longitudinal data set (aprox 5,000 records), there were some error messages that may be confusing to the user. When creating a report count from a report that did not include a filter on events, the first screenshot displayed with this message "The selected report has no radio button or drop-down fields to group by." though the report does contain a radio button field. However, the user is able to save it, at which point the second screenshot displayed shows up allowing you to select the field to group by. After filling that out, the message in the third screenshot appears "An error occurred while trying to save this count." This issue can be fixed on the user end by optimizing the report so that it does not include the data for unneeded events, but this may not be immediately obvious to the user based on the error messages. Could something be added to make this more clear to the user?
This worked as expected for small data sets, but for a large longitudinal data set (aprox 5,000 records), there were some error messages that may be confusing to the user. When creating a report count from a report that did not include a filter on events, the first screenshot displayed with this message "The selected report has no radio button or drop-down fields to group by." though the report does contain a radio button field. However, the user is able to save it, at which point the second screenshot displayed shows up allowing you to select the field to group by. After filling that out, the message in the third screenshot appears "An error occurred while trying to save this count." This issue can be fixed on the user end by optimizing the report so that it does not include the data for unneeded events, but this may not be immediately obvious to the user based on the error messages. Could something be added to make this more clear to the user?