Salesforce's APEX Namespace requirement creates barrier to continuous integration - Blog - Bracket Labs. Hey, I'm Jordan, one of the developers at Bracket Labs and I'm going to occasionally blog about Salesforce development stuff here.
If you're not interested in the nitty-gritty of building Salesforce apps, you'll probably want to skip my posts For my first post I thought I'd document some pain I've been living for the past week related to APEX Namespace issues Background Developers working on the Salesforce.com (SFDC) are all too familiar with the many roadblocks to continuous-integration. IDE's typically help developers leverage CI to manage source control, building, deployment, unit testing, etc. Relationships Among Objects. Relationships associate objects with other objects.
For example, a relationship can link a custom object to standard object in a related list, such as linking a custom object called Bugs to cases to track product defects associated with customer cases. To view the parent and child relationships among standard objects, see the ERD diagrams in Data Model. You can define different types of relationships by creating custom relationship fields on an object.
IDE. Custom fields. Apex triggers. Programr -Code It Online. Prepopulate fields.