nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Export Tools

Bernie Fitzsimmons

Hello, we ran into challenges exporting our annual appeal list due to the size of it. It would eventually time out and we resorted to exporting from a Query which produced inaccurate results. Are you aware of any tools/plug-ins available to use along with the Export function or instead of it? Thanks.

Find more posts tagged with

Comments

Austen Brown

@Bernie Fitzsimmons - I recommend you divide the larger exports into smaller pieces and then re-compile them in excel after they are exported. It could also have to do with the number of calculations the export needed to complete with summary information fields, take a look at those and reduce if possible. The Export area within Database View is the best option.

Faith Murray

@Bernie Fitzsimmons, seconding what Austen says. Database view will always give you the best choices for exports, as long as you use Export to produce the output fields. If Query criteria fields are discombobulating for your team, you can take your Annual Appeal list in webview, save it as a static query in database view, and link that query to your Export in database. This will provide you an identical list to what you refined in webview.

Marie Stark

@Bernie Fitzsimmons I do the same as Austen mentioned. I breakup the export into smaller exports and combine them in Excel.