Contact us Blog

Setting connection properties

Setting the batch size

When importing, updating or mass-deleting records, the data transfer to salesforce occurs in batches, where each batch typically contains at most 200 records. The requirement to transmit data in batches is one that Salesforce imposes. Apsona respects this requirement, and when importing, updating or mass-deleting, it automatically breaks up the data records into batches before transmitting them to Salesforce. Ordinarily, therefore, the batch size constraint is not something you (as an Apsona user) need to be concerned about.

But there are some circumstances in which this becomes an issue. One common situation is when you are importing or mass-deleting data, and there is a malformed trigger or other back-end component within your Salesforce org that causes an error when handling batches of 200 records. The usual workaround suggested in such a situation is to reduce the batch size to a small number like 1 or 2. The disadvantage of reducing the batch size is that the import or delete operation takes a lot longer, because each data packet holds much less data. But sometimes it is worth it to reduce the batch size, simply to accommodate a back-end anomaly.

To meet this need, Apsona includes the ability to change the connection settings. In Apsona, navigate to Tools - Connection Settings, and a popup window appears, enabling setting the batch size to a smaller value, as in the screen shot below.

You can use this popup to change the batch size, which will then stay in effect until the next time you reload the Apsona window.

The default lead assignment rule

You can also use the connection properties popup to set an option telling Apsona to use the default lead assignment rule.

Retrieving deleted records and archived tasks

Another not-uncommon situation is where you need to retrieve archived activity records so that you can export or delete them. Normally these records are not retrieved by Apsona, but if you check the "Include deleted/archived records" checkbox, Apsona will use the Salesforce queryAll call to retrieve archived or deleted records, so you can then export or delete them.

Modifying audit fields (Created Date, Last Modified Date etc.)

Ordinarily, the Salesforce audit fields - Created Date, Last Modified Date, Created By and Last Modified By - are set and updated by the system, and cannot be changed by applications or users. But when you create a brand new Salesforce org into which you wish to import existing data, you might want to preserve the existing audit field values. For instance, if you are importing data from a legacy Access database, you want the created dates of your Contact records to be those in your access database, and not just set to the date of the import. You can enable modifications for these fields via Setup > Customize Interface (see this article at Salesforce). When you do this, the audit fields become updateable, and you can import data and preserve the audit field values.

Normally Apsona does not let you update audit fields, for the same reason. But if you have the above permission enabled in your org, you can set the "Allow update of audit fields" checkbox in the above popup, and Apsona will let you import into and modify audit fields.

Caveat

Apsona will not remember these settings between refreshes of the page. If you make a change to these settings, they will remain in effect only until you reload the Apsona page. But this is sufficient if you wish to temporarily change the batch size for a particular batch of deletions or data import.