Skip to main content

Cache me if you can: What you should know before daring to set URL parameter on visualforce

Photo by John- Mark Kuznietsov 

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Platform Cache: Infographic
Passing the Account id in URL parameter was a valid option, however, any manipulation of that ID would be flagged as a security risk in the code. Besides querying the same data again and again during a single transaction is annoying. Clever developers (case in point) adopt the use of cookies or pass the reference as an URL parameter (Sidebar: DO NOT PUT STUFF IN URL PARAMETERS). Some people even went into Mordor and went ahead to use Custom Settings as a Cache, which makes no sense as it is as good as wasting the DML.For our problem, we adopted the use of browser cookie to maintain the account information in context.

It all comes to this- there was no proper way to keep a record in context or on the platform- until now. It was therefore when there was an announcement for Platform Cache, I wept with tears of joy. And also repeated those when I dreamed of removing the set Cookie and get Cookie from my class.

So Platform Cache API happened. The Platform Cache API lets us store and retrieve data that’s tied to Salesforce sessions or shared across your org. With Platform Cache, Salesforce adds a memory layer to its architecture. We can also control which apps can use the cache and partition it accordingly.

Here comes a bad news followed by a good one. The developer Org has no space for Cache allocated by default, but the good news is we can ask for a trial version of the same. Have provided the link at the very bottom to request your cache trial.
There are two types of Cache:

Org Cache:
The Org cache stores information that is available org-wide. It could be used instead of Custom Settings and we can save some DML statement.

Session Cache:
This is my personal favorite. Session cache can replace the horrible methods of storing information in cookies and URL parameters. We can use the session cache to store user session information that gets wiped clean every eight hours. It can be used as a cache to store the data used for the whole day.

Had a chance to brush my hands against the partition, so here is my little playground. Remember, the problem statement I talked about earlier? I had to keep the account information in context as the page kept fetching different information. The architecture for the solution was as follows:

Whenever there is a new phone call, I store the customer information in the user's cache.

Cache.OrgPartition custPart=Cache.Org.getPartition('Customer');
Account customer=[select id, Name from Account where phone=:calledID];
custPart.put('Customer', customer);

And then, every time I have to fetch the customer or want to find if the customer is on the phone call- all I do is, fetch this information from the partition.

Cache.OrgPartition custPart=Cache.Org.getPartition('Customer');
Account customerOnCall=(Account) custPart.get('customer');
System.debug('Customer on call? = ' + customerOnCall);

If my consultant is on a phone call, I get the customer information or I get a NULL value. Cache partition is going to solve a lot of transaction level problems. The use of this feature is only limited to our imagination.

What do you think? Is there a better way of using this?

Further reading:


Popular Post

The unofficial guide to become a Certified Salesforce Administrator (ADM 201)

In my attempt at maximum certifications in 60 days, I completed Salesforce Certified Administrator exam on February 11th 2013 So you have decided to ramp up your career and take certifications in your hand. Good choice. It is also likely that this is the first time you have heard of Salesforce, certification and since your company has a vision of you completing the certification you have decided to do it. At this stage it is likely that, You have done extensive googling. You have received countless brain-dumps. And you have received plenty of advise from different types of users which ranges from Admin certification is easier than making coffee to Admin certification is tougher than building a rocket-ship to fly off to the moon. The purpose of this guide is to give you a clear understanding of what to expect when you are expected to become Certified Salesforce Administrator. To bring sense to all the things you have seen so far and to clearly explain what to do and what

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag. For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag <apex: page renderAs='pdf'> This will render the entire page as PDF. Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media . Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the p

The Basics of writing a Apex Trigger

One of the most important and common asked question on Forums and everywhere is how do I write a trigger. Coding in Apex Trigger is like going to a dentist for a root canal, you keep dreading the moment until you realize it is actually not going to hurt you. If you plan to write an Apex Trigger this quick guide will help you doing so. The first and foremost rule in writing a trigger is to remember the oldest suggestion given to the most comprehensive Hitchhikers Guide to Galaxy, ' Don't Panic. ' Writing a trigger is not a rocket science, in-fact we should thank the team at Salesforce and ForceDotCom for making everything so simple, that anyone can do it. Enough of talk, lets code. So you want to write a trigger. Let us have a glimpse of what we are going to build. The problem statement is as follows Problem:  When the User is entering the Opportunity, check for the Opportunity Amount. If the Opportunity Amount is greater than 50,000. Mark the Parent Account as