Purpose
This guide helps resolve database field mapping errors that occur when running Instant VOBs (iVerify), specifically when custom fields are missing or incorrectly configured in your CRM instance.
Symptom/Error
When running an Instant VOB (iVerify), you encounter a database error with messages like:
"Query Failed: UPDATE vtiger_vobscf SET cf_XXX = ? WHERE vobsid = ?"
"Unknown column 'cf_XXX' in 'SET'"
VOB record count remains at zero even though the process appears to be complete
The system redirects to an error payload screen instead of showing a success confirmation
The VOB record is not created successfully, preventing workflows that depend on Instant VOB completion from triggering.
Cause
This error occurs when the Instant VOB process attempts to update custom fields in the database that either:
Do not exist in your CRM instance
Were incorrectly configured or deleted
Have mismatched field IDs between the system configuration and the actual database structure
Solution
This is a backend database configuration issue that requires technical intervention:
Contact Dazos Support immediately - Include the following information in your support ticket:
The specific error message from the payload screen
The VOB record ID where the error occurred
Screenshots or a video of the error occurring
Patient/record information where you can reproduce the issue
Provide reproduction steps - Our development team will need to:
Investigate the custom field configuration in your instance
Verify which fields are missing or misconfigured
Update the database schema to match system requirements
Test the fix with your specific use case
Test the resolution - After our team implements the fix:
Run an Instant VOB on a test record
Verify that the VOB record is created successfully
Confirm associated workflows trigger as expected
Temporary Workaround
While the database field mapping issue is being resolved:
Use the standard VOB process instead of Instant VOB if workflows are not dependent on the Instant VOB type
Export PDF directly from any existing VOB records to access verification information
Avoid repeatedly attempting Instant VOBs on the same records, as this will continue to generate the same error
When to Contact Support
Contact Dazos Support if:
You see database field mapping errors when running Instant VOBs
VOB records are not being created despite the process appearing to complete
You receive "Unknown column" error messages in the payload screen
Critical workflows dependent on Instant VOB completion are not triggering
⚠️ Important: This is classified as a Priority 1 issue since it prevents core functionality. Our development team will treat it with highest urgency.