Technically, I have two questions here, but hopefully they're related closely enough that no one will be bothered by me asking them together.
Firstly, I'm wondering what benefit there is in setting natativeNum. For example, I have my own way of calculating calories burned, and I have a field for that as MESG_TYPE_SESSION and another as MESG_TYPE_RECORD. I set the nativeNum for those fields as 11 and 33 respectively (which if I'm understanding the documentation correctly were the appropriate values). And when I look at the .fit data (as a .csv). I can see that the nativeNum values were set properly, but I don't notice any difference when I look in the Connect mobile app. I half expected my calculation for calories to replace the Garmin value (though I could understand Garmin not wanting to allow that).
Secondly, I'm wondering if I need my own fit data reader to get anything out of using the count option so I can save arrays as values. For example, I have one type of value for which I have two fields, one being the "actual" for the value type and the other is the "target" of the value type. I would really like for the Connect mobile app to display these on a single graph (I know the app does allow the user to manually overlay values from one plot onto another, but I would rather make this automatic), so I thought I'd try making one field that saves the two values as an array. Looking at the .fit data (as a .csv) shows that the value was properly saved as an array, but the app seems to only show the first value in the array.
I want to make it clear that I'm not asking what I'm doing wrong (though if anyone can see any error I'm making, I'd be glad to here about it). I really just want to know what I should expect when I use these two options correctly.
