POwer query resorting row position in final output

[Bazbuyer]

I have a query which looks at a excel spreadsheet A which is updated daily with new lines of data. The query in another workbook B looks through that data and pull in any new rows. It removes a couple of columns and filters for jurisdiction UK. Yesterday B at 84 rows. Today another UK item was added to A. When I go into the query editor this now shows as row 85 - where I'd expect it. Yet in B where the results show its inserted itself into row 67. This is critical as outside of the table I have formula based on what is inside the table on that row. Any ideas why this would do this? Why the query editor ifno should be different to the final output?

[AliGW]

There are instructions at the top of the page explaining how to attach your sample workbook.

[Bazbuyer]

thanks, unfortunately I cant attach the workbooks as I'm doing this from work and firewalls, protocols etc prevent me from doing so. However, I'm not sure how much it would help. When I view in the editor or close and load in the query screen/preview the new data is at row 85. When I go into the specific worksheet in the workbook at loads/inserts to row 65 (which is row 67 on the page), rather than row 85 as you would expect

[Shareez Saleem]

Remove the step Sorted Rows

[Bazbuyer]

thanks but there isn't a sorted row step. I've just looked at the connections properties (all refresh is disabled - the refresh is called by a macro on opening this workbook) Connections("Query - Central to Raw Upload").Refresh
Looking at the properties I have in data formatting and layout adjust column width and preserve cell formatting ticked (should I have preserve column sort/filter/layout ticked?) also ticked is 'insert cells for new data, delete unused cells', should I have insert entire rows for new data, clear unused cells'?.

[Bazbuyer]

I've soled this by adding an index at the end of the query then when the results are output to the worksheet running a sort on the index column. From what I could find on the web this may relate to some sort of memory optimization that group certain records that are similar, though I couldnt see the similarity myself