Export query results to CSV - bug or different behaviour

RLJB

V6 introduces different behaviour (and probably worse behaviour) than what previously existed.

This refers to when you have a query and you hit the little icon on the top right of the grid to "Export query results to CSV"

Prior Versions:

It would export ALL fields, regardless of if they were 'Hide column initially' or 'Show column initially'

Version 6 (build 2020):

It will only export fields if they are 'Show column initially'

This is not as useful, because to allow a user to export a field, you MUST have it 'Show column initially' - so to give them lots of options you have to have a messy user interface with lots of columns.

Is this is a bug? Any chance of having it go back to the old way?

hpl123

I actually think this is a good new option or rather I think the option to select which attributes to be included in CSV export is good. Hope this can be included instead.

RLJB

Yes, agree, the ability for the configurer to choose the items available for export would be good, but not really needed. If you have made it available for the user to see, then they should be able to export, that is a given I would think. (And not how it currently works)

hpl123

RLJB wrote
Yes, agree, the ability for the configurer to choose the items available for export would be good, but not really needed. If you have made it available for the user to see, then they should be able to export, that is a given I would think. (And not how it currently works)

Well, not necessarily. I often use different columns/attributes shown only when a condition is met meaning if I had all columns in an export that would not work. This is the main reason I don´t use the export functionality today.

RLJB

Yes, but that's a different issue. I'm not referring above to the use of the conditional display rules. Above is the fact that the behaviour of this export has changed between versions (for situations where no conditional display rules are applied).

I'm not sure what happens when you apply conditional display rules, you may want to check it out in v6 as the behavior might have changed.

RLJB

Hi Support

Any opinion about this new behaviour, is it considered a bug that will be fixed in future versions?

Tks.

aware_support

The change was intentional - it gives people flexibility to influence which attributes should be exported. You set visibility of the attributes you want to export and then it will only export those that are currently visible.

Note, it does NOT export attributes shown initially - it exports attributes CURRENTLY visible. The user can turn column visibility on and off.

RLJB

Hi Support...

it does NOT export attributes shown initially - it exports attributes CURRENTLY visible. The user can turn column visibility on and off.

...it doesn't work that way (build 2023), it currently exports 'shown initially', not currently visible. Will send you a bsv. Tks.