Forum Discussion
Error When Using Power Query to Restrict Data
Hello v-janeyg-msft,
It works now. The error refers to the calmonth field which is numeric and there is no null value for that field so it is odd when it refers to such error.
What I did was, I used August release (because latest release has a bug and I can't refresh). Then I select the field and choose 'keep errors'. It will generate a new step.
#"Filtered Rows" = Table.SelectRows(Table,
each ([calmonth] = List.Max(Table[calmonth]) or [calmonth] = List.Max(Table[calmonth])-1)),
#"Kept Errors" = Table.SelectRowsWithErrors(#"Filtered Rows")
in
#"Kept Errors"Then I 'apply' and it got refreshed. The first refresh was successful but the table was empty, so I tried few times until it gets populated.
After that I removed the ‘keep errors’ option and refresh again. Seems like it works fine now.
Mimi_Ibrahim Any updates?
Did I answer your question ? Please mark my reply as solution. Thank you very much.
If problem still persists, pls let me know.
Best Regards,
Community Support Team _ Janey
Hello v-janeyg-msft,
It works now. The error refers to the calmonth field which is numeric and there is no null value for that field so it is odd when it refers to such error.
What I did was, I used August release (because latest release has a bug and I can't refresh). Then I select the field and choose 'keep errors'. It will generate a new step.
#"Filtered Rows" = Table.SelectRows(Table,
each ([calmonth] = List.Max(Table[calmonth]) or [calmonth] = List.Max(Table[calmonth])-1)),
#"Kept Errors" = Table.SelectRowsWithErrors(#"Filtered Rows")
in
#"Kept Errors"
Then I 'apply' and it got refreshed. The first refresh was successful but the table was empty, so I tried few times until it gets populated.
After that I removed the ‘keep errors’ option and refresh again. Seems like it works fine now.