Custom Web Publishing Guide

Table Of Contents
Valid names used in query strings 77
1 Database names, layout names, and field names used in query strings are case insensitive, such as
–lay=mylayout to specify MyLayout.
Note Field and database names that are used in XSLT statements outside of query strings are case sensitive
and must exactly match the actual names used in the database. For example, in this statement:
<xsl:value-of select="fmrs:field[@name='LastName']"/>
the field reference “LastName” must exactly match the name of the LastName field in the database.
1 For the –find command, the value of a field is case insensitive. For example, you can use Field1=Blue or
Field1=blue. For the –new and –edit commands, the case you use in the value of a field is preserved and
stored in the database exactly as you specify in the query string. For example, LastName=Doe.
About the FileMaker Query Strings Reference
The FileMaker Server Advanced CD includes a FileMaker database called Query Strings Reference.fp7 that
contains brief descriptions and examples of each of the FileMaker query commands and query parameters.
You can open the FileMaker Query Strings Reference in the Custom Web Publishing Reference folder on the
FileMaker Server Advanced CD.
About the syntax for a fully qualified field name
A fully qualified field name identifies an exact instance of a field. Because fields with common names can be
based on different tables, you must use fully qualified names, in some cases, to avoid errors.
The syntax for specifying a fully qualified field name is:
table-name::field-name(repetition-number).record-id
where:
1 table-name is the name of the table that contains the field. The table name is only required if the field is not
in the underlying table of the layout specified in the query string.
1 field-name(repetition-number) is the specific value in a repeating field, and is only required for repeating
fields. The repetition number starts counting at the numeral 1. For example, field-name(2) refers to the
second value in the repeating field. If you don’t specify a repetition number for a repeating field, the first
value in the repeating field is used. The repetition-number is required for the –new and –edit query
commands involving repeating fields, but it is not required for the –find command.
1 record-id is the record ID, and is only required if you are using a query string to add or edit records in portal
fields. See the following sections
“Adding records to a portal,” and “Editing records in a portal.” The
record-id is required for the –new and –edit query commands involving portal fields, but it is not required
for the –find command.
Note To be accessible, fields must be placed on the layout you specify in the query string.
Adding records to a portal
To add a new record to a portal at the same time you add a parent record, use the –new query command and
do the following in query string for the request:
1 Use the fully qualified field name for the related portal field.
1 Specify 0 as the record ID after the name of the related portal field.
1 Specify at least one of the fields for the parent record before specifying the related portal field.
1 Specify the data for the match field (key field) in the parent record.