Dynamic Record Cloning
I’m building a custom cloning functionality that needs to meet a few objectives, most important of which is being dynamic. I don’t want to build these out for each object in our instance.
I’m building a custom cloning functionality that needs to meet a few objectives, most important of which is being dynamic. I don’t want to build these out for each object in our instance.
I think we’ve all been guilty of hardcoding URLs at some time – I tend to do it when I’m whizzing through some development and I’m too in the zone to do things properly. I’ll just come back and fix it once I’m out of the zone.
When wanting to display a number field without a comma, I’ve generally made a number field then a formula text field to display the value as text:
If you’re not following the current battle between Apple and the FBI, you probably should be. Long story short, the FBI wants access to the iPhone belonging to one of the deceased shooters from the San Bernardino incident, and they’ve secured a court order from the United States District Court of California to this effect.
I came across something Friday regarding default record types and Profiles with no access to Object Settings (the three Chatter profiles).
Something I’m consistently surprised to see is the misunderstanding around the two different types of keys in Salesforce. Every record has two keys: a 15-digit, case-insensitive key, and an 18-digit case-sensitive key.
Another iteration of my portfolio/blog/whatever. I’m sorry, all the .NET stuff is gone. It’s backed up somewhere, it may make a return someday, but please don’t hold your breath. So, what can you expect here? My passions. Salesforce. Music. Fitness. Maybe some friends and family. But mostly Salesforce. Everything else will be just to give you a glimpse into who