Unanswered

Form processor wont recognize the table

(0) Share

Report

Posted on by ebotero

I'm trying to create a model to read thousands of pages with rows of information. Ai builder is not recognizing the table, i also created a model to recognize the fields for the first rows that works but i don't know how get to iterate on each row. To add more complication the file has 2 rows per record...

I'm very new to ai builder and power apps, any help will be appreciated.

This is the result i need for each record

Name	AV	AMT bid at Tax sale	CO.	YR.	C/S#	Class	Code	Parcel Id	Description
ALLEN NETTIE HAYGOOD	520	80.82	01	00	0029	2	1	0123000220140020000000	LOT 11 BLK 4 HOMER HIGHLANDS

WWW_TRANS_01 1.pdf

Categories:

AI Builder

All responses (5)

Answers (0)

Sort by

JoeF-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @ebotero,

Thank you for reaching out.

Today for AI Builder to detect tables, these need to be have clear separators between columns and lines. It looks like the document you are trying to use does not conform to these requirements. Unfortunately without changing the document format, there's not much that can be done today.

Having said that we are actively working on improving table extraction so stay tuned for upcoming updates.
ebotero 2 on at

Like
a
(0)

Report
Copy link

Link copied!

So is there no way to have ai builder iterate ?
JoeF-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @ebotero,

If AI Builder is not detecting the table automatically, then there is no way today to manually define a table. If your table always has the same number of rows, you could tag each row as a separate field.
anothersphere 14 on at

Like
a
(1)

Report
Copy link

Link copied!

The fact that the rules around what can be detected as a table takes the AI out of AI rendering this fine for a very simple task but useless for things like real world export documentation.
JoeF-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the feedback @anothersphere, I understand the frustration. This is an area where we are actively working on so expect improvements regarding table extraction in the coming months.