The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Just checking if this is a known bug, If it isn't I'll investigate further or supply more details.
Here is what happens:
What is happening here???
Solved! Go to Solution.
Try adding a table.buffer() at the end of the query to cache the results
Try adding a table.buffer() at the end of the query to cache the results
Thanks @Deku , that did the trick!
Is this considered to be a work-around for a bug? And if so, has this bug already been reported?
Not a bug, just how PowerQuery is implemented
Hi @Keezz ,
we wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
If our response has addressed your query, please accept it as a solution so that other community members can find it easily.
@v-aatheeque , you are a bit impatient, aren't you? I happen to have other duties beside Power Query work, so I hadn't had the opportunity to review...
If it is not the first time to load into the table, the data will be sorted according to the settings on the table after loading.
If it is the first time to load, or the keep sort option of the table is turned off, it should be in the order displayed in the Power Query interface.
If none of the above conditions are met, this may be a bug. However, it is not ruled out that some operations may be optimized by Power Query, resulting in different displays in Power Query and Excel.
Hi @ZhangKun thanks, but I had already tried that. I removed the table and even removed the columns of the worksheet where the table used to be. After editing the load-to and re-creating the table, same problem!