Unanswered

SQL Get Rows with filter - Messed up output

(0) Share

Report

Posted on by Spångberg

Hi!

I'm using the action SQL Get rows (v2) to get a list of users from a data base view. To get only active users I added the filter query "Status eq 1". I thought that it worked as it should until i noticed that 3 users (of ~2500) was missing. To test I skipped the filter inside the action but added an array filter action with "@equals(item()?['Status'], 1)". Now I got all the users but strangely I got the exact same number of users in both scenarios. Further investigation showed that I had a couple of duplicates in the scenario with the filter inside "Get Rows" instead of my missing users. Can any one explain this behavior?

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Christopher S Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Spångberg

You can try by enabling pagination on the Get rows action in Flow, you can find this by clicking on the 3 dots and then settings:

On there, you can select the number of records that you can to retrieve with pagination:

Best Regards,

Was this reply helpful? Yes No
Spångberg 22 on at

Like (0)

Report
Copy link

Link copied!
Hi!

Pagination is already enabled and that seams to be part of the problem if it combines with filter.

If I disable pagination I don't get any duplicates (although I only get 2048 of 2276 records in the output).
If I enable pagination and filtering i get 6 duplicates (that does not exist in the SQL database).
If I enable pagination but filtering in a "Filter array action" it seams to work.
If I enabling pagination and filtering AND putting an unique value (like Email or EmployeeNo) in "Order by" it seams to work. A non unique value i "Order by" (like Status) generates duplicates.

So, the best workaround seams to be to put a unique value in "Order by' but the bug still annoys me...

Regards!
// Tomas

Was this reply helpful? Yes No