Acknowledged

Please allow nativeNum FIT fields to override native fields in Garmin Connect

Currently, nativeNum fields do not override native fields in Garmin Connect, which seems to defeat the purpose. This prevents apps from overriding distance, speed or power, for example.

This feature has been requested for several years:

[https://forums.garmin.com/developer/connect-iq/f/discussion/4854/fitcontributor-nativenum-functionality]

Parents
  • To be clear, this feature request is only asking Garmin to alow nativeNum fields written by CIQ apps to be treated just like native data in Connect (and to override any native data that's be written to the same FIT file).

    It is *not* asking Garmin to make it so that when a CIQ uses the nativeNum option, it actually writes the data to the FIT file exactly like native data. The reason I didn't ask for that is because I am 100% sure Garmin would never do that.

    Yeah, if CIQ data fields could actually write *literal native data* to the FIT file (and prevent the same native data from being written by the activity), that would accomplish things like Strava (and other 3rd party sites) automatically recognizing such data without any additional work on their part. But I don't think Garmin would ever implement that.

Comment
  • To be clear, this feature request is only asking Garmin to alow nativeNum fields written by CIQ apps to be treated just like native data in Connect (and to override any native data that's be written to the same FIT file).

    It is *not* asking Garmin to make it so that when a CIQ uses the nativeNum option, it actually writes the data to the FIT file exactly like native data. The reason I didn't ask for that is because I am 100% sure Garmin would never do that.

    Yeah, if CIQ data fields could actually write *literal native data* to the FIT file (and prevent the same native data from being written by the activity), that would accomplish things like Strava (and other 3rd party sites) automatically recognizing such data without any additional work on their part. But I don't think Garmin would ever implement that.

Children
  • Good clarification. So if you write Power data as a nativeNum from your field and I do as well, and Garmin also writes true native power, how would Garmin Connect disambiguate it? Maybe within the Garmin Connect system in general, or on an Activity basis, we could select which of the three (in this example) it should use as the "native" Power for calculation on calories, training load, etc?