Problem
Two small polish items came up while testing "Export current view":
1. Inconsistent export filenames
The downloaded filename differs depending on which export flow is taken:
- Small set / immediate download →
Expensify-2026-06-19 09_30_51.006.csv
- When prompted to wait or send via Concierge (even when choosing to wait) →
search_export_6a350c7b2fa9e9.03383144.csv
We should standardize on a single filename format regardless of the export flow.
Decisions from discussion:
- Drop the date and time from the filename — the OS already records the download timestamp, and existing Classic/NewDot exports use arbitrary, inconsistent date formats anyway.
- Keep a unique ID so Concierge-delivered files don't collide.
- Proposed format:
Expensify_<Current_View>_<unique id>.csv
2. Redundant export option name
In the UI the option reads "Export current view", but the user has already clicked Export to reach it, so the leading "Export" is redundant.
- Rename the option to "Current view".
Solution
- Update the export option label from "Export current view" → "Current view".
- Standardize the exported filename across all export flows (immediate download and Concierge delivery) to
Expensify_<Current_View>_<unique id>.csv.
Reported in Slack.
Issue Owner
Current Issue Owner: @mallenexpensify
Problem
Two small polish items came up while testing "Export current view":
1. Inconsistent export filenames
The downloaded filename differs depending on which export flow is taken:
Expensify-2026-06-19 09_30_51.006.csvsearch_export_6a350c7b2fa9e9.03383144.csvWe should standardize on a single filename format regardless of the export flow.
Decisions from discussion:
Expensify_<Current_View>_<unique id>.csv2. Redundant export option name
In the UI the option reads "Export current view", but the user has already clicked Export to reach it, so the leading "Export" is redundant.
Solution
Expensify_<Current_View>_<unique id>.csv.Reported in Slack.
Issue Owner
Current Issue Owner: @mallenexpensify