Salesforce Ninja: An Elite Blog about Salesforce.com for those who wish to become Ninja.

Subscribe to this blog

Newsletter

Search This Blog

Posts

Another presentation for the London Salesforce Developer Group using mobile app. When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense? We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

An overview and necessity of the agile methodology, and how it can be leveraged in Software development. A guide for individuals to work as part of an agile team and start thinking about features and less thinking about the product. Delivering a presentation with mobile.

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.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

Those of you who have barely made it to the 1st, congrats. 2016 has been officially branded as the worst bringer of bad news and us, you and me, have survived and entered 2017. So once again congrats on making it here.

Last year, Salesforce shocked everyone by announcing Lightning, a fundamental and drastic change to the very core of salesforce delivery. The message was simple- this was a major transition in the IT services and if they have not already, all the customers would want their CRM on portal devices. When Lightning was announced, it was like relocating the passengers from a completely full Boeing 404, sturdy durable and slow to the superfast Mig 41 that could deliver fast, break the sound barrier and was efficient- only this was mid-air.

This was a paradigm shift, however, you may want to deny it, and it was fundamentally necessary. But like it or no, the shift happened. And suddenly there was a lot of material out there and every other product that was laun…

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() {
PageReference pageRef = page.peskyProblemRedirection;
pageRef.setRedirect(true);
return pageRef;
}
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…

One of the early challenges that I faced while learning Salesforce, almost eight years back, is that it was too big of a cookie to eat. It still is. Salesforce Platform is huge- it has many products, integrations, different design patterns, different coding standards and Reid Carlberg is always experimenting with something next!!!. On top of that, new developers and admins are walking into the fold with their ideas of coding, the uncertainty of the job and a massive task at hand- learn this new technology that starts with a dot com. The task is daunting.
Salesforce on its part is very forthcoming to help the community- with its trailhead, online videos, webinars, and certification programs. But too much information in itself is not a very helpful start of a career. At times like these- you sometimes wish, you could take a deep breath, pause, reflect and say - ok this is where I start.
That moment is exactly why the new book -Salesforce Platform App Builder Certification Handbookis wr…