Multi-Field Bulk Update documentation

Requirements

• A Freshsales Suite account on a plan that allows Marketplace applications. Freshsales Classic is not supported.
• For installation: an administrator who can install applications, and that person's own API key for a one-time check.
• To use the application: your login email on the application's list of people who may run bulk updates, your own Freshsales API key (Profile settings, API settings), and Freshsales permission to edit the records you change.

Installation

The installation page asks for your Freshsales account name (acme for acme.myfreshworks.com) and the login email addresses of the people who may run bulk updates, separated by commas (up to 50). Verify checks the account name with your own API key. The key is used only for that check and is not saved.

Settings inside the application: your Freshsales plan and the share of its hourly API limit the application may use (default 50%), the CSV separator, the number of records per run (default 300, at most 1,000) and the kill switch.

Using it

• Open Multi-Field Bulk Update from the left navigation. Paste your own API key and click Connect. The key stays in the open browser tab for at most 15 idle minutes and is never stored.
• Choose Deals, Contacts or Accounts and a Freshsales view. Add up to five conditions (is, is not, is empty, is not empty, contains) if you need fewer records.
• Add up to ten fields and choose an operation for each. Saved operations keep a set of fields, operations and conditions for next time (up to 25).
• Click Build preview. Check the current and new values; Download preview CSV if you want a copy. Nothing is changed.
• Type the phrase shown, for example APPLY 6, and click Apply. The progress shows each batch; Stop after this batch stops the run, and History can resume it.
• History lists the last 30 runs. Undo this run asks for the phrase UNDO and the number of records changed.

Safety rules

• Nothing is written before the typed confirmation, and the server checks the phrase again.
• Each record is read again just before it is changed; if its values differ from the preview, it is left as it is.
• The previous values are saved before the change. If they are too large to keep for undo, the record is not changed.
• Each change is read back; a value that differs afterwards (for example changed by a workflow) is reported as Saved but not confirmed.
• Only one run at a time per account. The kill switch in Settings stops every change, also one that is running.
• Undo only restores fields that still hold the value the application wrote; fields someone changed since are left alone.

Limits you should know

• Each record takes three API calls (read, change, read back). The application keeps under 45 calls a minute and under the share of your plan's hourly limit set in Settings, so expect roughly 12 to 15 records a minute. The preview shows an estimate.
• A view may hold up to 1,000 records; use a narrower view in Freshsales for more. One run changes at most the number set in Settings (default 300).
• At most 10 fields and 5 conditions per run. Relationship fields, email fields and system fields cannot be changed.