From SQL Executor, when Attributes are exposed and passed by FME they are automatically Alphabetized and the column/attribute order set is lost
In the case where SQL is used, Columns/Attributes should remain in the order they were set in the SQL statement
I have the same problem in FME 2018. A large list of attributes generated from an SQL query is sorted alphabetically in "Attributes to expose".
I would like to have them in the original order.
+8Adding the option to import attributes as a presorted list from excel would be a positive stop gap
Any progress on this issue (FMEENGINE-8759)? I'm writing out tables with 70+ fields and having to reorder the results is getting old.
I'm not convinced this should require a vote for popularity. I've never come across a product where you stick in a SQL statement and it outputs the results in alphabetical order.
I'd really class it as a bug.
I processed a 480 column table yesterday. No way would I touch FME for it. It would be impossible or so hugely irritating I'd throw my laptop out of the window :-)
I've been encountering this same issue and I'm convinced it's a bug.
I tried to work around this using a PythonCaller; I wrote a script that had a list of columns in the order I wanted, iterated through the feature and stored the column names from the list and their values in a dictionary, removed ALL the columns (so we're starting with a blank slate theoretically), iterated through the list I created and looked up the value for the column in the dictionary, then used feature.setFeature to add the attribute/value back into the feature. I would think this would now reflect the order of the columns as defined in the list, but it didn't. Features appeared in a random order (the same every time). I moved around the items in my list and got the same (wrong) order every time.
It seems FME decides what order columns should appear in based on something and doesn't let you change them.
+1Another vote for 'please fix'. I'm presently having to go through 61 attributes in an Attribute Manager to fix the order...
+4We're working on this now! When it's done, the status of this idea will be changed to Released, and we'll post a comment for which Beta you can find it in.
This will be a great enhancement. Note as a work around I paste in a list of comma separated attributes (in the desired order) into ”Attributes to Expose” , which the SQL transformers honour.
