Exports should have an option to export the current columns #9758
Replies: 2 comments 1 reply
-
agree with this one.. example.
|
Beta Was this translation helpful? Give feedback.
-
Just wondering if there are any plans to look at this for Craft 5+? Appreciate there are probably some complex technical barriers here. |
Beta Was this translation helpful? Give feedback.
-
We have a few clients that want to export items from entries, orders and some other custom elements, but they're getting confused by the output not being what they expect.
From a client point of view, they're expecting the export to contain just the columns they're currently viewing in their control panel. Now granted, the default exports contain columns for every custom field available on the system and every attribute on the element, and some might think that useful - more is better than less. And the client can certainly go through and pick-and-choose the columns to keep, but that's pretty tedious on a system with lots of custom fields.
I'll mention that of course we can create a custom bit of code to add a new type of export to handle this scenario (particularly for third-party plugins), but feel like maybe it should be the default export behaviour? Even if it's a breaking change?
Related, but is there much point - other than performance - for Raw and Expanded? There's columns in the default exports like
fieldLayoutId
,newParentId
,deletedWithEntryType
,tempId
,draftId
,contentId
, etc - all of which are pretty unnecessary. These two exports seem pretty identical otherwise.What I might propose is to have 2 exports, both of which are different to the current.
So maybe something to consider or discuss?
Beta Was this translation helpful? Give feedback.
All reactions