Has anyone found success using additional (secondary) tables in their IDC Document Form Definitions? We have only been using IDC/ECM for AP Invoice Automation, but are trying to find other ways we can utilize IDC. We are hoping to be able to use it to gather data from bills, but the hiccup is that some bills will have more information than others (albeit in a similar format). I was thinking I could add another table to collect different “rows” of data (that share a couple columns) and then export it as a CSV. However, when I set up the additional table, I have not been able to get it trained. The “header” fields come in quite reliably, but only one “detail” field at the most seems to be trained and pulls in fine. The other “detail” fields either pull in random information, or none at all. I’ve also marked those fields as required, yet when they are blank, the batch still passes verification.
Does anyone else use an additional table in their document form definition?