Allow users to sort edited columns in export definitions.
This is useful because the column order is reflected in the CSV file. For example when editing an export definition, the edited fields show up at the bottom of the export definition and appear out of order, no matter how they are sorted ie. if you have an export definition with the constituency field mapped at 10 columns, save the export definition and add the date to field the definition all of the date to fields appear at the bottom and appear out of order, no matter how the constituencies are sorted.
-
Guest
- Oct 10 2016
- Reviewed: Voting Open
| Organization Name (Please enter full organization name) | Simon Fraser University |
| Reported Version | 4.0 |
Related ideas
This can be a weird one to wrap your head around. Essentially what we've found is that when you go into edit an existing export definition by adding a field that can have multiple results (eg: Groups Belonging To, Educational History/Degree, etc.) and you export this to multiple columns and set a filter to order these in Ascending or Descending order based on date or name, the definition somehow ignores this filter and adds the columns in the wrong order. You then risk carpal tunnel arrow clicking each column up or down in the column order window to put your export into the correct column order. The problem is even worse with custom table data. A consistent, functioning filter on exported fields would be a huge time saver.