Overview Brief summary: certain load file fields, when mapped directly to Venio system fields, can cause document handling issues if the source data isn't consistently populated.
The Problem
- Load files often contain fields like FileType, FileSize, and Extension
- These fields may be populated for some records but blank for others
- When mapped directly to Venio's built-in fields, blank values are taken as-is
- Result: Venio treats blank FileType as "Unknown," triggering errors like "Selected Document Not Supported" when viewing the document or not able to send the files for html conversion
Affected Fields
- FileType
- FileSize
- Extension
4. Root Cause Direct mapping overrides Venio's own computation logic. Venio normally derives these values from the actual native file during processing, but mapped values take precedence — including empty ones.
5. Recommendation
- Before mapping, review the load file for completeness in these fields
- If values are inconsistently populated across records, do NOT map these fields to Venio's built-in fields
- Instead, map them to custom fields if you need to retain the original load file data for reference
- Let Venio compute FileType, FileSize, and Extension natively for accurate, consistent results
6. Document Type Identification — Import Method Differences
- VOD imports: Venio automatically computes document type; no additional configuration needed
- Console imports: On the "Document Type Identification Fields" step (Step 11/20), select "Use imported native file to identify document type during import" instead of relying on mapped fields from the load file
Pre-Upload Checklist
- [ ] Check FileType, FileSize, Extension columns for blanks/nulls
- [ ] If any blanks exist, unmap these fields from system fields
- [ ] Map to custom fields instead, if retention of original values is needed
- [ ] For Console imports, confirm "Use imported native file to identify document type during import" is selected
- [ ] Proceed with import
Comments
0 comments
Please sign in to leave a comment.