2 Replies Latest reply on Jul 2, 2015 1:49 PM by TSGal

    XML query for -layoutnames returns extra empty elements

    Malcolm

      Summary

      XML query for -layoutnames returns extra empty elements

      Product

      FileMaker Server

      Version

      13.0.9.905

      Operating system version

      Mac OS X 10.9.5

      Description of the issue

      An xml query for -layouts returns the wrong set of elements. In the instance that I have observed, the returned set contains the correct elements but it also contains extra elements which are empty.

      Steps to reproduce the problem

      Database hosted on FMS 13.0.9.905 with an account which has xml privileges enabled.

      The privilege set should have custom settings for layouts. Some layouts are not acessible, others are.

      Make an xml request for either FMPXMLRESULT or fmresultset.

      Request: https://domain.name/fmi/xml/FMPXMLRESULT.xml?-db=Responder&-layoutnames
      Request: https://domain.name/fmi/xml/fmresultset.xml?-db=Responder&-layoutnames

      Expected result

      We expect the xml to return the correct elements, the correct number of elements and the correct count of elements.

      <?xml version ="1.0" encoding="UTF-8" standalone="no" ?>
      <!DOCTYPE fmresultset PUBLIC "-//FMI//DTD fmresultset//EN" "http://localhost:16020/fmi/xml/fmresultset.dtd">




      </field-definition>

      connect
      confirm

      Actual result

      The xml returned includes the correct elements. It returns the wrong number of elements and the wrong count of elements. The count returned accurately reflects the number of elements returned, however, the number of elements returned is wrong.

      <?xml version ="1.0" encoding="UTF-8" standalone="no" ?>
      <!DOCTYPE fmresultset PUBLIC "-//FMI//DTD fmresultset//EN" "http://localhost:16020/fmi/xml/fmresultset.dtd">




      </field-definition>

      connect
      confirm



      Exact text of any error message(s) that appear

      There are no error messages

      Configuration information

      no additional config required

      Workaround

      no workarounds found