It's fair enough to make a comment on the forums about something you don't like but please refrain from swearing.
Constructive feedback is welcome. Look at the Ideas section if you want to suggest alternatives.
Thank you for your comment.
1- Usually, tableau provides improvements together with new versions. Honestly, the new data connector is nothing else than a step back.
2- My proposal is very simple: get an alternative for writing text queries and bypass the SQL query graphical constructors.
There have been previous forum suggestions to allow renaming to be turned off. There was some interesting comments on this post (In 8.2 - how do I stop Tableau from renaming all my fields?) which suggests it's possible.
You can use Custom SQL. When I tested this it did not rename the fields I was using (from an Oracle database). Note that if you use custom SQL you miss out on the ways Tableau has for generating SQL against your database. If you join the database tables in Tableau, then tableau will generate efficient SQL against your database. With custom SQL it has less opportunity to do this.
Thank you for the reference to the other post. At least, I am not the only one frustrated with the 'we know best' approach :-)
I guess my issue is the opposite. I like the renamed fields, but just from yesterday I am having the issue where it is changing names to a few fields and not others. Yesterday AM, the fields had spaces "Customer Id" now today I am seeing "Customer_ID". Tableau is showing an error in locating these fields because of the name change today. I am connected to a Live data source, and have not encountered this issue before. Seems like I have to reference all the names and then rename them without the Underscore.
It happened with me as well.
I just dragged out the table/custom SQL from edit data source window and dragged in again.
It renamed column headers with spaces (removing underscore).
I hope this helps!