'Key' column for Table Snip
In most cases where table snip is being used, rows have text split over multiple lines, which table snip incorrectly interprets as multiple rows. This issue is significant when dealing with large PDFs as each table snip has to be edited manually.
A simple way to solve this would be to have a 'key' column which the user selects, which tells table snip where to look to determine where the rows should be. For example, there might be a single date or value for each row (despite multiple text lines within the same row), and selecting this to be the key column would prevent the multiple lines from being considered individual rows.
If this key column is retained for each table snip repeated in the document, then very large PDFs could be snipped in a significantly shorter amount of time than they currently are.
Hugh Pilsworth
shared this idea