Thank you! That's a good suggestion. I have not looked into possible options for automating line-drawing, but that sounds like a good step to take.
I think for the case I tested, the main problem was not borderless, coz when I added those in, the AI PARSE DOC still results in shifted result due to the overflowing text issue.
I also hope(?) Document AI would outperform using AI SQL in some scenarios: for instance table columns do not change but the spacing between rows are changed with time, or overflowing text in my example, etc. Using SQL to transform after AI PARSE DOCUMENT does mean some maintenance effort with time, I imagine. But I agree if both are equally taxing in maintaining then AI PARSE DOC is a better option.
Thank you! That's a good suggestion. I have not looked into possible options for automating line-drawing, but that sounds like a good step to take.
I think for the case I tested, the main problem was not borderless, coz when I added those in, the AI PARSE DOC still results in shifted result due to the overflowing text issue.
I also hope(?) Document AI would outperform using AI SQL in some scenarios: for instance table columns do not change but the spacing between rows are changed with time, or overflowing text in my example, etc. Using SQL to transform after AI PARSE DOCUMENT does mean some maintenance effort with time, I imagine. But I agree if both are equally taxing in maintaining then AI PARSE DOC is a better option.