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

"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?"

That's a great question, and I think the answer would be that Garmin will never fulfill this feature request, so it's a moot point.

Obviously the intent behind this feature request is that Connect would completely override true native fields (such as distance, power, etc) with the corresponding CIQ nativeNum fields.

Your question kind of suggests one of the reasons Garmin does not want to do this - what happens when apps write bad nativeNum data for power/distance/etc? Customers will probably point their fingers at Garmin.

I don't think it's a solution to allow customers to select the data source, as it's just more work for Garmin and more confusion for the end user.

Even strava doesn't allow you to select the power data source for running - if real native power is present, then it's always used, otherwise CIQ nativeNum power will be used if present. That's why if you want Stryd power to be used in Strava, you have to disable native running power. (Ofc it's no issue for the Stryd app, since Stryd will naturally ignore native Garmin power in favour of Stryd power.)

"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?"

That's a great question, and I think the answer would be that Garmin will never fulfill this feature request, so it's a moot point.

Obviously the intent behind this feature request is that Connect would completely override true native fields (such as distance, power, etc) with the corresponding CIQ nativeNum fields.

Your question kind of suggests one of the reasons Garmin does not want to do this - what happens when apps write bad nativeNum data for power/distance/etc? Customers will probably point their fingers at Garmin.

I don't think it's a solution to allow customers to select the data source, as it's just more work for Garmin and more confusion for the end user.

Even strava doesn't allow you to select the power data source for running - if real native power is present, then it's always used, otherwise CIQ nativeNum power will be used if present. That's why if you want Stryd power to be used in Strava, you have to disable native running power. (Ofc it's no issue for the Stryd app, since Stryd will naturally ignore native Garmin power in favour of Stryd power.)