5 Replies Latest reply on Jun 18, 2015 11:02 AM by philmodjunk

    XML query for -layoutnames returns extra empty elements



      XML query for -layoutnames returns extra empty elements


      FileMaker Server


      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 with an account which has xml privileges enabled.

      Make an xml request for either FMPXMLRESULT or fmresultset.

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

      Expected result

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

      Actual result

      The xml contains extra elements and the attributes of several elements contain the wrong information.

      The element DATABASE's RECORDS attribute is wrong. It is assigned the number of elements returned.
      The element RESULTSET's FOUND attribute is wrong. It is assigned the number of elements returned.
      The RESULTSET contains the correct ROWs and also contains a number of extra ROWs. The extra ROWs are do not contain data. Their MODID and RECORDID are both assigned "0".

      <?xml version ="1.0" encoding="UTF-8" standalone="no" ?>


      Projects List View
      Projects List View | iPad
      Projects | iPad
      Tasks | iPad
      Project List | iPhone
      Project Overview | iPhone
      Projects | iPhone
      Tasks | iPhone
      Projects List View | Web
      Projects | Web
      Tasks | Web
      PHP Technology Test

      Exact text of any error message(s) that appear

      no error messages

      Configuration information

      no extra config required


      no workaround found