Forum Discussion
Finding Null Values to resolve an error
Hi IanDavies
Well done for working that out.
You could use the size attribute and set a minimum size:
Or on the Invoked Custom Function step before expanding the rows remove the error rows:
What do you think the solution should have been? Removing the errored tables before it was combined?
Sounds to me like you solved it, mark yourself as solution!
Hi IanDavies
Before you do this add columns step can you change the column [Name] and [DNSHostName] to TEXT.
This will let you sort, filter etc as the nulls will be convereted to blanks.
Beware when using the preview values at the top of the column, they are only based on the first 999 rows of data.
You could also add a Replace value step before doing your test:
Sam,
Thanks for the suggestions, Ive made some mental notes about the column formats, I hadnt spotted that and will update the table. Unfortunately on this occasion neither of your seuggestions worked. Even after changing the column types, I still got the error and I added a replace step but again I still got the error.
Knowing that this worked the last time the data was updated, I rolled back to the last known good state.
This table brings in all files in a folder using
= Folder.Files("filepath")
Having rolled back to a known good state, I introduced this weeks files one at a time. I found the one that caused the issue and established that it was empty. If there is a way in Power Query to manage an idiot putting an empty CSV files into the folder, please do let me know.
Thanks for responding and for pointing out the typing mismatch. I don't think its appropriate to mark it as a solution because it didn't work albeit another good trouble shooting step along the way.
