Currently, when selecting "ALL" in certain features, the system silently truncates and caps the data at a maximum of 500 records without throwing any notification, warning, or banner. From a user perspective, selecting "ALL" implies viewing or processing the complete dataset. Because this truncation happens silently, it can be highly misleading and lead to incorrect data analysis or incomplete reporting.
The solution I would like
- Warning Message / Banner: Implement a clear visual indicator (a warning banner or tooltip message) whenever a selection is capped by this 500-record limit, explicitly letting the user know that the data has been truncated.
- Lift the Limit: Ideally, provide a way to configurationally lift or expand this 500-record constraint for specific high-volume use cases.
Alternative solutions considered: Documenting it in the Knowledge Base (KB) helps, but an in-app UI warning is critical to prevent silent data issues during active development and analysis.
