It may not be the whole story but I’m trying to figure out why a seamless Clone field referencing the same field seems to stick an extra array around the output when it’s a direct field in a field group vs. a sub field of say a Repeater.
Output of the Clone field directly on a field group for a Custom Post Type using get_field (content_select is the ID of the cloned field):
Sorry to resurrect an old thread, but I’ve just been pulling my hair with the same issue on a new project.
It was proving very difficult to get fields and sub fields to match references, as I needed them to, for various template parts.
In my example,the client had a broad colour palette,and pretty much every page component (built using flexible content) could use any colour from the palette.
Rather than manually recreate the colour select field,I thought I’d be a bit more efficient and create a select field in a ‘brand options’ field group,and then clone that field whenever needed. For example: