FileMaker Cloud 1.16.1.18 Release Notes
This software updates FileMaker Cloud version 1.16.0.55 to version 1.16.1.18, and fixes bugs.
FileMaker Cloud 1.16.1.18 is available in the US, Canada, Europe, Japan, and Australia.
Software details
New features in FileMaker Cloud 1.16.1.18
Improved database downloading:
-
When you download a database, FileMaker Cloud checks the space available for download processing and notifies you during the process of checking and downloading.
-
Error logging for downloading has been improved.
Compatibility and upgrade
- FileMaker Cloud 1.16.1.18 is compatible with FileMaker 16.0 clients at minimum.
-
You can upgrade to FileMaker Cloud 1.16.1.18 from these versions:
- FileMaker Cloud 1.16.0.55
- 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:
- Instance settings information can take several hours to appear in FileMaker Cloud Admin Console after an upgrade or switchover.
- Version upgrade or instance switchover can fail for t2small instances. If this occurs, restart the instance in the Amazon Web Services (AWS) console.
- 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 the Configuration > Password and Users tab 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 the following issues:
-
An error occurred when attempting to download a large database.
-
An error caused by insufficient disk space occurred when opening a large database.
-
The notification "Insufficient free space for download: volume size upgrade recommended" has been added.
-
When the AWS snapshot limit has been reached, the notification "Snapshot error during backup," followed by an AWS diagnostic message, is displayed.
FileMaker clients
-
When uploading database files to FileMaker Cloud:
- In FileMaker Pro Advanced, encrypt the file before uploading it.
- 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
-
If you request multiple database downloads, after the initial download notification, any subsequent notifications do not appear until the FileMaker Cloud session expires and you sign in again.
FileMaker Admin API
-
When you create a message or script schedule and specify a start date parameter with two digits for seconds, the seconds are 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).
Documentation errata
The following information was missing from FileMaker Cloud 16 Admin API Guide:
-
When a script runs and a service is already executing (for example, during a long loop), the FileMaker error 10006, "kServiceAlreadyRunning," is returned.
-
When a script schedule stops executing, the FileMaker error code 10908, "System script aborted," is returned.
APIs, technologies, or features to be deprecated
As FileMaker Cloud evolves, the list of supported technologies, APIs, and features will change. As part of this evolution, certain operating systems versions, hardware, and features may be deprecated in favor of newer ones. While deprecation does not mean the immediate deletion of an item, you should migrate your solution away from deprecated technologies, as these technologies may be removed in a future version of the product.
For current deprecation information, see FileMaker Cloud Technical Specifications.