Import Records

•Verify SSL Certificates verifies the SSL certificate of the server specified in an HTTP request for XML data. If the certificate cannot be verified, users can choose to connect anyway or cancel to skip this script step. If the certificate cannot be verified and the Set Error Capture script step is set to On, this script step behaves as if the server were unavailable.

•With dialog specifies whether to display import-related dialog boxes when the script step is performed. However, if a data source file has not been specified, the Open File dialog box is displayed when a script is run.

•Specify data source specifies the file or source of the data to be imported. Depending on the file or source you choose, a dialog box may appear for specifying the following additional options:

When you choose this file or source	Do this
File	In the Specify File dialog box, choose the file you want to import, or type file paths directly into the list. Specify one path per line. FileMaker Pro Advanced will use the first path it locates as the file to import. See Creating file paths.
Folder	In the Folder of Files Import Options dialog box, choose the folder of image or text files that you want to import, or type the folder paths directly into the list. Specify one path per line. FileMaker Pro Advanced will use the first path it locates as the folder to import. See Importing a folder of files all at once and Creating file paths. This option is not supported in FileMaker WebDirect and server-side scripts.
XML Data	In the Specify XML and XSL Options dialog box, choose the source of the XML data that you want to import, and choose an XSLT style sheet if you want to apply one prior to import. The XML and XSLT source may be a file or the result of an HTTP request, or a calculation that generates a file path or an HTTP request. For more information, see Importing XML data.
ODBC Data	Specify the data source name and location, the user ID and password (if any), and the SQL query to be executed. You can enter a query directly or specify a calculation to generate the query. For more information, see Automating ODBC import using the Import Records script step. SQL statements are limited to a maximum length of 256 K characters (512 KB). Note If you use the Import Records script step to import ODBC data that contains Unicode strings, your ODBC driver must support Unicode. Otherwise, the results may be inconsistent.

•Specify import order tells FileMaker Pro Advanced to use a predefined import order. The last import order used in the file appears as the default and can be edited. This option also lets you choose whether to keep repeating field data together or to split repeating fields into separate records, as well as whether to add new records, replace data in the current found set, or import data as a new table.

Note When import source fields and target fields are mapped using matching names, field name matching is performed dynamically each time the script step is performed.

Compatibility

Product	Supported
FileMaker Pro Advanced	Yes
FileMaker Go	Partial
FileMaker WebDirect	Partial
FileMaker Server	Partial
FileMaker Cloud	Partial
FileMaker Data API	No
Custom Web Publishing	No
Runtime solution	Yes

Originated in

Description

You can set the import order and use the Specify import order option, or perform this script step with the dialog box so the user can set new criteria, such as importing data as a new table.

If the source file is open, the found set is imported; if not, all records in the source table are imported.

If you include this script step in a server-side script and you do not set With dialog to Off, the text (NOT compatible) appears after the script step. The script, however, will run. The behavior will be the same as if With dialog is Off. See Get(DocumentsPathListing) function for more information.

If you run a server-side script to do any of the following, you will receive an error:

Notes

•For FileMaker Pro Advanced, if an absolute path is not specified in a script that will be run from FileMaker Pro Advanced, the path is assumed to be relative to the location of the database file from which the script was run. For example, if a script containing the Export Records script step is run with the pathname file:/export.tab, and the file running the script is /MyFiles/Library/Books.fmp12, the exported file will be created as /MyFiles/Library/export.tab.

•Support for importing photos from a digital camera or device has been removed from FileMaker Pro Advanced.

•If a script created in an earlier version of FileMaker Pro Advanced or FileMaker Pro contains an Import Records [Digital Camera] script step, the step is commented as obsolete. You can remove the step, but you can’t edit it.

•If a button references an Import Records [Digital Camera] script step, the button is disabled and the Import Records script step is commented as obsolete in the Button Setup dialog box.

•FileMaker Go only supports importing from one FileMaker Pro Advanced file to another FileMaker Pro Advanced file.

•FileMaker WebDirect does not support the Specify data source option. Users must specify a file accessible by the web browser.

•FileMaker WebDirect only supports importing from FileMaker Pro Advanced, comma-separated values, tab-separated values, DBF, merge, and Excel file formats.

Example 1

Imports information from New Product Catalog.xlsx as new records without prompting the user.

Example 2

Example 3

Sets the next serial value after importing records. Useful when Perform auto-enter options while importing is not selected to preserve dates and other auto-entries.