Yeah. I had to do this to get the dates in the right order. There's no guarantee the keys will be sorted how I want them to be. If I had done 2017 11 Nov it'd be okay, and the items would stay in the right order. The other option is to do an array, since arrays can be any order. I was working on adjusting it. That said, the re-loop add milliseconds, so I didn't see the actual harm in looping again.
Howdy. Your idea of setting each possible x-axis to 0 and then later updating it is a great idea. I took that and turned it into a JSON object where the key is "2017 Nov" and the value, to start is 0. My version of the script uses your basic look. I updated each value from 0 to the correct summary value, using your great method of the fast summaries (which I have just recently learned). I then had to create the $x and the $y by looping again through the possible dates and extracting the value from the key. Take a look. It's the "GatherData" script. Since charts need all possible axis points, I would usually recommend a summary table to run and add a record for 2018 Mar even if the amount is 0. But the JSON object is a good substitute, especially using the (amazing) fast summaries method. Inspections_JSON.fmp12