This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

weight data bugs

Former Member over 9 years ago

I am experiencing two serious problems with entering and viewing weight data.

1. I can only enter weight data on the smaller weight widget (for the current day only). I cannot enter weight data on the larger weight widget (for any day, using the calendar control). The save button shows a "not allowed" icon when I mouse over it and the button cannot be pressed. Why?!?!

2. My entire historical weight data has been shifted off by one day. For example, the weight for March 19th is now shown under March 18th...and this goes back many months into the past. I know this because I have paper records of my weight data.

A possible explanation for bug 2: I live in Germany where the week begins with Sunday instead of Monday. But I doubt that could cause all my data to be shifted for years of weight data.

This is very frustrating!!!

0 pshare over 9 years ago

For your #1, I just tried it and didn't have a problem. Is it possible a pop-up blocker or a setting in your browser is interfering? Perhaps try another browser.
For your #2, I doubt this would fix it but is your display timezone correct in Connect? Head& Shoulders icon - settings - display settings.

0 ASmugDill over 9 years ago

I am experiencing two serious problems with entering and viewing weight data.

OK … the first one is not a serious problem, because…

The save button shows a "not allowed" icon when I mouse over it and the button cannot be pressed.

… you simply need to select a date (or just click on the date field) after you enter the weight on the Weight page in Garmin Connect in your browser.

Why?!?!

Obviously someone decided that it's not a valid manual weight entry if the user does not select a date when using the Weight page, even though the field is already pre-populated with today's date. Is that program logic flawed? Yes, I'd say so.

I'm not saying it isn't an issue for the user, and I'm not saying it isn't a defect in the application, but as far as problems go, you can easily get around it and so it isn't serious. Obviously I encountered it myself as a user, and it stumped me for a while, but then I figured it out.

0 Former Member over 8 years ago

This does not work for me unfortunately.