This is what I’m getting
I got the same error on v1.6
I’ll spend time later today troubleshooting.
1 Like
Thanks! I wouldn’t even know where to begin.
Let me know if the solution by PM resolves your issue, then I can share the solution here.
1 Like
Just got your PM. It will be tomorrow before I can check. Thanks for your help. Much appreciated
That worked! Thank you.
1 Like
In the setup, the number of columns needs to match the number of columns from the Wellness data. This can be checked by changing the value (highlighted) to 50. In the below example, there are 44 columns, which is why the rampRate would show as an error; it’s the first column after the value showing when using v1.6.
3 Likes
You actually don’t need that ‘Columns’ parameter and I don’t know why it remained in the shared file. I must have forgotten about it after experimenting…
My local version just has this:
And it will always automatically extend when new parameters are added. But types will not be assigned correctly.
Since the last file update, there are 5 added fields in the wellness csv (steps, bedTime, wakeUpTime, respiration and locked). I will prepare a version 1.7 to take them in account and post an update here when it is available.
1 Like
My own version also doesn’t have that showing, which is why I also didn’t have a problem with the addition of the extra data.
Thanks @Gerald and @MedTechCD for solving this, and also @nasatt, for flagging the issue. I had the same problem, since around 22 March.
I struggled and could only solve this by modifying PowerQuery and getting rid of reading in a few columns (rampRate, atlLoad and ctlLoad) but then of course information needed for some of the charts was missing. I was not aware and completely missed the Columns parameter in the source description in PowerQuery. Luckily you guys are great at this.
Thanks again,
Marc
1 Like