DU error while classifying sample invoice documents

Help Activities
, ,
1

Hello.
I’ve just started to practice with Document Understanding feature.
I brought some sample Invoice PDF files from https://acme-test.uipath.com/ (Type=WI3 Items)
I am using enterprise license and do have API key for AI Units.

Since there were two different color themed invoices from the website, (purple and blue invoices)
I thought it’d be a good point to practice classification.

image
image920×498 35.3 KB

image
image865×484 35.8 KB

Purple Invoices had their ID Number tagged as “Invoice No.”
while Blue Invoices had its tag as “Invoice ID:”
so I have prepared the Keyword Based Classifier as follows:
image
image799×462 99.2 KB

https://docs.uipath.com/activities/other/latest/user-guide/classify-document-scope
and I looked at official documents and UiPath Academy to Configure Classifiers,

but none of them had any keywords specified in their examples, so I also did leave them empty.
image

However, I am getting following error:
Classify Document Scope: Method not found: ‘Void UiPath.DocumentProcessing.Contracts.Results.ResultsValueTokens.set_TextType(UiPath.DocumentProcessing.Contracts.Dom.TextType)’.

If I try to write any keywords into those Keyword Based Classifiers, it will just throw no matching results at all.

Any clue would be nice :slight_smile:

Thanks in advance.

2

Did you print the text using writeline after digitizing?

3

Yes I did and it did digitize properly.
I was able to see all texts yet it had the issue while classifying…

4

Hi @jspark ,

Is it possible for you to provide a screenshot of the Dependencies used along with their versions ?

5

@jspark

Please check this

image
image828×815 160 KB

https://docs.uipath.com/activities/other/latest/user-guide/classify-document-scope

Hope this helps

Cheers

6

@jspark ,

It does seem that a similar post having the same error was solved by updating the dependencies to the latest stable versions.

Could you try performing the same and let us know if it doesn’t work.

7

It was the dependencies.

I updated every packages’ version from latest preview to latest stable versions, and the error disappeared.

Thank you.

1 Like
8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.