This post is my attempt to reach out to Salesforce with a full narration of a bug in Security.stripInaccessible() method with protected custom settings only. Also, this could help any ISV Partners using Security.stripInaccessible() with protected custom settings and running into issues.

As suggested by Salesforce docs, one can use services like requestb.in or inspectb.in to test outbound messages. But these services are pretty generic so they just return 200 / OK response for any inbound…

You can easily run into this error if you are trying to perform DML on setup and non-setup objects in the same transaction. Non-Setup objects can be any one of the standard objects, like Account or any custom object.

Here are a few examples of the Setup Objects:

This post is about an issue that comes with Apex-managed sharing, i.e. System.SObjectException: Field is not writeable: Sobject__Share.RowCause. We faced this problem recently and tried searching…

I saw this tweet today about the apex-fast-xml-dom library. Unfortunately, it's true that FastXMLDom can’t support CDATA sections as of now. This is because FastXMLDom is a wrapper on top of Spring’10 Apex DOM classes, and DOM classes don’t support CDATA sections.

Apex programming WSDL can be downloaded from the “Setup” area of your Salesforce org. Just land on the “App Setup > Develop > API” page. Instructions to download are shown below:

As mentioned in my previous post, I was researching/benchmarking on how HTTP Compression with Apache Axis improves performance. The results I got post HTTP compression, are surprisingly amazing…

What if you want to create a Batch Apex Job that uses SOQL having aggregate functions like SUM, MAX, and COUNT on top of results grouped by the “GROUP BY” clause? You can’t easily create a Batch job via QueryLocator, as shown below. When working with Batch Apex in Salesforce, you might encounter a scenario where you need to run SOQL queries with aggregate functions like SUM, MAX, or COUNT while grouping results using the GROUP BY clause.

This post is for developers working on Visual Force. I came across an interesting way to control the rendering of HTML markup; previously, I was using “<apex:outputPanel .. />” for controlling the rendering of some HTML markup. This approach works….

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.

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.