Hi
Is there a way of blocking the entire export of a batch to SQL database when one item results in export error.
For example I have 10 items in a batch. I export them all to database. One item has an error, meaning only 9/10 items arrive successfully in the database. In other words the erroneous item is automatically skipped because it failed.
Is there a way of preventing ALL items from arriving into the database. I need to have 0/10 successful whist the error item is fixed and a future export will always be 10/10
Im using Flexicapture 11.
An example error would be " User defined export target value: '...' Not all pages processed correctly"
I'm not looking for a solution to the error itself. Just a way of blocking export of all items of a batch.
Thanks
Richard
Comments
7 comments
Hello,
Please enable the “Process whole batches” checkmark if you use the simple workflow or “Wait for all documents of a batch” checkmark if you use the advanced workflow in the project properties to prevent export to database the batches that contain errors.
Hi Ekaterina
Where do I find these options? I cant find them anywhere, and I don't have the ability to create advanced workflows.
I've also noticed that my version of flexicapture 11 exports items 1 at a time, where when I used to use Flexicapture 10 and 9, it would export as one big group at a time. Is there a way of configuring to export as a group? My thinking that if 1 item in the group fails in export, the whole group will be stopped.
Thanks
Hello,
There is special event handler "Batch integrity check" that is used to decide if the whole batch could be exported.
You need to check if there are any documents containing errors in the batch, and if yes, then set
CheckResults.CheckSucceeded = false;
CheckResults.ErrorMessage = "Found at least one document with an error";
I have tried this and it doesn't make any difference. All items in my batch are still getting exported regardless.
I have also tried using the script:
for(int i = 0; i < CheckResults.Batch.Documents.Count; i++)
{
if(CheckResults.Batch.Documents[i].HasErrors)
{
CheckResults.CheckSucceeded = false;
CheckResults.ErrorMessage = "Found at least one document with an error";
break;
}
}
Cheers
Richard
Hello Richard,
Please send us your project with typical normal and erroneous documents so that we reproduce the issue on our side.
Hi,
For my business's security reasons I cant send any projects. Basically my error is a field that is set up in the document definition to have a maximum length of 500, and a red flag.
So when a doc is scanned and that field for example, has a length of 642 characters, the red flag appears.
The doc and field still manage to be exported, despite there being an error flag and scripts saying "if you find an error flag, gonnae no export"
running a batch integrity check overlooks an error flag too, so I don't think its to do with export.
Thanks
Richard
Hello Richard,
Please check your export settings in the Document Definition. The “Documents contain no errors” line in the “Documents condition” pop-up list should be chosen to prevent exporting documents with errors.
Please sign in to leave a comment.