Import Records And FileMaker Script Breakage

From Dwayne Wright PMP
Certified FileMaker Developer

TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

Many of us love the copy and paste script feature in FileMaker Advanced but it isn’t always fool proof. In most cases, if the pasted script has problems, you can quickly see it within the script. However, that isn’t necessarily the case with the Import Records script step.

When you paste a script from one file to the next, if FileMaker doesn’t see a layout, field, sub script, etc... that it needs, you will generally see an [unknown] tag somewhere. However, if a field is missing from an import order, it can throw off a portion of or your entire import order in the script. You don’t see this on the surface glance of the script, so it can appear to be just fine.

I have heard it mentioned that adding new fields or deleting fields in the source table can affect your import field mapping process as well. So the advice of testing all imported or pasted script steps holds particularly true if the scripts themselves have the Import script step within them.
More info about the author and FileMaker in general, contact me at

© 2008 - Dwayne Wright -

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.