Apsona's document and email merge tool doesn't have a specific record limit enforced, but you can hit limits or errors when running large data sets or using large document templates. Below are some things to consider as you design large merge actions.
- Part of the benefit of Apsona is that it's designed to get passed some of the limitations enforced by Salesforce. Though Apsona display's as an app in Salesforce, the code that Apsona uses for its operations is technically run within the browser, not within Salesforce. As a result, Apsona can avoid some of the enforced limits of Salesforce. But it does depend on the computational power of your browser. Some browsers have a higher capacity than others. Our understanding is that Firefox and Safari have the highest ability to compute large sets of data. So if your merge action continues to process but never finishes, or get's 'stuck' you can experiment with one of the more powerful browsers. Another trick you can try is reducing your browser tabs down to just the one running the merge action. This focuses all of the browser's compute on the task at hand, and increases the likelihood of finishing the large merge action. This article has more about this topic.
- If your merge action is sending emails, it's important to note that Apsona sends emails through Salesforce's email engine. This means that it is subject to Salesforce's limit of sending 5000 emails per 24 hour period. Our understanding is that when this limit is reached, Salesforce batches and stores the remaining queue and sends the emails after the 24 hour period passes. We can not guarantee Salesforce's performance with large batches of emails and once Apsona packages and sends a set of emails off to Salesforce, our tool has no control of how Salesforce manages those emails. Do confirm the behavior and limitations of Salesforce regarding email behavior. Apsona can not send emails through a 3rd party email tool. If you need to confirm whether an email has gone out through our Document and Email merge tool, try requesting an email log in Salesforce Setup.
- Salesforce does enforce time limits and SOQL query limits that Apsona must abide by. When Apsona gets an error from Salesforce it displays it to the user when it can. For more information on Salesforce limits:
- This apsona support article and this article both provide best practice tips on how to increase success with larger operations in Apsona. These 2 articles are specifically written within the context of our Dedupe tool, but many of the suggestions apply to general Apsona use.
- If you are concerned about running a merge action on a large data source you can split up your data source in a variety of ways to essentially run your merge in 'batches'. Here are some ways to accomplish this:
- Use a filter to split up your data. For example, Apsona treats letters like numbers in its filters. You can create a filter like "Account Name is less than L" This will reduce your report results to all Accounts whose name starts with A-K. You can then adjust your filter to be "...at least L" to run the rest of the records. Or you can create a date filter and use it in the same way
- You can shift+select rows within an Apsona report to run only certain rows of a data source.