Yes, there is a way to deal with this. If you post one of the scripts you're having trouble with, we should be able to suggest changes to it.
A Lesson in Templates shows how fields are renamed during spawning pages with the 'bRename" parameter set to true.
The fields of the template are prefixed with "P[#}.[emplateName]." If one uses the "event.target.name" property of the field name, the string value can be parsed to obtain the field's name split by the "." character. The first element of the array will be the "P[#}" value and the second element will be the template name. One then only needs to compute the prefix string which can be added to any field's template source name on the spawned page to obtain the full name of the field on the spawned page. I would create a document level function to generate this prefix string if the field has an altered name as part of the spaqning. If the field's name has not been altered then return a null stirng. This approach will allow one to workout the necessary scrpts on the template and easily add the prefix string if needed.
It's probably the wrong way to do it, but like I said I am self taught so its the best I could do haha
var myRad = getField("16");
if(myRad.value == "Yes")
getField("Total Floor area").textColor = color.black;
getField("m").textColor = color.black;
getField("m2").textColor = color.black;
getField("Height:").textColor = color.black;
getField("Percentage of overall floor space:").textColor = color.black;
getField("%1").textColor = color.black;
this.getField("Floor area").readonly = false;
this.getField("heights").readonly = false;
this.getField("% of floor").readonly = false;
Thanks in advance
If you used the rename option when calling the spawn method, you have not accounted for the addition of the "P#.templateName." being prefixed onto the fields on thw spawned pages