The field in question has been set to auto-enter serial numbers, correct?
- When you import records, just after you finish mapping your data to specific fields in your filemaker table, you click a button named "import".
- A small dialog pops up labeled "Import Options".
- There's a check box in this dialog labeled "Perform Auto-Enter Options while importing"
- Select this check box and click Import
- Filemaker should now assign a unique serial number to each imported record
See, I knew it would be super easy! Thanks for pointing out something I should have seen myself.
how do you add this step to a filemaker script?
You'll find a script step for the same process in your script editor. When you add it to your script, check the items that appear in the script options section at the bottom of the editor.
Select perform without dialog if you don't want the user to modify the import.
Click specify data source to select the file from which you want to import.
Click Specify Import Order to bring up the same exact dialogs I've described above to map fields and enable auto-enter options.
Warning! Scripted Import Records steps can often be dangerous if you add/remove field definitions!
See the following link for more on this bug:
Thanks alot man! While in specify fields i hit "OK" and then was presented with the Import Options window where i checked the box for "Perform auto-enter options while importing (mod date, serial number, lookups, etc.)."
Appreciate the help!
I have the same problem... EXCEPT...I DO choose the "Perform auto-enter.." function....
However..my results are --- NO RECORDS get imported...BUT..it uses up the Serial Numbers in the next sequence.
I have to go into DEFINE DATABASE and reset the serial numbers back.
Picture of error window after I attempt to import. NEVER in all my years have I had a problem importing records.
Enabling that option, enables all auto-enter options so check to see what else may be getting auto-entered and check to see what validation rules are in place. One way you could get this result is if you have a field set to only allow "unique values". If your import adds new records to your table that match existing values in this field, they will be blocked from being imported.
I thought that might be it..but I'm not importing any previous IDs from the other records..I'm treating them as new.
ALSO..I've also exported to .tab file and tried to import that...they still wouldn't import from a .tab.
So the current table has fields that are possibly set to only allow "unique values??"
I'm pretty sure I only use that for the key felds..but I will double check.
Get back to you!
Check for all your validation rules. Other validation rules besides Unique values might be keeping the records from being imported.
I can't see anything that would give me this problem. I'm not doing anything different that I've done before.
Plus..I'm not even importing more than 40% of the fields that already exist. I removed any fields..that are not absolutely necessary..and they are really simple like COMPANY NAME, FIRST NAME, LAST NAME...
The only thing I can think of is that some of these fields are using "Auto-enter Data" when a new record is made. The First Name field pops up FIRST NAME..in the field automatically for the user.
Is there any other configurations of the Database file as a "whole"..that might prevent it from importing?