-relatedsets.filter and -relatedsets.max Ignored When Used With FMPXMLRESULT
Description of the issue
FileMaker Product(s) involved FileMaker Server Advanced (and likely FileMaker server) right up through the current v2 (.206) release (this bug was first reported by me prior to the initial release of FMS10). Operating System involved Tested with Mac OS X v10.5.8 Detailed description of the issue When performing a query via the WPE, any -relatedsets.filter parameter present is ignored. Adding -relatedsets.max makes no difference. As a result, all portal rows are always returned (ironic on a dataset billed as "less verbose", as portal data can frequently be the most verbose part of the data returned.) Exact steps to reproduce the issue Create a new database called "Test.fp7".In the newly created Test table, create two fields: Test_ID (a number field) and Test_Label (a text field).Create another table in the database named "Test_Related", and add 2 fields to it: Test_Related_ID (a number field) and Test_Data (a text field).Add a relationship between the two tables using the Test_ID and Test_Related_ID fields.Click "Okay" to close the Define Database dialog.Create 3 records in Test, set their ID field to different integers (I used 1, 2, and 3), and their Label text to easily identifiable strings (I used Curly, Larry, and Moe).Enter Layout mode, add a portal to Test Related, and set the portal to display 2 rows with no vertical scrollbar; click Okay, add both related fields to the portal, then click okay again.Return to browse mode (saving changes), and navigate to the Test_Related layout.Create 3 records for each parent record, and add recognizable text for the data (I used 3 'a's in the first record, 3 'b's in the second, up to 3 'i's in the ninth, with 3 related to each parent record.Return to the Test layout, and you should note that 2 of the 3 related records for each parent record appear in the portal.Close the database in FileMaker.Open the FMS admin application, and log in to your FMS machine.Use the "Upload a Database" wizard to upload your new database to your FMS server.Open your newly oploaded database via remote, and change the extended privileges to allow XML access (fmxml) on the full access account.In your browser (I used Firefox) run some queries against your new database. Expected Result The following queries should return either 1 or 2 portal rows, but never all three (the layout is only displaying 2 remember): http://192.168.2.3/fmi/xml/FMPXMLRESULT.xml?-db=Test&-lay=Test&-relatedsets.filter=layout&-relatedsets.max=1&-findanyhttp://192.168.2.3/fmi/xml/FMPXMLRESULT.xml?-db=Test&-lay=Test&-relatedsets.filter=layout&-findanyhttp://192.168.2.3/fmi/xml/FMPXMLRESULT.xml?-db=Test&-lay=Test&-relatedsets.filter=layout&-relatedsets.max=1&Test_ID=1&-findhttp://192.168.2.3/fmi/xml/FMPXMLRESULT.xml?-db=Test&-lay=Test&-relatedsets.filter=layout&Test_ID=1&-find Actual Result All portal rows are returned in each case. Exact text of any error message(s) that appeared N/A Any additional configuration information/troubleshooting that is relevant to the issue This issue seems to appear in any database, and not merely the simplest case as described above. Any workarounds that you have found None, without switching to a verbose data set.