I would like to report what appears to be an issue with the Connect IQ data field selection on the Garmin Edge 540. I run an iPhone12 with iOs 26.5.2.
Description
I have several Connect IQ data fields installed, including:
- AppBuilder 5
- AppBuilder 5 (B)
- AppBuilder 5 (C)
- AppBuilder 5 (D)
- PoWer Prime
- RaceNotes
All applications are installed correctly and appear under Connect IQ → My Data Fields.
However, when configuring activity data screens, the available Connect IQ fields depend on the screen layout and even on the position of the field within the layout.
For example:
- some layouts only offer a single AppBuilder instance,
- others offer two or three,
- occasionally AppBuilder (D) appears while (C) does not,
- PoWer Prime also appears inconsistently,
- there is no obvious or reproducible mapping between screen position and available Connect IQ fields.
Troubleshooting performed
To exclude configuration problems I have:
- restarted the Edge 540,
- synchronized repeatedly,
- deleted all data screens,
- rebuilt the activity profile from scratch,
- tested 1-, 2-, 3- and multi-field layouts,
- verified that all Connect IQ fields are installed correctly,
- reproduced the behaviour with unrelated Connect IQ applications (not only AppBuilder).
The behaviour therefore does not appear to be specific to AppBuilder.
Expected behaviour
Every installed Connect IQ data field that is compatible with the Edge 540 should be selectable in every data-field position where Connect IQ data fields are supported.
If there are documented limits (for example, only one CIQ field per screen or per layout), these should be applied consistently and documented clearly.
Why this matters
Many cyclists use Connect IQ data fields to extend Garmin's functionality—for example to compute custom power metrics, physiological metrics, W′ balance, corrected sensor values, or other derived quantities.
The current behaviour makes it difficult or impossible to build custom data pages, because the available Connect IQ fields appear to change unpredictably depending on the selected layout.
Could you please let me know whether this is
- an intended limitation,
- a firmware bug,
- or an issue already known to the development team?
I would be happy to provide further details or perform additional tests if helpful.
Kind regards,
Raphael Berger