I agree. Would be great if there is a way to exclude some fields in csv export. 

Hi everyone,

So, more recently I have found that it is very useful to have invisible fields that are not shown in visual format renderings but are rendered in CSV.

This is mainly due to the nature of the CSV rendering, as (potentially) so many columns are generated from the hierarchy with repeated data, that it would be difficult for an automated system to process the CSV accurately.

Unless the report is already rendering fields that clearly identify groups and detail rows, I found that an invisible textbox in the group header section with the Key/ID (typically the grouping value) for the group provides means to help identify distinct group fields.
Along with this, prefixing the names of textboxes for field values in group sections and those in the detail section consistently (e.g. "Group-{name}_*" and "Detail_*" (where "{name}" is the current grouping name)) makes it easy to identify distinct group and detail row values.

I am just now wondering if it would be a good idea if there was an optional(?) built-in feature to do this automatically in the CSV renderer - data keys and group names etc inserted in the export and fields prefixed. Otherwise in the meantime at least, something like a textbox/item naming tool that can batch rename/prefix by group and/or section.

While content with Visible=false being rendered in CSV would be good to keep in place, some other means of excluding content from CSV rendering (and any other data output format that is typically processed by computer systems) will still be beneficial. Without it, potentially many useless columns are rendered and file sizes can become uneccesarily large.

Hi Todor, I am facing the issue where textboxes with Visbile = false are displayed in csv exports. i believe its the same issue raised here. Do we have an update on this issue.