When you are going through loop in a trigger you don’t have access to Record Type name like RecordType.Name, you can only access Id as RecordTypeId
To get code coverage of a class or all classes you can use Tooling API on objects like:
- ApexCodeCoverage – contains coverage per class per test class
- ApexCodeCoverageAggregate – contains coverage per class for all test classes
- ApexOrgWideCoverage – contains coverage overall for all classes in the org
Salesforce provides a native way to use country and state values in Account and Contact address fields. It’s very useful on page layouts. But what if we want access that values and use them in our Apex Class and Visualforce Page?
Today I came across a problem with accessing Owner custom fields (for the User object I had several of these fields).
I only could access few standard fields like Owner.Name, Owner.FirstName without problems.
SELECT Id, Name, Owner.Name, Owner.FirstName, Owner.Store_Name__c FROM CustomObject__c WHERE Id = :ourId
ERROR at Row:1:Column:74
No such column ‘Store_Name__c’ on entity ‘Name’.
When we create an application that uses multiple languages, we use translation workbench is the purpose of the translation. Salesforce takes care of the translation user interface, so we always got the right language. But to get the data (picklist values and record type names) in the appropriate language in Apex and VisualForce – we have to do it ourself.
Files associated with a record can be stored in 2 ways: as an attachment (in the Notes & Attachements related list) as well as Salesforce Content (using Chatter Files).
Recently I had a task to create Visualforce pages, which put on the Page Layout as inline Visualforce showed the files posted by Chatter Files associated with the record. Adding files was carried out by the Chatter. Assigning Topics to an entry in Chatter allowed to filter files by this as a category.
Working as a Salesforce Developer meet with the various problems of both a configuration and developing.
One of the problems was when I created a Master-Details field on custom object to another custom object. When I created a record on the child, I coulnd’t edit value of this field.
As it turned out this inner Salesforce limit (no edit option in the Master-Detail field regardless of the permissions to read / write). Fortunately, with the Summer 12 release we can change this value. To do this, enable the “Allow reparenting” in Master-Detail field definition. By default, you cannot “reparent” records in master-detail relationship.