User's issue:
User have reported an issue with batch importing CSV files when selecting a custom column for Document IDs. Although importing the same CSV with auto-generated Document IDs works, choosing a specific column as Document IDs leads to an error: "n.charAt is not a function."
Cause:
Column types like reference and image, require custom parsers. Previously, these parsers were stored in an object with the column index as the key. However, when using a custom document ID, the explicit setting of the document ID resulted in a change to the column index reference.
Fix:
The fix involves using the column key as the key to store the parsers, rather than relying on the column index.
User's issue: User have reported an issue with batch importing CSV files when selecting a custom column for Document IDs. Although importing the same CSV with auto-generated Document IDs works, choosing a specific column as Document IDs leads to an error: "n.charAt is not a function."
Cause: Column types like reference and image, require custom parsers. Previously, these parsers were stored in an object with the column index as the key. However, when using a custom document ID, the explicit setting of the document ID resulted in a change to the column index reference.
Fix: The fix involves using the column key as the key to store the parsers, rather than relying on the column index.