ML Extractor bounding boxes are all displayed on the first page of the document

Hello everybody!

I am facing the following issue while using a custom ML Extractor to extract data from a multi-page PDF - every bounding box appears to the first page of the document rather then the page where it was found.

I used the DocumentUnderstanding model, version and I trained it with 10 invoices labeled using the Data Labeling functionality from the AI Center. The training documents are also multi-page PDFs. I checked the generated data used to train the model and each bounding box is found on the right page, therefore it seems like the problem was not in the labeling stage.

The ML Skill was deployed and I am using it inside a Data Extraction Scope (see DU Framework). Checking the extraction results I found out that the bounding boxes are indeed all set to page “0” (first page).

Any idea why this is happening?
Is this a known behavior or rather a bug?
Did any of you face this problem and know a work-around?

P.S. The data extraction works good, only the bounding boxes aren’t where they should be.

1 Like

Hello @alins!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly