In single row queries, we are given the option to choose our own headers, just like in database view. Imagine my shock when the headers in the file I exported from my new single row query did not match those I entered in my headers. Instaed, all of my columns headers had underscores in place of the spaces which I had entered in my headers.

This is incredibly frustrating for multiple reasons:

1. I was given the option to name the columns and expected the export file names to match the column headers I was allowed to enter (this is how it works in database view).

2. There was no warning that any spaces would be replaced by underscores.

3. This creates extra work for anyone who needs file headers to exactly match something and include a space, either we have to go in and manually remove underscores from all headers and replace them with spaces or we have to update processes to reflect this change in functionality.

It would be ideal if the system stopped replacing spaces with underscores and generate a file with headers named exactly as the user enters in the single row query setup including any spaces the user may include in the header. Alternately, if spaces are not going to be exported by the sytem, then remove the option to enter spaces in the column headings.

Screenshot 2026...

Screenshot 2026...

Attachments Open full size