I suspect this might be down to how they're implemented on the external system itself. The where part of the query is not handled by Salesforce, but by the OData compliant API at the other end, the where basically defines a query for the REST response.
Dynamics CRM uses text based labels for what we know as picklists, but then has integers for the actual ...
Definitely a common use case that Salesforce is aware of and working on solving. See this pilot: https://developer.salesforce.com/releases/release/Summer15/big+objects
If you aren't under a deadline, Waiting might be the best answer.
#safeharbor as always.
Mocking the external object API calls is not properly supported by SFDC yet. However, there is a pretty neat workaround by Graham Barnard. It does require some redesign of your External Object queries and it will not give you 100% test coverage (because of the isRunnningTest() statement). But it will allow you to functionally test the code that calls the ...
I am not sure on pricing, but what I can confirm is that Lightning Connect follows OData Protocol and it is getting better with each release.
Big players like Microsoft, SAP are supporting this out of box.
Data is not saved in SFDC so you will save cost on space .
Data will be always realtime.
You dont need any developement effort to connect SFDC with ...
As part of step 2, you need to configure the redirect_uri parameter. See this link which clearly states
Redirect URL— Enter the Callback URL you copied when creating the
Authentication Provider in Salesforce.
If this does not match the value that was specified while creating an auth provider in Salesforce, it would result in the error that you are ...
Yes. You can absolutely do that. But use this markup:
I'm sure others will answer with style tips, such as working within a Visualforce Component at first, or using a text static resource, but if this way works for you while developing, then go for it.
Yes this is possible. Here is the rough outline of steps, and note that this is only one simple way of doing this, there are other options I'm not covering here, like OAuth and per user access:
In your "app" org, setup a new External Data Source - Setup > Develop > External Data Sources
Give it a name and label and choose Lightning Connect: Salesforce from ...
You can do so by this steps:
Get the count of external object.
Divide this by 2000, use this value in the for loop condition.
In the loop query the object and add the records to a list.
for every iteration add the records to the list.
One more thing to take of is that, put the offset 2000 * n, where n = 1,2,3.. in the query so that the records will not be ...
You can retrieve this using the Tooling API by using the externalDeveloperName attribute of the Metadata returned from:
/services/data/v39.0/tooling/sobjects/CustomField/[your field id]
Alternatively, if you don't know the field ID you can use the query endpoint,the only issue with this is that if you want to return the Metadata field you must ensure that ...
You will have to be in Salesforce Pre-Release Org for the same .In my Summer 15 trial org ,I can see the configuration as shown in below screenshot .You will select Type as Lightning Connect:Salesforce
Also Please create an Auth Provider of type salesforce as shown in below screenshot
OData is an open data exchange standard. As such, you should use it, if given a choice. The alternative, using pure Apex Code, is intended to interface with systems that do not understand OData and that you can't justify writing an adapter for on the far side for whatever reason (e.g. the server is already overloaded, you plan on replacing the software soon, ...
Response from SFDC Support Tier 3:
As per the current design this behavior is not bulkified. But you can probably raise an idea for the same.
Regarding the long run times, it is some thing dependent on the processing times of the record insert on the external and the response received from the external server.
That's a shame...
Refer Define External Objects documentation, where it specifies the need of creating custom fields.
If the external system allows it, we recommend that you sync the external data source to automatically create related external objects. You can instead choose to manually define external objects to customize the external object names and manually create the ...
This Salesforce documentation page Handling Failed Records in Batches has this information as the first item of "Parse the results for each record" (bolding added by me):
Track the record number for each
result record. Each result record corresponds to a record in the
batch. The results are returned in the same order as the records in
the batch ...
As usual, the "forward looking statement" safe harbor caveats apply to this response. :-)
External objects are currently (June 2014) in a limited pilot with plans currently to go to beta in Summer 14. If you are interested in using this feature, you should reach your AE or Customer Success contacts and see about enrolling in the pilot.
I just checked my ...
Option A) Use Winter'15 release
This feature is not available in Summer'14 by default. However it is available in my Preview-Org running Winter'15 release.
So you need to register a prerelease Org here https://www.salesforce.com/form/signup/prerelease-winter15.jsp
Option B) On Summer'14 you may try to log a case and ask Salesforce to enable it
We cannot directly connect SQL Server Using External data Source. But it is possible to create an OData Wrapper around SQL Server and then connecting to SQL Server using OData. See below link for exposing SQL Server as an OData Server.
I attended the Salesforce World Tour event in Washington DC this week - they were demonstrating INSERT and UPDATE support using Lightning Connect in a Preview version of the software. Lots of "Safe Harbor" caveats, but it was described as coming either later in 2015 or early 2016. This is the first time I've seen INSERT and UPDATE publicly demonstrated.
A 'Simple URL' data source is simply a file located at a given URL. The functionality allows you to have the linked file show up in the Chatter Files tab and feed. It's not related to the OData functionality at all.
See the docs for a little more info.
It is important to note that OData is only available to connect with via Lightning Connect which isn't generally available yet. Until then you can only test it in a dev sandbox.
We anticipate this product will be generally available in the November 2014 to January 2015 time frame. Any unreleased services or features referenced in this or other public ...
Reporting against External Objects has been introduced with Winter '17. Check out the Release Notes for more information.
Currently the lightning connect dont support reports .I got the information from below document
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 ...
I think I understand what you are attempting to do here...
It seems that you are using some version of the "Account.Name" instead of "Account.Id"? That seems to be the issue based on your error message, and not something else. Your Process Builder should look similar to this image:
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.