1
Export Drawer UX
Source: directus/directus#24916 · opened by @connorwinston
Describe the Bug
The Export Drawer's UX in the Data Studio, does not match the functionality of the actual service. The Export Drawer uses the API's Export Query Parameter which converts a JSON API response to a JSON, CSV, XML, or YAML file. This means that the export can not have duplicate keys, the order of the keys is not preserved, only top-level fields of the item are columns, etc. The way this is currently designed does not reflect those requirements from the field/column selection interface.
Directus Version
v10
The Export Drawer's UX in the Data Studio, does not match the functionality of the actual service. The Export Drawer uses the API's Export Query Parameter which converts a JSON API response to a JSON, CSV, XML, or YAML file. This means that the export can not have duplicate keys, the order of the keys is not preserved, only top-level fields of the item are columns, etc. The way this is currently designed does not reflect those requirements from the field/column selection interface.
Directus Version
v10
No pledges yet. Be the first to back this.
Comments
Similar requests
Implement 'Save All' Functionality for Nested Collections in Relation Drawer
3 votes · 0 comments
Add a button to switch "select item" drawer to a "create item" drawer for better user friendliness
1 vote · 0 comments
Add “Per Page Limit” option to Notifications Drawer
1 vote · 0 comments
Move Extension Settings to drawer trigggered by settings icon
1 vote · 0 comments
m2m: option to hide relational item in drawer
12 votes · 0 comments
No comments yet.