Hi, Becca 

We got confirmation on this.

Our developers are going to work on fixing this behaviour as soon as possible - i can't say an exact ETA, but they will do their best to make a fix in one of the future updates.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

For the time being, the only workaround to avoid the issue, will be, to change the Origin header Name ( to be without non alfa numerics;  and then add the full name as Displayed Header);

For example, when we use SQL Tables;

you can use an alias for any column that has non alfa-numeric characters;

I made a little Test Table, just to test one column :

Then i make a Query for this column, like this :

And, we got a working result .

(of course, you can use any alias Origin Header name, as long as you avoid non-alfa numeric characters > which you can then change manually for the Displayed Header Name.)

-

-

Let me know if all that makes sense, and if it can work as temporary solution - until the devs make a fix.

Thank you