That sucks.
I've tried just about everything at this point. For some reason, some datamaps appear to have mostly nested just fine and others just become scrambled into HTML. I was using a variable to call the child datamaps, so I tried inserting them into the code wholesale, but I got the same result.
2. The Map object (which is what datamap is) doesn't impement conversion to String itself so it defaults to the Object object's method which always returns "[object Object]".
Not sure I understand. What if the object's object is a datmap? It seems like other people have not only done this, but outright told other people that this is possible. It's really frustrating, seeing that it doesn't actually appear to be possible at all.
I don't know a way to overcome this, short of outputting each of the parent datamap's child Map based properties manually.
I've caved, and am now tediously going back to enter every individual field. It kind of sucks, because I wanted to give it a certain look and feel using nested datamaps. I intended to make this into a kind of fancy-looking dossier broken down by headers and subheaders.
I personally view the (print:) macro's ability to output complex Map objects as more of a debugging feature than a means to display content to an end-user.
It looks like it isn't actually necessary. Whether you use the (print:) macro or just call the datamap variable by itself doesn't really seem to matter, because it prints the full datamap either way.
Thanks for your answer.