Hot answers tagged

6

In Salesforce, everything is a CRUD operation. As far as your service is concerned, it needs to support CRUD OData operations. Your application would need to be modified to support CRUD operations. Databases typically support triggers, which is when some code is executed in response to a DML request. While salesforce does support using methods other than ...


2

Salesforce doesn't currently expose data as OData. If you want to access Salesforce data using OData you currently need to rely on a third party solution like one offered by rssbus. If you want to access Salesforce data exposed by one Salesforce org to another using Lightning Connect, there is currently a pilot for a Salesforce connector which is intended ...


2

Here is an example of setting up Olingo with a JPA provider: http://scn.sap.com/community/gateway/blog/2014/02/05/odata-producer-using-apache-olingo-with-mysql-jpa-tomcat-web-server The blog mentions MySQL but you can use any database.


2

Developer Edition orgs provide a single OData External Data Source. It has lower limits than a production data source (1,000 OData queries per hour rather than 10,000 - see docs for more), but works just fine for proof-of-concept.


2

You can change the field type for a custom field on an external object to a Lookup or Indirect Lookup to associate its values with a Standard object. Use a Lookup if the column in the external data holds Salesforce record ids, and an Indirect Lookup if it is a business key. Indirect lookups can only point to unique custom fields that are flagged as ...


2

External Data source type are available in following way Simple URL External Data Source Available in: both Salesforce Classic and Lightning Experience Available in: Enterprise, Performance, Unlimited, and Developer Editions Lightning Connect—OData 2.0 or 4.0 Adapter,Lightning Connect—Salesforce Adapter, Custom Adapter Available in: Salesforce Classic ...


2

I had the same issue and got around it by adding the following to my custom connection class just before I call the getResponse method: if (Test.isRunningTest()) { Test.setMock(HttpCalloutMock.class, new MockHttpResponseGenerator()); } HttpResponse response = getResponse(url);


2

Depending upon your "build" vs. "buy" perspective... if you're interested in building your own solution, check out this Salesforce project: https://developer.salesforce.com/blogs/developer-relations/2015/05/introducing-lightning-anydb-connector-data-democracy-fueled-salesforce-lightning-connect.html If you're interested in "buying" instead, we are one of a ...


2

When creating the scratch Org, make sure that edition in definition file is assigned to developer. The Developer Edition will allow us to use 'OData'. { "orgName": "ABC", "edition": "developer", "features": [], "settings": { "orgPreferenceSettings": { "s1DesktopEnabled": true, }, "caseSettings": { "...


2

Well, the solution was trivial. I was trying to use default login endpoint, turns out I should have been using my org's domain. So getting UserInfo is as simple as sending a GET request to: https://my-org-name.my.salesforce.com/services/oauth2/userinfo With either Authorization: Bearer TOKEN header or access_token=TOKEN GET param. Edit: well another ...


1

The advantage is that you don't have to write code. The disadvantage is that you cannot support features that are not supported by the system library. There might also be a trivial difference in performance for using the OData Connector, but it's not enough of a difference to make it a major deciding factor.


1

First, the OData model is a protocol; it expects to be able to call sub-resources of the specified URL and get specific responses back. For example, $metadata returns a list of objects/fields available in the resource. There's examples of doing this on this trailhead. OData doesn't work on static files, unless you have all the files in a specific format. ...


1

You have 2 ways to do it as of now: Write that component yourself and break the sweat Install this Enhanced Lightning Grid from Salesforce Labs which does the same. I have personally loved this product and would recommend must for admins. You can add filtered related lists and its all configurable at metadata level. Probably in future release salesforce ...


1

You could probably write Apex webservices that conform to the OData standard, but this may not be easily scalable as you'd need to spin up new classes for each type of object you add, unless you use the SObject name in the URL parameters and do everything dynamically. If you do take this approach be sure to lock it down and make sure you're not opening your ...


1

With Winter 16 we are getting Writable External Objects which supports full CRUD operations on external data. Check the release notes for full details. but here's a quikie


1

External objects are really quite limited. It may be worth checking that link which is to official documents but it states that: Formulas and roll-up summary fields can’t reference fields on external objects. The only type of relationship you can have on there are lookup and external lookup, and indirect lookup relationships. But as far as mapping is ...


1

Good luck getting an account executive to turn on the OData for an existing developer org if you don't have it. I've checked two of my existing orgs, one from 2007 and another from 2012, and they both have this feature enabled. One has three Lightning Connects (Salesforce, OAuth2.0, and Simple URL), while another only has two (OAuth2.0 and Simple URL). I ...


1

AFAIK there is currently no native support for exposing OData from Salesforce. I wouldn't be surprised if this changes in the future though. Meanwhile, there are several vendors who support exposing SFDC data via OData adapters. I don't know the landscape there very well, but you'd probably want to start with Informatica and CData.


1

Well, if what you are asking is how you build your own OData v2 service from scratch, then the answer would depend on what language you are using. The .NET space has the best support for OData. You can see a tutorial on building a V3 endpoint using WebAPI in .NET here: http://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/odata-v3/creating-an-...


1

You might want to also check out an article I did for DeveloperForce recently about Accessing a SQL Server Azure database with Lightning Connect


1

I have blogged on this and you can use the below link as reference to kick start http://cloudyworlds.blogspot.com/2015/01/lightning-connect-and-sql-integration_3.html


1

I am with Progress Software. We are one of the 3rd-party vendors who offer Lightning Connect "gateways". A customer of ours is in production with 5,500 Salesforce users accessing on-premise Siebel data on an Oracle database using Lightning Connect through DataDirect Cloud. (We handle getting through the firewall.) No changes to the Siebel environment. You ...


1

Platform Connect is now branded as Lightning Connect. You can use it with "anything," so long as it is exposed in a manner that Salesforce understands. Currently, Salesforce only supports OData v2. If you have a way to expose your Siebel data in the OData version 2 format, you can use Lightning Connect with it. Some third party vendors like Informatica ...


Only top voted, non community-wiki answers of a minimum length are eligible