I would look at the data. Is it the same 572 records that are not importing? Are you updating or adding data.
it's possible that the Excel data contains Return characters, and FM is interpreting them as new record indicators. Two returns in a row would make a blank record; but then, you should have more than 6,232 records imported.
'Twas just a thought.
1 of 1 people found this helpful
I sometimes (perhaps usually) find it easier to first open an Excel file in FM and then import from there. This middle step gives you an opportunity to check the data as FM data, and can enable you to spot issues that may be present. It may be worth trying that and examining the data there before importing into your destination solution.
Interesting--when I open the Excel file in FM all the data is there. Does that help troubleshoot the source of the problem at all?
Maybe start by carefully examining the first iteration of a funky record, original and import.
Maybe, from Excel, try to export a .csv or .tab file and examine that same first iteration.
Yes, a lot. To chase it down, as suggested by David, find a record that is OK in this file but did not import originally, and carefully examine the data. If you find something see if the same thing is repeated in other records that failed to import. It may be carriage returns, it may be some unusual character (e.g. a fraction or some such) but there's likely to be something different. Once you find something that you think might be the cause, check other records that did import OK looking for absence of this. You should be able to isolate the issue fairly quickly I'd have thought.
Alternatively, you could now simply try to import into your destination file from this FM file and see if the data that failed to import direct from Excel now imports correctly.
Also check any validation of the FMP target fields; if the incoming excel data fails FM field validation tests, records may fail to import.