Home / Salesforce / Page 19

Salesforce

Force.com Licensing – Know Your Options

July 2017 Update: Force.com has been replaced with App Cloud licensing options. Learn more about the change and how to transition here. In most organizations, not everyone needs access to full-blown CRM functionality.  There might be users who never touch Leads or Opportunities, need read-only access to just Accounts and Contacts, or maybe a custom

Force.com Licensing – Know Your Options Learn More ❯

Working with The Force.com IDE and Subversion (SVN)

The Force.com IDE is one of two IDEs that we use here at Soliant Consulting. The other one is MavensMate. I personally prefer the former at the moment, mainly because of the Synchronize perspective, which, as mentioned below, can be very useful in different situations. Some of my colleagues prefer the latter, so you may

Working with The Force.com IDE and Subversion (SVN) Learn More ❯

SFDC Best Practice for Child Relationship Names

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 ❯

On-View triggers in Salesforce (trigger for Opportunity Contact Roles)

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 ❯

Scroll to Top