The Import Record dialogue box has a check box for "Add new records"
When I check that box I end up importing all the records in the import file rather than just the new records.
I'm obviously misunderstanding "Add new records". What does it mean?
What do you know about the records that makes them "new"? Is there a field or fields that have a date or a number above what you might already have?
In what format (CSV?) are the new records for import? Is there a way to ‘get' only records that are new before you need to import them?
Is there something in your existing records that would match 'old' records to import? Thus if there is no match, then whatever records are left in the import source would be new-to-add, right?
Sent from miPhone
There is a discussion from back in 2012 where the trick to importing new records is ensuring there is a field that somehow denotes a record is new. Considering the discussion was so old I thought it might be out of date.
You questions suggest to me that there does have to be something that identifies records as new. I’ll work on that
Kutcher Engineering & Inspection Inc.
Don't bother. You are looking in the wrong direction.
Brief clarification of terms. You import from a source file to a target table.
Import will ALWAYS process ALL the records in the found set of the source file.
If you have chosen "Add new records" that means:
Create new records in the target file using the entire found set of the source file.
It never, ever, matters how "old" or "new" the data in the SOURCE is.
Richard, Bruce answered the question.
Add new records will just create a new record for every "source row/record" (regardless of what records are "found/showing").
Read these help topics on the import process:
[NOTE: TSGal Nowhere in the Import Records help topic does it even point to the above links and they are vital to understand the process!! As many people look at existing files and study the help topics for the Script steps, it would be even more beneficial to have Import Records point to the starting overview of importing & about the secondary dialogs that may appear while this is set up.]
rkutcher I'm saying that (going beyond the Add new records):
1. IF you have some way to determine the "new" from the source, only import those records (get just the source to be only "new" if at all possible).
2. if you are not getting just "new" from the source, then you need to determine a "match", so that existing records are not imported (only updated) and the remainder are "newly" imported/added.
3. if you don't want an "update" of existing records, I use a method to temporarily import from the source and script to determine (by date and/or match fields) what would be new and create new records in the final table with just those that may be "new". (I have not given much detail on how, sorry.)
Mostly, I'm trying to get you to think about what you have and what you need to do with it. And I was asking to help us give you the answer(s) by you providing just a little more information on the Source and the Destination. Anyway, read the help topics and come on back with more question, more information, and/or what you discovered.
p.s. sometimes we try to guide you into learning a little more than you may think you need to know.
I went back to the original 2012 discussion to follow those instructions and changed the field validation of the report primary key of both the source and target tables. They are now my unique identifiers
After a few unsuccessful tries, where I learned something each time, I got it working.
Beverly’s original answer was helpful because it let me know that the 2012 discussion was not outdated. I was worried that after 6 years, Filemaker might have changed how things worked.
You may mark your own answer as Correct, Richard!
Now I should clarify my terms.
When I said “…something that identifies the records as new.” I meant a field that is unique to each record.
Once I set up the unique field the “Add new records” seems to be working and only bringing in the records that are not already in the target file.
Retrieving data ...