1 Reply Latest reply on Nov 18, 2008 7:06 AM by TSGal

    defining a new field messes up imports



      defining a new field messes up imports

      Description of the issue

      I just hit on another serious bug with importing, and I have tested in 8.0  8.5 and 9.0 -- it has been around a long time!! If you script an import from one FMP table to another (one or two files makes no difference), and then define a new field in the source table, FileMaker will auto-map the field as a new source field for that scripted import, so long as it can find an as-yet-unmapped field in the target table. yikes. I take it that scripted FMP-to-FMP imports are just completely not to be used? gaBby

        • 1. Re: defining a new field messes up imports



          Thank you for your post.


          Our Development and Software Quality Assurance (Testing) departments are aware of this issue.  If you are going to be adding fields after creating scripts, you will run into this problem.  Once you have your schema finalized, then update your scripts.



          FileMaker, Inc.