This example submits a single record consisting of fieldName/value pairs to RESTfm, where fieldName may not begin with the prefix 'RFM' (this limitation is described in the section about POSTing data in application/x-www-form-urlencoded format). Join string to httppost:// URL with '?'.Join each 'fieldName=value' pair with '&'.Replace all occurrences of '=' with '%3D' and '&' with '%26'.Replace all occurrences of '%' with '%25' (This step must be done first).

For each fieldName and value to be submitted:.Note: Under the hood, 'httppost' POSTs data as application/x-Note 2: Except where additional pre-encoding is noted below, no 'URL encoding' should be performed on the string passed to 'Insert From URL', this is handled automatically for you by FileMaker (which is why it is impossible to submit data containing '&' and '=' characters). Note: This no longer applies to FileMaker 16 and later where the Insert From URL step allows proper data passing and encoding. RESTfm is informed of this additional encoding through the use of the RFMfixFM02 flag. This page describes a workaround by applying additional encoding to allow all possible characters to be submitted in a POST.

This new protocol allows FileMaker to act as a RESTfm client where data may be submitted to RESTfm and the response stored in a field.ĭue to limitations in the design of the 'Insert From URL' script step, some characters cannot be submitted (specifically '&' and '='). FileMaker 13 introduced the 'httppost' protocol for use with the 'Insert From URL' script step.

Filemaker pro go