Import error handling should be more efficient

When importing a file, errors are only done sequentially; therefore, if there are several errors, it takes several attempts before you will finally figure out which ones you need to fix. Once it finds an error in any one column, the import seems to stop. Consequently, I had to import the same file over a dozen times before I could finally get through all of the requirements. For example, if you didn't have all dates in YYYY-MM-DD, the first error you get is that it couldn't parse or that the year had to be 4 digits. So, even if the date was formatted as MM-DD-YY and you got the years had to be 4 digits, the next time you went back through, you got the format error of YYYY-MM-DD. Then, if one value didn't match a list value, only on the next import did you find that issue. Then, created by is a required field. I had it as null; there is no documentation that says is is required. I had assumed it would take my user ID if it was blank.

In addition, even if you headers are EXACTLY the same name as the value to map to, the import cannot recognize. Thus, I have to map the fields each time. When it took more than a dozen tries to get the first.

Hours fixing and remapping what should be a simple task, especially if you spend the time to put in matching headers. And, if you would surface all errors at one time, then, we can reduce the amount of time to finish a task.

If there is a header that matches an existing field, default to that as the field match.
Created by should default to the user importing if none defined.
File should be scanned and surface all errors before processing instead of hitting one error and stopping.