Thanks John, I don’t want to hijack this thread, but I fixed the issue by using the field key rather than the name to access the relationship field contents; then all was back to normal.
I probably have a naming collision somewhere, although its strange that I didnt see this behaviour before the 5.6 update.
Thanks for the pointers nonetheless!
