We have a unique situation that we haven't been able to figure out in FileMaker 12. We needed to update a set of records in an existing database to reassign accounts to new account managers. The source data was in an Excel file, so the first thing we did was to move it into a newly created table in FileMaker. We then then set up an import script to handle the update of the target table using the "Update Matching Records in found set" parameter and AcctNo = _pkxAcctNo as the match fields in their respective tables. (Note: All fields involved in the import are defined as Text, are not calculations, and are indexed.)
After running the import, we discovered that about 25% of the records that should have been updated were not touched. We thought there might be an issue with the source data, so we did a Replace Field Contents of the AcctNo field to clean up any stray characters like a carriage return, etc., but the import still partially failed as it had before. We then picked out a couple of records where the import failed, copied the field value from the _pkx_AcctNo field in the target table and pasted it into the AcctNo field in the source table and ran the import again. The import on those records still failed.
We then set up a relationship between the source table and the target table using the two fields that were used as the match field in the import -- AcctNo and _pkx_AcctNo. Even though the import failed to recognize the match, the relationship set up between these two fields worked 100% of the time. While this will allow us to update the records, my concern is that there is an issue with the importing of matching records that is causing it to sometimes fail without reason or warning.
Has anyone else seen this? Is there a reported or unreported bug for import matching?