Unusual behavior from Table.FirstN

[Porkey]

Hello,

Im getting unusual behaviour from the Table.FirstN function please see image below, does nyone have any idea why

The source is from sharepoint, which is the same as the other queries in the file which are all fine.

Filter to find the filename in a library

Sortby Descending created date

All im doing with the function is getting the most recent created file with a specific name.

The files in the library actually date back to Aug 2022, but November is showing . Ive had a little play around with no success but when i dont include the sort by it gives the first and sixth row instead of the first and fifth which it does wth the sort by.

Any idea would be appreciated

I have tried an older version of the file that was previously fine, same thing happens.

I have restrated the pc

I have logged in and out of microsoft.

This does not happen on all the queries i have on other workbooks or in powerBI.

I had the same issue on one other sheet about a month ago. Which i just rebuilt to resolve, but i dont wan to have to do that everytime.

Thanks

[artemus]

I belive this is a known bug where doing a first N with 1 on some data sets that only have 1 value could return 2 results. You can try the following workarounds:

1. Get the first row of the table as a record with #"Previous step name"{0}?

2. Add the step before: Table.StopFolding(#"Previous Step")