"FileMaker Pro no longer imports data from fields that were added or changed after field mapping was defined in the Field Mapping dialog box. Data is imported only from fields specified during the original import mapping."
In the past you could create a table with, lets say, 15 fields and then create an import script to bring data into that table from another database.
One day you add a new field to the table. When you next run the import script your data is imported to the wrong fields because the field maps have changed. There is no warning and it creates a big mess.
Now with v12 you are able to add new fields without affecting scripts that contained import script steps. This is great news.
1 of 1 people found this helpful
I've alwys understood that import field name matching is resolved at runtime. FMI now seem to be saying that isn't the case any more, although it still seems to work that way in my example. Can anyone explain how, and in what circumstances the behaviour of FMP 12 has changed?
FM12 fixes a bug relating to importing. This bug did not affect imports using "matching field names" so you were immune to it. It only affected imports that relied on the field order in the imported file.
Thanks for the reply Malcolm
For custom field selections that's my understanding as well. However it doesn't clarify whether or not the change applies to field name matching. FileMaker's notes suggest it does, what I've seen suggests it doesn't. That's what I'd like to clarify.
Do you know if that's documented by FMI anywhere so I can pass it on to a customer?