CVL imports - improve error handling

Who would benefit?	Partners and Customers
What impact would it make?	Allow for a more user friendly way to manage the import of large and complex CVL data sets.
How should it work?	We recommend creating error messaging via the import status report. This report would be generated in the Control Center after a CVL list is uploaded. O this could also mimic the features that exist in the import wizard in Enrich such as pre-import validation.
Why is it needed?	CVL data is product data. The difference is that the upload of CVL data must adhere to strict criteria. When that criteria isn't met or is incorrect, the information is rejected. Providing detailed feedback to the user will make CVL management for efficient.

Some examples include:

Import file includes key id values with special characters that are not allowed
- Error message: Display the special character(s) which are not allowed
Import file includes key id values exceeding number of allowed characters
- Error message that displays values of the failed key ids
Import file includes parent key ids that has been removed or are incorrect
- Error message that displays failed Parent CVL key ids
Import file include a key id that already exists
- Warning message of the CVL key that already exists
File that exceeds the import limit or includes empty rows with spaces or special characters that exceeds the 999 row limit
- Error message: File contains more than 999 rows. If the file looks correct, check for blank rows at the bottom of the spreadsheet
- Alternately, allow files with more than 999 records to be imported.

RELATED IDEAS