"Error parsing key for this row" enhancement

StevenK

Currently when importing some transactional data into Anaplan we will occasionally get "Error parsing key for this row" for rows where bad data might be present (or data might be missing)

The error is often overly vague and requires us to compare the failed row to one that's previously processed correctly. The errors often have to do with missing numeric values where were importing nothing at all.

The enhancement request I have is: Please add to this error message which column is failing, not just the "value" that's failing. If there are 3-4 columns it's increasingly difficult to identify all of them to address the underlying issue. Either the column # OR the Column Name if the data in the action has a header, all of this information is available based on how the action was built and the corresponding Import Data Source.

GarryW

also this error messgae is populated if there is blank row, in our case, empty last row. Hopefullty import process could bypass it without show this error message

StevenK

@GarryW Common problem for us when using exported data out of Oracle Fusion BIP Report

GarryW

@StevenK similar but strange here as importing csv file which has extra line without value when exported from BI source.

Hope anaplan product team could add a tick box to ignore no value row and not trigger warning message by saying 1 failed record.