Custom settings in Salesforce are a valuable tool for development, but they can trigger unexpected Null Pointer Exceptions when deployed to new orgs without predefined records. This common issue arises from calling CustomSetting__c.getInstance() without any available data, resulting in runtime errors.

While doing some coding using the new Apex DOM classes, I felt so frustrated regarding the BAD class design, that I decided to write a post covering my experiences.

I was going through the code sample and apex docs for new Spring 10 Apex DOM Classes. I feel these new classes are really a great missing piece for apex developers that work on integrations via web services(XML) for ex gdata api’s…

This post is for those who want to make AJAX calls in VisualForce using 3rd party JavaScript frameworks like JQuery, Yui, Dojo, etc. Though most of the time the built-in visual force Ajax works pretty well, you don’t need to make your hands dirty by doing this.

force.com standard and custom objects allow you to define fields with default values. However, there is a major confusion regarding the usage and availability of default values in Apex code.

There are many ways to handle XSS or cross-site scripting problems in Java, J2EE, Struts, Spring, and JSP. This post covers the most popular tools and ways to do that. In this post, I will explain tools like: