Hi everyone, I hope you have been having a great week, and just a couple more days to the weekend!
I have a Flexicapture 12 project wherein I am OCR extracting 10-odd fields from a form, comparing a unique key to a database, and returning 25-odd fields for verification from said database.
To achieve this, I have used:
- Dataset (updates every 1 hr, 'cache data' checked, 'operators can add records' checked, 'operators can edit records' checked).
- Database check rule with field links ('Field where to save record ID' is blank).
Now, the field links are working, and I am getting the correct data returned (it is actually very useful, previously I was prepared to script the db connection and query myself before stumbling onto this feature). However, the returned data is editable but not saveable.
What I mean by this is that the fields are coloured light blue/grey, and I can select and then edit the value in the field. ABBYY will even give suggestions on which values it thinks I am trying to find. However once you press Enter or Tab out of the field, the value returns to the original as per the field link.
What I want to see happen is:
- Verification starts.
- Field links are populated in the verification form.
- Operator checks all the field link values and all are ok except for one field.
- Operator edits that field to the correct value, saves changes, and closes batch.
- The newly edited field value is exported as an index OR the newly edited field is written back to the original database from which the dataset has been created.
Is this possible? I am hoping it is just a simple config button I overlooked :)
Thank you all for the help so far, this forum is a fantastic resource.
Regards,
Lee
コメント
3件のコメント
Hi there folks,
I have an update to the question above. The same behaviour applies when I use a script rule to populate a field. E.g.:
me.field("abc").value = "Hello There!"
I can change the value from 'Hello There!' to something else, but as soon as I press Enter to verify that field, it changes back to 'Hello There!'. Is there a way to make it populate only once, when the verification loads the batch?
Thank you :)
Possible solution.
Add another set of fields duplicates of fields from database lookup rule.
And then for this fields create script rule that would be something like this
if (string.IsNullOrEmpty(Context.Field("NameOfField").Text)) {
Context.Field("NameOfField").Text = Context.Field("NameOfCorrespondingFieldFromLookup").Text
}.
If you hide (don't show them on verification) fields from database lookup it would be what you want.
Hi Kostya,
Thank you very much for your reply. I was thinking along those lines as well, and alternatively to create a custom action that will set the primary lookup field to nothing when clicked.
I notice that once the primary lookup field is empty, all the corresponding retrieved values will remain but can then be edited, verified, and exported. So the flow is:
1. Create duplicate field that will hold same value as primary lookup field.
2. Create custom action that will
a) Move value of original primary field to duplicate field
b) Empty the original primary field
3. This causes the rest of the lookup fields to be editable, and I can retrieve the original lookup values if I type in the original primary lookup field if I wish to.
4. Export the duplicate primary field along with the edited lookup fields.
Thanks once again for your suggestion, I think I have at least 2 ways of doing this now!
サインインしてコメントを残してください。