Skip to main content

Why didn't my Scratchpad update save to Salesforce?

Learn why a change made in Scratchpad may not be reflecting in Salesforce

Scratchpad updates Salesforce in real-time via API. If a change isn't saving, one of the following is usually the cause.

Updating the incorrect field


Salesforce often has multiple similarly named fields - for example, "Next Step" and "Next Steps" - and it's easy to add the wrong one to your view.

If you're updating a field that isn't the one your team uses in Salesforce, the change won't appear where you expect it.

To fix this, check which field your Salesforce admin has configured for your team, then update your Scratchpad view or tile to use that field.

Updating a field on the incorrect object


When adding fields to a view, Scratchpad shows you which object each field belongs to.

For example, "Next Step" may appear under both the Opportunity and the Account as a cross-object field - updating the Account version won't update the Opportunity record.

Salesforce is rejecting the update


If a Salesforce validation rule or required field condition isn't being met, the update will fail and Scratchpad will display the Salesforce error message.

Address the condition Salesforce is flagging and try again. If you're unsure how to resolve it, reach out to your Salesforce admin.


Still having trouble? Chat with us by clicking Help in the bottom-left corner of Scratchpad, or reach out to [email protected].

Did this answer your question?