11 Replies Latest reply on May 9, 2017 7:02 AM by TSGal

    Print[] Script Step XML Broken

    JEDtech

      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.

        • 1. Re: Print Setup XML Broken
          beverly

          this information may be helpful to the TS folks:

           

          OS and version

          Hardware

           

          beverly

          • 2. Re: Print Setup XML Broken
            JEDtech

            Thanks, updated to include that.

            • 3. Re: Print[] Script Step XML Broken
              TSGal

              JEDtech:

               

              Thank you for your posts.

               

              Technical Support has run into this issue with a customer, and our Development and Testing departments are aware of it.  The notes from Testing are a bit cryptic, but it seems the cause is a Print script step with the Restore option.  Without the Restore option, the XML DDR appears to not have this issue.  However, another Tester reports it is the Print script itself.  Therefore, inconclusive, but it is still being investigated.

               

              I have attached your post to the original report.

               

              Could you send in a clone of your solution?  This may help Testing and Development narrow in on the cause.  If so, I have sent you a private message with instructions where to send the file.

               

              For now, until this is addressed, the workaround, is to either remove the Print script steps prior to running the XML DDR, or remove the extraneous characters from the CDATA element.

               

              TSGal

              FileMaker, Inc.

              • 4. Re: Print[] Script Step XML Broken
                nickorr

                JEDtech,

                 

                The issue isn't the CDATA, it's this bit :

                 

                <PlatformData PlatformType=" Õ">

                 

                That's an invalid platform type, and the invisible character before the O will be a high ascii, invalid in XML character.  Delete the Print step and re-create it and you should be right.

                 

                Cheers,

                Nick

                • 5. Re: Print[] Script Step XML Broken
                  TSGal

                  JEDtech:

                   

                  Clone of your file has been received.  I have sent the file to Development and Testing for review.  When I receive any feedback, I will let you know.

                   

                  TSGal

                  FileMaker, Inc.

                  • 6. Re: Print[] Script Step XML Broken
                    JEDtech

                    This problem is still occurring when the Print command is created with FileMaker Pro 15.0.1 on Windows 10.  The bad XML shows up whether the DDR is generated on Windows or Mac with FMPA 15.  Deleting and re-creating the print step still shows bad XML in the PlatformType.  In addition the XML line with the broken PlatformType has a CDATA that exceeds 10 MB.

                     

                    It may be worthwhile to note that the only printers that are generating these corrupted and huge PlatformType CDATA records are locally-attached, not network printers.  The printers causing the problem are a Zebra ZP450, Brother HL2240, Aficio SP C431DN.

                     

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

                         <StepText>Print [ Current record; All Pages; Orientation: Portrait; Paper size: 4.5&quot; x 11&quot; ]

                    [ Restore: Zebra; No dialog ]</StepText>

                         <NoInteract state="True"/>

                         <Restore state="True"/>

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

                              <PlatformData PlatformType="PrNm"><![CDATA[0...

                              <PlatformData PlatformType="?®"><![CDATA[0...

                         </PrintSettings>

                    </Step>

                    • 7. Re: Print[] Script Step XML Broken
                      TSGal

                      JEDtech:

                       

                      I can confirm the issue was not addressed in FileMaker Pro 15.0.1.

                       

                      TSGal

                      FileMaker, Inc.

                      • 8. Re: Print[] Script Step XML Broken
                        JEDtech

                        Interestingly I tried to reproduce the problem in a simple database by copy/pasting the problem script but the script pasted into the new database was not broken when I did the DDR.  I also tried copy/pasting just the broken script step and it was also clean.  I tried on both Mac OS X 10.11.5 and Windows 10 with FileMaker 15.0.1.  I also noticed that when copy/pasting a group of scripts, some of which had the problem, it would not successfully paste all of them in one batch and seemed to stop at the bad ones.

                        • 9. Re: Print Setup XML Broken
                          jlf_nga

                          We ran into the same issue here with FileMaker 14.0.2, 15.0.2 and 15.0.3 running on Win 7 64 bits.

                           

                          I have made an empty DB with only one script, only one print step. The xml database report is around 20 MB.

                           

                          I tried with 3 different printers (server printer, local and pdf writer). The problem appears on all of them.

                          • 10. Re: Print Setup XML Broken
                            TSGal

                            jlf_nga:

                             

                            I have attached your comments to the original report.  When more information becomes available, I will post again.

                             

                            TSGal

                            FileMaker, Inc.

                            • 11. Re: Print[] Script Step XML Broken
                              TSGal

                              JEDtech (et al):

                               

                              This issue has been addressed in FileMaker Pro 16.

                               

                              TSGal

                              FileMaker, Inc.