You don't have to select one of the options at this point. In fact, adding explanations to each of the three options is a huge improvement. I’m glad they changed the original middle option of "Update existing records in found set" to "Replace" (with an explanation). The "Import Field Mapping" dialog is now named "Specify Import Order" and the first thing you're prompted to do is select the type of import action you want. There are no changes to file types that can be imported, but once you select a file to be imported the changes start!
If you're importing from another FileMaker database and that database is open, you will need to control the found set in that database as only the found records will be imported. When selecting an import type of either Update or Replace, only your current found set of records will be affected so you need to either show all records or establish your found set before starting the import process. The only exception is if you change the default Target from "Current Table" to "New Table." Since the goal is to create a new table, you're essentially creating a new Context as well. Verify the current layout is connected to the appropriate destination table through a Table Occurrence. Please note, these requirements have not changed at all in FileMaker 18. Let's explore the new import features and functions.īefore we dive in, let's review a few things in order to prepare for a seamless import process. The new import dialog interface features a mix of graphics and text so it should be very easy for both new and seasoned developers to choose the most appropriate actions. 
has shown it a lot of love in FileMaker 18!įileMaker’s importing capabilities are pretty extensive but they're not always intuitive.
FileMaker's import process has not changed in a long time and so it's ripe for an update.
0 kommentar(er)
