CiviCRM Community Forums (archive)

We do a lot of exporting, and the leftover CSV files can be a data protection issue. It'd be great if Civi could optionally show exports in an HTML table, rather than generating a file. These could then be copied/pasted into Excel / whatever (Excel at least does a pretty good job of handling copy/pasted html tables).

Plus it'd be a bit quicker. I regularly need a quick list of Civi IDs or something to vlookup against, and this would save a few clicks.

Just a thought :-)

Search views are ok, but we do quite a few bespoke exports where we select the columns we need as we export. So we'd end up with dozens of one-time-only search views. Plus there's no easy flow into the search view setup, unlike the export process - and creating a profile is much more time-consuming than selecting the fields on export.

Also there's a lot of surrounding html that prevents easily highlighting of columns you want - the 'View', 'Edit', 'more', and the checkboxes. Search views also can't be used in Membership/Contribution/etc. searches.

Plus when we do use mappings they'd inevitably overlap - sometimes I do need a CSV file of names and emails, say, and it seems inefficient to create search views and export mappings of the same thing.