Salesforce - Developer - Epiphanies
// Salesforce - Developer - Epiphanies #1: Force.com IDE is a plugin for Eclipse. A force.com project is a container that stores all metadata for a single username in Eclipse. Projects are made up of metadata pulled down from the server and stored locally. At the same time, changes are pushed back to the server. Most components from an org can be included in a project. To create a project: 1. Launch Eclipse 2. Change to the Force.com Perspective 3. Click on File -> New -> Force.com Project
// Salesforce - Developer - Epiphany # 2: One way to evaluate your code is to use the Execute Anonymous feature. If we are using Force.com IDE, we can launch Execute Anonymous by Looking for the "Execute Anonymous" tag in the bottom pane. You can resize the bottom pane, or click on the maximize icon, or double click on the tab to either maximize or return this tab to its normal size to make it easier to work with Execute Anonymous. If we use the Developer Console, we can use Execute Anonymous by clicking on the Debug menu and then select "Open Execute Anonymous Window". Execute Anonymous is a screen where you can write code and run code. This code is not saved anywhere.
// Salesforce - Developer - Epiphany #3: System.debug() is a special method that you can add to your code to generate output when code is executed to provide feedback for the developer. For example, System.debug('The value of x is:' + x);
// Salesforce - Developer - Epiphany #4: We can obtain a list of columns that a table contains by using the Developer Console by clicking on File -> Open -> Object
// Salesforce - Developer - Epiphany #5: When unhandled Apex exception occur, emails are sent that include Apex stack trace, the customer org, and the user ID. No other customer data is included. Unhandled exception emails are sent by default to the developer specified in the LastModifiedBy field on the failing class or trigger. Additionally, we can have emails sent to users in our Salesforce org and to an arbitrary email addresses. To set up these email notifications: 1. Go to Setup 2. Type "Apex Exception Email" into the Quick Find search box 3. Click on "Apex Exception Email" We can also configure Apex exception emails using the ApexEmailNotification object that is part of the Tooling API. If duplicate exceptions occur in Apex code that runs synchronously, Salesforce automatically detect and suppress subsequent exception emails. This prevents flooding the developer's inbox with emails about the same error. For asynchronous code, including batch Apex and methods annotated with @future, emails for duplicate exceptions are not suppressed.
// Salesforce - Developer - Epiphany #6: If a custom object is not displayed on the "Custom Objects" page, look under Settings. Go to Setup, type Settings into the Quick Find text box. Click on "Custom Settings" under "Develop"
// Salesforce - Developer - Epiphany #7: To determine the API version that our org is using: 1. Go to Setup 2. Type API into the Quick Find text box 3. Click on API under Developer 4. Click on Generate Partner WSDL, and it will tell you on the first line
page revision: 8, last edited: 02 Feb 2017 18:21