I am in the process of getting some testing protocols drawn up, to load in the Guides/Help section - a closed topic, so that the process to test is clear for everyone to see.
AlphaHRV is one of these protocols, but I first need to test and understand it myself. Anyone with questions can then use the general discussion to ask. This way the information is in one place, and the important information isn’t lost among the general chit-chat.
I do have some pending work to update the description (text and images) in Connect IQ store for alphaHRV
I can imagine you are quite busy at the moment
I know support for this has ceased but I still use the Intervals_API_Tools_Office365_v1.5 excel sheet regularly enough. Today I refreshed it to find my Training Advice but the sheet produced an error as seen below.
Column ‘AI’ of the Wellness tab of the excel sheet is ‘rampRate’
Has this field been removed from Intervals.icu or something? Why can the sheet not find this field anymore?
@david @MedTechCD Any ideas why ‘rampRate’ column is no longer found? Did an update to the site code break this sheet? It was working a couple of days ago without issue.
Thanks
I’m still using it and had no problems this morning.
Verified the Wellness tab and rampRate came in normally but in my case it is now column AN. It moved up right because other columns got inserted. Today, column ‘locked’ was added by the new functionality to lock Wellness data.
Did you make any changes to the original sheet that address columns by fixed column location? The sheet was made with all references to Column Names, not Column location. If you did not change anything, it should work, but if you somewhere made a change or addition addressing column AI, that would brake it.
That’s really strange so. I never changed anything on the excel sheet. I will try again now.
Edit:. Still getting same error. I will go back and find original template and see if that works for me.
I’m using my original file, which is not the Intervals_API_Tools_Office365_v1.5 version.
Mine works fine too.
On the Data tab, if you click on Queries and Connections it will/should open the Task Pane Options to the right. Hover your mouse over the Wellness data (don’t click) and it will the following:
Then click on EDIT to open the Power Query Editor
From here you can check if the RampRate shows, and possibly troubleshoot.
Thanks. I was also using v1.5
Went back to the Google Drive link and downloaded v 1.6 and getting same error
I will do what you suggested now @Gerald and see what I come up with
I’ll download v1.6 and see if it replicates your problem.
I got the same error on v1.6
I’ll spend time later today troubleshooting.
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.
Just got your PM. It will be tomorrow before I can check. Thanks for your help. Much appreciated
That worked! Thank you.
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.
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.
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
