Please declare a unique Child Relationship Name! Think of it as just as important as the Related List Label (which is what your Salesforce users see). The Child Relationship Name is what developers see when writing sub queries in Apex. Salesforce uniquely names Child Relationships if you don’t. However, those names are generally useless for […]
SFDC Best Practice for Child Relationship Names Learn More ❯
Native Opportunity Limitations One current limitation with Salesforce.com native Opportunities model is the inability to have a trigger on the Opportunity Contact Role object. Say you have built a custom Opportunity rollup or scoring mechanism of some variety and it relies upon what/who the user selects in the Opportunity Contact Role area: how will you
On-View triggers in Salesforce (trigger for Opportunity Contact Roles) Learn More ❯
If you want to create a new Lead via Visualforce or web form with Apex it’s very possible you could overlook the Assignment Rules. As you might know, it’s not even always obvious on the native Lead creation layout. Notice the lower left corner checkbox in the screenshot below. To enforce Assignment Rules in Apex
Setting Lead Assignment Rules with Apex Learn More ❯
You can send emails programmatically in Salesforce Apex, but if you’re not careful you can hit the measly governor limit of 10 in no time at all. You see, although your outbound email limit is 1000 with Apex, only a total of 10 sendEmail method calls are allowed in each context. Obviously the way to
How to Avoid Governor Limits with sendEmail in Apex Learn More ❯
Visualforce is SFDC’s custom mark up language and represents the view in a Model-View-Controller target=”_blank” software design pattern. Each Visualforce page is tied directly to a controller. These controllers, of course, manipulate the data in the model (database) and contain your application’s business rules. Visualforce is made up of components (standard and custom.) These are
Visualforce: Salesforce.com’s markup language Learn More ❯