Salesforce Insights in 5 Minutes·Issue #197·Reddit Discussions
I'm afraid of performing mass updates
Mass updates on old records really freak this person out, so they tend to avoid them whenever possible. Last task was updating 81,000 records with a new payment date, but they ended up on sick leave before tackling it. Big worry is not knowing how to be sure nothing breaks, plus no clear way to roll back changes afterward. Checking every field and value across 81k records isn't realistic, and there's also fear of hidden blockers like triggers or validation rules messing things up. Basically asking for a solid, clear approach to handle mass updates safely without losing sleep over it.
The site uses the cookies it needs to work, such as your sign-in. With your consent it also uses
Google Analytics, to count visits, and Google AdSense, whose ads fund the
extension: both set their own cookies and send your address to Google. Neither runs until you choose, and you
can change your mind at any time from Cookie settings at the foot of every page.
Which cookies, and why.
