Link in a formula text field - Explained with Use Case

Use Case:

I have three objects-

·         Application User

·         Bank

·         Credit Card.

Application User is having master detail relationship with both Bank and Credit Card where in both the cases Application User is on the master side and Bank/Credit Card are on the details side.

Schema is as below –

Now when I click on the Credit Card tab, I would like to display the Application User’s detail in the list. So I need to credit a new view to include the Application User detail. I did that (View Name: All Credit Card)and below is what I can see-

Now the problem is - with the above view, from “Credit Card Holder” column, I am not able to identify the Application User. I need to click on individual “Credit Card Holder” entry to go to the details page of the Application User object and then identify the user. OMG!!! Definitely not a good and efficient way. We have to be smart. So let’s think about something innovative –

Why not display the “LastName, FirstName” in the Credit Card Holder column so that from this page only, I can understand the owner of the Credit Card. Great good idea. Let’s see how we can do that –

Let’s create a formula field which will fetch the Application User’s LastName and FirstName and populate like below-

Now let’s add the field in the previously created view i.e. All Credit Card. Let’s see what I have achieved –

WoW!!! Much better. Now I am able to identify who is the owner of a particular credit card. Great.

But Noooo!!! Another problem – now from this page, I can’t go to Application User’s detail page because my entries in the column “Credit Card Holder Name” are not links any more. I need to fix that. Let’s see –

Why not create another formula field to make the text clickable so that when user clicks on the link, the detail view of that particular user can be displayed. Let’s do that –

Now let’s add the newly created field in the previously created view i.e. All Credit Card. Let’s see what I have achieved –

Now user can easily click on the Credit Card Owner hyperlink to view the details of the particular Application User.

Please share your feedback on this. Thanks in advance.

Share:

Read More

How Salesforce Does Agile

Share:

Read More

Winter '15 Release-Overview and Highlights

Share:

Read More

Version Controlling in Salesforce with Git + Eclipse

I always prefer version control while doing coding. I can’t think of writing code without version controlling. But when I moved to Salesforce, the first thing that I was looking for is the version controlling to have better source code control.

I worked with many version controlling tools like CVS, SVN etc. But I personally feel Git is the best version controlling option we are having now. I am a big fan of Git. Git is much more powerful than any other version controlling tool. Here in this post, I am not going to describe the advantages of Git. But if you want, you can refer below URLs to understand how powerful Git can be:

https://www.youtube.com/watch?v=4XpnKHJAok8
http://www.vogella.com/tutorials/Git/article.html

Here in this post, I will explain how we can use Git + Eclipse for Version Controlling in Salesforce.
Step 1: Once we download and install Force.com IDE, we need to install the Git plugin. The name of the plugin is: EGIT. We can download the same from http://www.eclipse.org/egit/
Step 2: Get the salesforce code into your local worspace.
Step 3: In this step, we will configure the “Local Repository”. What we need to do is: Right Click on Project | Team | Share Project.

Step 4: We need to choose Git as an option and click on “Next”

Step 5: Here we need to click on “Create”. Select “Parent Directory” and “Name” as below and click on “Finish”. This is the step where we will mention the local repository name and the path.

Step 6: Once we click on the “Finish” button, we will see that all files in Eclipse are marked with “?” mark like below. Question marks means Git does not know what to do with files, either you can schedule them for commit or add few of them in ignore list.

Step 7: Here in this step, we will commit our changes to our newly created “Local Repository”. In order to do that, click on Project | Team | Commit. It is always good practice to provide meaningful comments against each commit so that if required, developers can easily recognise the changes.

Once we are done with the commit, we will notice that “?” mark will vanish. It means that the changes are committed to the local repository.

Step 8: Till now we have committed our changes to our local repository. But now it’s the final and most important part where we will move our code from local repository to actual remote server. For that we need to create a remote repository in Git. Please search in Google for “How to create remote repository in Git?”. Once we are done, we need to configure the same in eclipse. For that click on Remote | Create Remote.

Step 9: A new pop-up window will come up. First select the option “Push” and give name of remote repository. “Push” means we are going to save changes on remote repository and “Fetch” means we are going to fetch code from remote repository.

Step 10:  Clicking on the “Ok” button, a new pop-up window will open. Here click on the Change button. In the new pop-up window, we have to provide Git URL, username and password like below and click on finish.

Step 11: Now here click on “Advanced” button. In the new pop-up window, select the options as per the below screenshot and click on finish.

Step 12: Finally click on “Save”. Now our remote repository is also configured. Let’s check whether it is working now.
Step 13: Here in this step, we will push the code from our “Local Repository” to “Remote Repository”. Do as displayed below:

Step 14: Once the push is done, we will see all our code is moved from “Local Repository” to “Remote Repository”. Here is the code in Github. 

In the same way we can configure “fetch” to get the code from remote repository.

I hope this article will help many developers. Please feel free to provide your feedback.

Share:

Read More