23-07-24 08:21 PM
Hi Team,
I am trying to read the table data which is spread across the multiple pages, my requirement is i want to read only the alternate rows from the table is there any way to achieve this using the new Decipher version?
when i am reading it i am getting the entire table data. See the below images.
I don't want the agency discount details row to be taken as 2nd row, 2nd row should be taken from the ID.
How to tell the decipher to pick the 2nd row from a specific position?
Answered! Go to Answer.
29-07-24 08:26 AM
I've seen similar issues when some users have been trying to read address fields where the number of lines is variable. The only methods I've seen help in the current version are using the lists functionality, where the potential values are limited and known (these can be stored in a sql db, see validation lists). Or you could see if a particular Format Expression (Regex) helps, that is if the format has some consistency.
We're currently working on an improvement to this, due in our next release due out Aug/Sep 2024.
Thanks
24-07-24 08:27 AM
Hi Salman,
That's quite a tricky table as each row is effectively two rows with separate rows of headers. Have you tried using the misc. parameter "UTD = true"?
You would need to reset your training data to test, but it may give improved results after training 2/3 documents.
Thanks
24-07-24 01:33 PM
Hi @Ben.Lyons1
I already tried with the misc parameter UTD = true for all the table fields. The issue i am facing here is sometimes in the invoice 1st page itself contains 2 rows (Two Placement ids are available in 1st page itself) as shown in the image below
In another type of invoice it contains only 1 row in the first page like below
In this case decipher is considering the internal row (Header-- Agency Discount) as the actual second row and extracting those values.
Finally, when there are two rows in Page 1 its extracting correct data, if incase the page1 doesn't contains 2nd row it is treating the internal row as the actual second row and extracting the wrong data.
Is there any option in decipher to handle this?
Is there any option/ way based on the text mentioned can we extract the data like below (Key Value Pair feature).
Please keep in mind the row no's are dynamic
Thanks
Salman Shaik
24-07-24 01:37 PM
Hi Salman,
There's nothing specific in Decipher for this scenario, I can't recall having ever seen a document like it.
The only alternative I can think of is using the sub-table misc parameters or just extracting all the rows and editing the data in your Blue Prism process.
Thanks
25-07-24 12:48 PM
Hi @Ben.Lyons1
I kept extracting the entire table data as my last option, now nothing is working so i have to use that option.
I will let you know if any issues are there, thanks for your suggestion.
Thanks
Salman Shaik
25-07-24 04:00 PM
Hi @Ben.Lyons1
I came up with a new issue for you i have a field for campaign which may contain the data in 2 or 3 lines (dynamic). For one invoice if we are selecting and defining the region in another invoice its not able to detect all the lines properly because the no of lines are different, i trained with 6-7 invoices but still if one invoice works other is not working Properly.
In the below invoice it contains only two lines so its including the campaign id aswell for the campaign field.
Campaign Flag Type is Multiline, Exclude keywords is used
Campaign Id is using keywords, Exclude keywords, StrictPositionAnchorText (Misc Parameter)
How to handle this one?
26-07-24 08:06 AM
Hi Salman,
This is very difficult to advise on without the full document, training performed and DFD. However, things to consider are:
Thanks
27-07-24 06:19 AM
Hi @Ben.Lyons1
I was able to extract the entire tabular data and handling at the blueprism level, the fields Campaign, Campaign Id are completely separate fields not related to any table.
See the below image for clarification
I am trying to extract these fields. Sometimes the campaign field contains two or three lines of text. In this case it's failing to identify it.
Can you suggest on this
29-07-24 08:26 AM
I've seen similar issues when some users have been trying to read address fields where the number of lines is variable. The only methods I've seen help in the current version are using the lists functionality, where the potential values are limited and known (these can be stored in a sql db, see validation lists). Or you could see if a particular Format Expression (Regex) helps, that is if the format has some consistency.
We're currently working on an improvement to this, due in our next release due out Aug/Sep 2024.
Thanks