Fields Order troubles

[Anonymous]

Hello,

In a POC I have 2 small tables, in PowerQuery they are just the same script except 1 filter (one goes on 1, another on 2).

They both have a ReorderColumns in it.

But, in PowerBI Table sthe field order is different and when union a UNION this goes bananas.

[ImkeF]

Why not append in the query editor instead ? (there the order of the columns doesn't matter, so you could even skip those steps):

Haven't come across this behaviour before, but maybe a

Table.Buffer(NameOfYourPreviousStep)

as the last step would help:

[Anonymous]

It was in a first test to create 2 separate filters on the same table, but this approach didn't work out. But I had never had something like that before.

Appending wasn't good, I was trying to UNION the selected rows in both tables, but with the very strage effect ...

Thx 

[v-piga-msft]

Hi @Anonymous,

I have made a test with creating the script in Query Editor try to reproduce your issue, but both of my two tables have the same oder in Data View as that in Query Editor. 

Besides, by my test, it seems that there is no option for us to change the filed order in Data View.  I also have tested that when I rearranged the column order in Query Editor then Close && Apply, the order will not update in Data View.

If it is convenient, you could share a dummy pbix file which can reproduce the issue, so that I can test in my environment? You can upload it to OneDrive or Dropbox and post the link here. Do mask sensitive data before uploading.)

Best Regards,

Cherry

[Anonymous]

Hope this works ... OneDrive

We only have OneDriveProfessional

[v-piga-msft · Accepted solution]

Hi @Anonymous,

I have made a test with your data sample in my site Power BI Desktop (Version: 2.58.5103.501 64-bit (May 2018)), everything works as expected.

You could try to copy my query in Advanced Editor and change the data source. 

I have attached the test file below, you could have a reference.

Best Regards,

Cherry

[Anonymous]

I just started over with a the same file renamed, modified both queries in advanced query to the new filename, reloaded and it came correct.

But this was definitly PBI going bananas ...