I've successfully set up a fusion between a child node type - Profile - and a parent node type - Usernode. It pulls in all the necessary information, with the child node as the primary view, since the parent node is only pulling in one field from Usernode. However, all fields from the Usernode view (and not the primary, Profile view) are being included twice (I added a second one to be certain it wasn't a single field at fault).

Any thoughts on what might cause this? My best guess at this point is that something in the SQL call is wrong (or something in my setup). In every case there is only one Usernode and one Profile node.

Comments

tortoise’s picture

tortoise commented

I have this problem as well, in certain circumstances. I have a fusion which shows various fields for all the grandchildren (via Node Relativity) of a given node. When I go to the page view for this fusion, everything is fine, but when I embed the view into grandparent nodes using Viewfield, the fields from the fused view show up twice.