AnsweredAssumed Answered

Import.log should record successful record imports and specific errors for unsuccessful imports

Question asked by PaulSt on Nov 19, 2010
Latest reply on Dec 14, 2010 by TSGal

Summary

Import.log should record successful record imports and specific errors for unsuccessful imports

Product

FileMaker Pro

Version

11 Pro

Operating system version

Mac OSX

Description of the issue

The Import.log should always record successful record imports and specific errors for unsuccessful imports. This would help in tracking down import errors. It would provide a record of good imports too. Right now, the import log does NOT record imports into existing files. It does not record specific record import errors either.

Steps to reproduce the problem

Import new or updated records from a file to an existing DB file.

Expected result

1. All successfully imported records should be listed in the import.log with date and time stamps.
2. All unsuccessfully imported records should be listed in the import.log along with a specific and helpful error message as to WHY the import failed and with date and time stamps.

Actual result

Nothing is recorded.

Workaround

NONE!!

Outcomes