While adjusting the date range for the example export in #5, I encountered a client-side error when attempting to manually set the date range. Specifically, when entering the year, upon the first keystroke (e.g., "2" when entering "2025"), a client-side exception is immediately thrown. Presumably, it is not waiting for the entire year to be entered before attempting to repopulate the date table and it isn't a fan of the year 2 AD.
Steps to replicate issue:
- Select the year portion of the end date:
- Press the number "2" on the keyboard
While adjusting the date range for the example export in #5, I encountered a client-side error when attempting to manually set the date range. Specifically, when entering the year, upon the first keystroke (e.g., "2" when entering "2025"), a client-side exception is immediately thrown. Presumably, it is not waiting for the entire year to be entered before attempting to repopulate the date table and it isn't a fan of the year 2 AD.
Steps to replicate issue: