Turns out my 11-yo daughter has developed a love of disaster movies. Go figure?
Author Archives: Phil
Volcanologist Harry Dalton comes to the sleepy town of Dante's Peak to investigate the recent rumblings of the dormant volcano the burg is named for. Before long, his worst fears are realized when a massive eruption hits, and immediately, Harry, the mayor and the townspeople find themselves fighting for their lives amid a catastrophic nightmare.

This review may contain spoilers.
Watched it with the kids (11/14). Had to preface that the dog doesn’t die but Grandma does. Aside from the close up on the gnarly compound fracture, all good!
★★★ (contains spoilers)
In Depression-era West Virginia, a serial-killing preacher hunts two young children who know the whereabouts of a stash of money.
Yeah, I agree, what he said.
When you want to make friends but get told off…
The scientist father of a teenage girl and boy accidentally shrinks his and two other neighborhood teens to the size of insects. Now the teens must fight diminutive dangers as the father searches for them.
A packed cruise ship traveling the Atlantic is hit and overturned by a massive wave, compelling the passengers to begin a dramatic fight for their lives.
Shout out to all the people that complained about Google
Well, that’s interesting!
PowerQuery vs. JSON null or empty list
I had an interesting problem recently when the JSON output from an API started to return a null value instead of empty list. This broke my PowerQuery so I wanted to share a fix.
Originally, I used the built-in “Extract values (from a list)” feature, which concatenated them to make comma separated values:
= Table.TransformColumns(#"Removed Columns", {"List_Field", each Text.Combine(List.Transform(_, Text.From), ","), type text})
And that worked fine. Until the content of that field was not a list. Evidently, this field had previously contained an empty JSON list if it contained no values. I’ve never looked at the JSON itself so I had no idea. So, when the API started returning null for that field instead List.Transform failed:
Expression.Error: We cannot convert the value null to type List.
In some of my other Queries it was also failing “silently” because this step was immediately followed by a RemoveRowsWithErrors step. Whoops. Having no idea that the API output had changed (or what it originally contained) was my big problem here. Took me a while to understand what had gone wrong and how.
The fix itself isn’t complex, simply check if the value is a list before concatenation:
= Table.TransformColumns(#"Removed Columns", {"List_Field", each if Value.Is(_, type list) then Text.Combine(List.Transform(_, Text.From), ",") else null, type text})
However, that DOES make me wonder why the built-in doesn’t automatically add code to check the type. Can’t be that hard…



