Skip to main content

Hands on for Salesforce Lighting Connect (External Objects)

Salesforce External Objects is a new tool that has caught my attention in recent times. Those who spend their day listening to words like REST, SOAP, Integration etc. the following information for you.



Salesforce External Objects is nothing but the out-of-box implementation of ODATA architecture. ODATA is a open-source data transfer standard backed up by the Empire Microsoft (they are good guys now). Instead of an architecture of sending messages back and forth using HTTP like REST, ODATA focuses on the content of the message over HTTP. ODATA can also be compared with ATOMPUB format (RSS feed format). However ODATA is useful in sending tabular or data over HTTP, that example can also be sorted, searched, filtered and other URI conventions.

In this second post on Lighting series I am going to delve deep into how Lighting Connect lets you access external data right into Salesforce. If you were living under the rock or in some place with no internet connect, here is the summary of what you need to know about Salesforce Lighting.



In this hands-on I am going to pull some real time data into Salesforce.

Step 1: First thing we need to find out what external databases are available for us to connect to. Salesforce supports ODATA V2 databases. A quick google search brought me to this page that has some live example. (http://www.odata.org)

Step 2: If you go to Services on the site, you will find OData (read/write) that is online.
The link opens a URL (http://services.odata.org/V2/(S(l4iqzxoq5ftoav2fe5qcumtx))/OData/OData.svc/) hold on to that for now, lets open Salesforce.

Step 3: As always login to your developer account. (Note: for this tutorial and any tutorial on Lighting, please get a fresh org. As I learned the hard way, an old sandbox did not have this feature in built.)

Step 4: If all is well, you will find External Data Sources and External Objects


Step 5: We are going to first add an External Data Source and point it to the OData. Go to External Data Sources -> Click 'New'

In the form you can specify the Name and Label. The Type should be Lighting Connect: OData 2.0 



Step 6: Once you select the type, it will have further fields like Server URL. Copy the URL we have in Step 2 above and click Save.

Step 7: Once you click Save and all is well you should see a detail page with options to Edit, Validate and Sync and Delete



Step 8: Click on 'Validate and Sync' it will scan the URL and get you all the objects available to Sync with Salesforce. Note: if it does not sync or you get an error, it will be shown in Status field.



Step 9: I am going to select Product object to sync. Select your objects and click on Sync. You should see one record in the External Object section.



Step 10: Now comes the best part, go to Create-> Tabs and you can find our objects right there in Salesforce object tabs


As I have understood in past few days, Lighting is a vast thing. In the next few weeks, Ill be posting one blog about the Lighting Framework. Be sure to subscribe to the blog and if you have any comments, mention in the comments below.

SforceNinja Out.








Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

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:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

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 page. To p…

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

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…