I don't know if what you ask is possible or not but I was thinking of another way to go about this.
You could make two extra timestamp fields in your table called "Created" and "Modified" And you could set as auto enter options that one would set a timestamp when the record gets created and the other would set a timestamp once the record gets modified.
That way you can import your data and see all the timestamps of creation or modification.
I don't know if that might help you get any further.
There is no way that I know of the identify the record that was not imported.
What problem are you trying to solve when this happens?
There are several different approaches you can investigate depending on what you need to do here.
You might try an update import with the add records option or you might import into a different table and use a relationship between it and the target table to identify records that already exist in the target table. After resolving the issues produced by these records, you could then import a from this interim table into the target table.
What I'm trying to solve is getting the Product ID field name for each Record that does not get imported but skipped when using the Import Record function.
The reason why I need the Product ID for all the records that get skipped by the import function so I can check to make sure the correct part number was entered in the file.
Then perhaps importing first into an interim table so you can compare records to those already in the target table via a relationship based on part number will serve...
So is there no way to find out which row from the file that caused the error and skip?
"So is there no way to find out which row from the file that caused the error and skip?"
Yes: "Then perhaps importing first into an interim table so you can compare records to those already in the target table via a relationship based on part number will serve..."
Import the new records into an interim file (or Table). Set that table to have a relationship using:
InterimTable::ProductID = DestinationTable::ProductID
Then, for example, create a calculation field in the interim table (there are many other ways):
ExistingProductIDYesNo = If ( Count (DestinationTable::ProductID ) = 0 ; "No ; "Yes" )
Then search in the interim table for all records where this equals 'No'. That will be the new ProductIDs that do not exist in the existing table.
with the above tables/relationship, you don't need a calculation field.
You can just enter find mode and specify an * in the DestinationTable::PRoductID field to find only those records that match to an existing record in the destination table.
I would like to just be able to export the location of where the error occured instead of having to import new records into an interim file or Table?
For the FileMaker Errror that shows how many errors occured and records skipped during the record import process is there just a way to find the error file and locate where the errors occured?
As we have both said before, this is not possible. That's why we are recommending this alternative.