Troubleshooting

My accounts imported but none of my balances are there?

When accounts are imported, but the account balances are $0.00, the column in your spreadsheet that relates to balance may not have been mapped to "Claim Amount"
By |December 14th, 2018|FAQ, File Importing, Troubleshooting|Comments Off on My accounts imported but none of my balances are there?|

SimplicityCollect Alert: ERROR – Parameter ‘custom_field_X’ has already been defined.

This message will appear on a Results File after an import attempt using the Account Importer tool (or one of the various update tools). "Parameter" refers to the column headers in the file you are using. This error specifically means that two headers have the exact same name. For example, you may have two columns in your spreadsheet that say "Debtor Phone".
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: ERROR – Parameter ‘custom_field_X’ has already been defined.|

SimplicityCollect Alert: WARNING – No data elements found mapped for updating

Double-check your file to make sure there are at least two columns for mapping, and the second column has data in at least one cell to map.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: WARNING – No data elements found mapped for updating|

SimplicityCollect Alert: Imported 0 of 0 accounts. Error: There was a problem reading the Excel File. External table is not in the expected format

We recommend that you open the file, copy and paste the data to a new document (using the mouse, not CTRL+A to select all), double-check the data looks correct on the new file, and then save and re-upload it to SimplicityCollect.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Imported 0 of 0 accounts. Error: There was a problem reading the Excel File. External table is not in the expected format|

SimplicityCollect Alert: Debtor Add Error – Data too long for column ‘ssn’ at row 1

Sometimes this can happen if other information is also being stored in the SSN field, such as a 2nd possible SSN for the debtor, another SSN for their spouse, or information/notes pertaining to their case. Remove these longer numbers (and any other inaccurate information, such as placeholders like XXX-XX-XXXX, 000-00-0000, etc.) and then attempt to re-import your file.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Debtor Add Error – Data too long for column ‘ssn’ at row 1|

SimplicityCollect Alert: Debtor Add Error – Data too long for column ‘state’ at row 1

Double-check your file for any columns related to address information and verify that all states are listed with two digit abbreviations.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Debtor Add Error – Data too long for column ‘state’ at row 1|

SimplicityCollect Alert: Account Error – The given key was not present in the dictionary

You can either re-import the file and double-check the mapping (by selecting the mapping name, clicking "Edit", and making any appropriate changes), then re-save the mapping, OR you can create a brand new mapping.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Account Error – The given key was not present in the dictionary|

SimplicityCollect Alert: Account Error – String was not recognized as a valid DateTime

Double-check your file for any columns that may be tied to date type fields in SimplicityCollect (this includes stock fields and custom fields). Verify the formatting is correct, and that the dates are not placeholders or fake dates. This can sometimes happen with dates like 2/29/2000 or 0/0/1900. Once you've corrected your columns, re-import your file.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Account Error – String was not recognized as a valid DateTime|

SimplicityCollect Alert: Account Error – LQ Syntax Error

Search through your spreadsheet for each column related to phone number type fields, and remove any text you find. Then attempt to re-import.
By |July 30th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Account Error – LQ Syntax Error|

SimplicityCollect Alert: Insert New Claim General Error – Duplicate entry ‘XXXXX’ for key ‘UniqueCaseNumberIndex’

This message will appear on a Results File after an import attempt using the Account Importer tool, and indicates: 1) That you are mapping a column to SimplicityCollect's Account Number field, and 2) that an account already exists in SimplicityCollect with that specific Account Number.
By |July 27th, 2018|Error Messages|Comments Off on SimplicityCollect Alert: Insert New Claim General Error – Duplicate entry ‘XXXXX’ for key ‘UniqueCaseNumberIndex’|