TestStand 3.1 XML Reports in TS4.1

Question

I am trying to implement TestStand 4.1 in our facility as seamlessly as possible. This means I still need to run TS3.1 sequences with no modifications on both systems with TS3.1 and with TS4.1.
My problem is with the creation of xml documents when run in TS4.1. When we first implemented xml it was on TS2.0 which didn't support xml at the time. So some patch was downloaded from NI I believe and it worked fine. We continued to use the patch when we switch to TS3.1. But when I now run the TS3.1 sequences in TS4.1 the reports are generated, but slightly differently, I cannot view the xml document in I.E. The error is:
"Required white space was missing. Error processing resource"
and the offending line(s) in the report are:   <ATMLStylesheetMRU type=" dimensions="[0..2]" decimateBy="0">
  <Element type="" index="[0]" name="ATMLStylesheetMRU" >trml.xsl</Element>
  <Element type="" index="[1]" name="ATMLStylesheetMRU" ></Element>
  <Element type="" index="[2]" name="ATMLStylesheetMRU" ></Element>
  </ATMLStylesheetMRU> 
These lines do not appear in the report if the sequence is run with TS3.1. 
I modified the TS3.1 Process model and ReportGen_XMLseq to use the original "modelsupport.dll" from TestStand 3.1 since the TS4.1 version didn't support some of the commands called. I also changed the report.xsl and horizonal.xsl called from the process model to the TestStand 4.1 versions, but the problem is still there. 
I admit to not knowing exactly how the reports are generated, but I suspect the above lines are there because the API calls are to the TS4.1 engine as it is the active TestStand version. Looking for any sort of help on this one, not that well versed in xml. Am I trying to do the impossible? I don't want to switch the reports to the TS4.1 format at this time, as we have custom software that imports the data and it currently doesn't work with the TS4.1 report format.
Thanks 

Answer 1

Cabman,
In TS 3.5 we added a new type of report called ATML. The
offending lines in the report that you are refering to, is to store
stylesheet information for this new report format.
But adding these new properties to ReportOptions should not cause the issues you are describing. 
I
did notice that the text you pasted is not exactly what we generate in
TS 4.1.Here is why we generate in TS 4.1 for xml reports
    <Prop Name='ATMLStylesheetMRU' Type='Array' LBound='[0]' HBound='[2]' ElementType='String' Flags='0x0'>
        <Value ID='[0]'>trml.xsl</Value>
        <Value ID='[1]'></Value>
        <Value ID='[2]'></Value>
    </Prop>
In
the text you pasted, I noticed that type attribute is empty in all 4
lines and also the generated XML snippet looks different.
I am not sure how your XML report was generated,  but that might be the issue. 
In TS 3.0, we introduced a new API called PropertyObject.GetXML which can be used to generate an XML report. 
To help diagnose the problem I have a couple of questions. 
1. Do you still use your TS 2.0 process models or are you using TS 4.1's process models?
2.
Can you give me more details of how does the XML report get generated
in your system? Are you using the 2.0 XML report generation mechaism or
did you move to using TS 4.1's XML report generator?
Regards
Anand JainNational Instruments