When a user says they need a field to be both required... AND optional.
(via GIPHY)
Sweet Seals For You, Always
2025 on Tumblr: Trends That Defined the Year

JVL
art blog(derogatory)
No title available
Misplaced Lens Cap
h

★
will byers stan first human second
hello vonnie

ellievsbear
🪼
PUT YOUR BEARD IN MY MOUTH
d e v o n
YOU ARE THE REASON

izzy's playlists!
"I'm Dorothy Gale from Kansas"
trying on a metaphor
TVSTRANGERTHINGS
Today's Document
seen from Australia

seen from United States

seen from India

seen from China

seen from Australia

seen from Uganda
seen from Philippines

seen from United States

seen from France

seen from Netherlands

seen from Türkiye

seen from United States
seen from Singapore

seen from T1
seen from Germany
seen from Malaysia
seen from United States
seen from United States
seen from Canada
seen from Colombia
@lifeofthesalesforceadmin
When a user says they need a field to be both required... AND optional.
(via GIPHY)
When, in the middle of an all-night deployment, you discover that you have to manually recreate 50+ fields because someone else’s code won’t allow your change set to deploy successfully.
(via GIPHY)
When a user who never offered an opinion during any phase of development or testing pipes up after you've deployed a change and says “that’s not going to work for me.” Uh..... (via GIPHY)
The relationship between an admin and users. (At least, sometimes it feels this way.)
When you have a speaking roll at Dreamforce.
When receiving a call to help a user.
When you don't have the budget to go to Dreamforce.
Right after you say "sure, I can totally do that in Salesforce. It'll take like 5 minutes." And you realize it's not possible with standard functionality.
Friday afternoon, after a long de-duping session.
When you create a complex formula, click "Check Syntax" and get the "No syntax errors in merge fields or functions" message.