JEDtech

Print[] Script Step XML Broken

Discussion created by JEDtech on Mar 3, 2016
Latest reply on May 9, 2017 by TSGal

PROBLEM

 

Using FileMaker Pro Advanced 14.0.5 on Mac OS X 10.10.5 (MacBook Pro Retina Mid-2014) to generate a DDR from a database produced XML that could not be imported into Inspector.  It appears that the XML syntax is invalid or too large.  The XML block totals over 12 MB of data, the overwhelming majority of which is in the 2nd Platformdata CDATA element. I have truncated the 2nd PlatformData CDATA element because of the size.  Also the 2nd PlatformType appears to be corrupt since all the other PlatformType references I could find in the file were either "M_PM" or "W_PM".

 

<ButtonObj buttonFlags="0" iconSize="12" displayType="0">

   <Step enable="True" id="43" name="Print">

      <StepText>Print [  ]</StepText>

      <NoInteract state="False"></NoInteract>

      <Restore state="False"></Restore>

      <PrintSettings PageNumberingOffset="0" PrintToFile="False" AllPages="True" collated="False" NumCopies="1" PrintType="BrowsedRecords">

         <PlatformData PlatformType="PrNm"><![CDATA[0000000300000011000000000000001100000000000000210000005C0000005C000000640000006500000074000000630000006D000000770000006600000070000000720000003000000030000000380000005C0000004400000045000000540000004F00000044000000430000005000000052000000310000003700000030000000330000005F000000430000006F0000006C0000006F00000072]]>

         </PlatformData>

         <PlatformData PlatformType=" Õ"><![CDATA[0064006500740063006D0077006600700072003000300038005C004400450054004F00440043005000520031003700300033005F0043006F000000000001040006DC00F81B43FF800701000100EA0A6F08640001000F005802020001005802020000004C00650074007400650072002000280038002E00350020007800200031003100220029000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000040000000200000001000000FFFFFFFF0000000000000000000000000000000044494E5522007802B4044417A46CD8001000000000000000000000000100000000000000000000000000000016000000000000000000010000000000000000000000000000000000000000000000000000000000010000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000078020000534D544A00000000100068025800650072006F007800200043006F006C006F00720020004300360030002000500043004C0036000000524553444C4C00556E69726573444C4C005872785472756554797065466F6E74446C4F7074696F6E005454465F444F574E4C4F4144.........

         </PlatformData>

     </PrintSettings>

  </Step>

</ButtonObj>

 

WORKAROUND

 

Digging through the XML I was able to identify the 2 buttons that were generating the corrupt XML.  I switched them from doing a single script step of "Print[]" to calling a script which resolved the problem.

Outcomes