Performance: Minimizing cross doc table imports

1

Hi All, just wondering if anyone knows - when doing cross-doc table imports, is it a good practice for larger tables to setup a view in the originating doc of a table to only contain the columns that you need to import?

We’re noticing that our document search time using the regular search bar is going up, and I’m guessing that by minimizing the size of our cross-doc imports, we should be able to lower the amount of data in the document.

2

I’m not sure about performance but another argument for doing it this way is data privacy. Maybe not an issue in the context you’re working in, but it can be good to send over just the columns (and even filtering to send certain rows) that will be needed.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.