Workout with both Power and Cadence target

Totally agree.
Does anyone can suggest any fields on IQ store to get around the problem?

Garmin Connect supports primary and secondary targets for custom workouts:  

Based on my user experience, Garmin Connect does support primary and secondary targets when creating custom workouts, however, the secondary target is not displayed in the Workout screen on the Edge 830.

If, for example, you select Power as your primary target and Cadence as your secondary target only the Power target range is displayed at the top of the Workout screen with (usually, but not always) a real time power graph in the screen space below the primary target.

I have created custom workouts in both the Garmin Connect PC version and mobile app and neither result in the secondary target being displayed on my Edge 830 Workout screen - instead, a real time power graph or, alternatively, the lap time is displayed below the primary target (in my case, Power).

So yes, you have the capability to create a secondary target in Garmin Connect for custom workouts, but it does not display on the dedicated Workout screen (or, at least, I haven't found a way to get it to work).

pcrowder straight to the point, you’re 100% right.

Hi Former Member

Can the FIT fields for the secondary targets which are "secondary_target_type",  "secondary_custom_target_value_low" and "secondary_custom_target_value_high"  (and maybe some more) be documented in FIT SDK documentation https://developer.garmin.com/fit/file-types/workout/ They are missing there.

It is very frustrating that 3rd party providers are not integrating secondary targets when workouts are synced with garmin edge 1040/840/540 that support secondary targets.

Here is the ticket for trainingpeaks to set the secondary targets
https://peaksware.uservoice.com/forums/106657-trainingpeaks-customer-feedback/suggestions/46307749-training-peaks-bug-workout-goals-are-populated-in  . There was a note for Garmin Product Team: with incident # 469564 

It does not help that Garmin do not have the fields documented in the FIT SDK. 

Hi,

I was after the exact same thing, and in the end,I ended up writting my own data field for the Edge devices to do exactly this.

It displays both the primary and secondary targets, and displays both the current values and the average values for current step.

Along with this, it also shows you what the next step is, so you can be ready for the next effort.

The only thing is, that because Garmin have not provided the secondary step information in the API, you do have to add a short entry in the notes field of the step to describe the secondary objective. (i.e. Sec:0080:0100:RPM )

As you have to add text to the workout notes, I don't think it will work with workouts that are sync'd via other apps such as Training Peaks, but works perfectly well with workouts created in Garmin Connect.

Please try the 'Training Edge' data field that you can install from Connect IQ Store. Make sure you read all of the description to understand the syntax to use when adding the step info to the notes section.

https://apps.garmin.com/en-US/apps/e0a4c637-e1a0-4135-a1a9-48fe7b24f0a5

Hopefully this will provide what you are looking for.

Dave

good work on the app data field.

reverse engineering the workout files from garmin connect, and extracting the fit file from the edge device filesystem in workouts folder and passed through fitfileviewer/FitCSVTool gives some idea... I saw how the fields "secondary_target_type",  "secondary_target_value", "secondary_custom_target_value_low" and "secondary_custom_target_value_high" are used.  But obviously having a published API would be better.

This would be useful for the non edge 540/840/1040 where secondary targets are not displayed in default workout screen.

Hi Former Member if you cant answer this, can you direct me who to contact to get the secondary targets documented publicly in the Garmin Fit SDK

This thread is in the Edge 830 forum, the x30 devices do not support secondary targets. Unfortunately the training peaks file only sends over the primary target.