FileMaker Cloud 1.16.0.55 Release Notes
This software updates FileMaker Cloud version 1.15.2.32 to version 1.16.0.55, and fixes bugs.
FileMaker Cloud 1.16.0.55 is available in the US, Canada, Europe, Japan, and Australia.
Software details
New features in FileMaker Cloud 1.16.0.55
- OAuth 2.0 client authentication: You can configure FileMaker Cloud to allow FileMaker clients to authenticate via an OAuth identity provider to access a hosted database file.
- PDF and print support: Files hosted via FileMaker WebDirect can now use the Print, Print Setup, and Save Records as PDF script steps. FileMaker Script Engine now supports the Print Setup and Save Records as PDF script steps for all hosted files. See FileMaker Pro Help.
FileMaker Admin API is an application programming interface that allows web services to perform administrative tasks on FileMaker Cloud. For information about this REST-based API, see FileMaker Admin API Guide.
FileMaker Admin API is a trial feature in FileMaker Cloud 1.16.0 that expires on September 27, 2018. Once the trial expires, the feature will cease to operate.*
FileMaker Data API is an application programming interface that allows web services to access data on FileMaker Cloud. For information about this REST-based API, see FileMaker Data API Guide.
FileMaker Data API is a trial feature in FileMaker Cloud 1.16.0 that expires on September 27, 2018. Once the trial expires, the feature will cease to operate.*
- Tableau Web Data Connector for FileMaker: Produce graphic representations of your FileMaker data with this connector, a FileMaker Data API that integrates with Tableau Desktop. Tableau Web Data Connector is also a trial feature.
*Product and feature releases remain at the sole discretion of FileMaker, Inc., and are subject to change without notice.
Compatibility and upgrade
- FileMaker Cloud 1.16.0.55 is compatible with FileMaker 16.0 clients at minimum.
You can upgrade to FileMaker Cloud 1.16.0.55 from these versions:
- FileMaker Cloud 1.15.2.32
- FileMaker Cloud 1.15.1.35
- FileMaker Cloud 1.15.0.194
- FileMaker Cloud 1.15.0.185; you must apply the FMUpdate001 patch to upgrade successfully
Notes:
- When you upgrade from a previous version and have set up Login with Amazon OAuth authentication, the Login with Amazon button disappears. To restore the button, in FileMaker Cloud Admin Console, go to Configuration > Password and Users and save Amazon as an identity provider again.
- After upgrading from FileMaker Cloud version 1.15.0.185 or 1.15.0.194, you must refresh your instance before attaching or detaching snapshots of database volumes.
Fixed bugs
Addressed an issue where, under certain conditions, committing a record while reconnecting could corrupt the record.
FileMaker clients
When uploading database files to FileMaker Cloud:
- In FileMaker Pro Advanced, encrypt the file before upload.
- If you have FileMaker Pro and will upload an unencrypted file, check the space available on your storage volume. You need at least three times the file size in space to upload. If you don't have that much space, upgrade the AWS storage volume size before uploading to FileMaker Cloud.
When a CSV or TAB file with UTF-8 encoding that contains about 1500 Asian-language characters and has macOS end-of-line (EOL) or UNIX line endings is imported using the Perform Script on Server script step or FileMaker WebDirect, the imported characters become unknown characters.
To import characters as expected, do one of the following:
- insert double quotation marks around each field value
- save the file with a different encoding such as UTF-16
- save the file in a non-text based file format such as FMP12, MER, or XLSX
FileMaker Admin API
- When you create a message or script schedule and specify a start date parameter with two digits for seconds, the second digit is ignored. For example, a date specified as
2017-10-25 11:30:23
returns the result"2017-10-25 11:30:00"
. - When you specify a
gracetime
parameter with the close database call, the parameter is ignored and defaults to 90 seconds (the default for disconnection). - cURL commands do not work with the open, close, pause, and resume database calls. To fix this problem, add
-d {}
to each command.