AnsweredAssumed Answered

FileMaker 12 import bug

Question asked by scottworld on Apr 4, 2012
Latest reply on Apr 5, 2012 by scottworld

Summary

FileMaker 12 import bug

Product

FileMaker Pro

Version

12

Operating system version

Mac OS X 10.6.8

Description of the issue

This is a pretty large bug, and it only seems to affect files that were converted from .fp7 to .fmp12 format. I haven't yet been able to reproduce the bug with a brand new .fmp12 file created from scratch, but it is definitely there when you convert a file from .fp7 to .fmp12 format.

Steps to reproduce the problem

Here are the ways to reproduce the bug:

1. In your .fp7 file, create a script that has an "Import Records" script step in it.  The script options for this step should be set to:
- Perform without dialog
- Specify data source: Choose the same file that you are working on
- Specify import order: Import records from one table to another table within the same file that you are working on. See screenshot below for an example of what this stored import order might look like.

2. Now convert the file to .fmp12 format.

3. Open up your .fmp12 file, and delete one or more fields from the "source" table (the table which was on the left side of the import window).

4. Now go back into your script that has the stored import, choose the "Import Records" script step, and click on the button for "Specify Import Order". This is where the bug crops up: You will notice that all the fields are improperly mapped, so data is being imported into the completely wrong fields. See 2nd screenshot (in next posting of this discussion thread) for example of what this looks like.

5. You'll notice that this particular stored import is arranged by "Last Order", but the bug crops up even if the stored import is arranged by "Custom Import Order" as well.

Screenshot_1.png

Outcomes