Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Microsoft Excel and other applications generally have poor support for date times represented in ISO 8601, or even with any timezone suffix at all. Because CSV export is predominantly targeted towards users who will analyze the data in applications of that sort (As the API exists for more programatic usage where ISO 8601 would be more conventional), this removes the timezone from the date times in CSV export and formats them in a standard YYYY-MM-DD format using the configured timezone.
For consistency and data completeness this also adds a column including the timezone the dates are rendered in.
Checklist
Demo
Notes
.get()
with the intention of streamlining the logic and marginally improve performanceTesting Instructions
YYYY-MM-DD HH:MM:SS
, without timezone suffixhttp://localhost:7000/#!/record/{Record UUID}/details
Closes PT164776646