• Claudius Li
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 2
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 0
    Replies
Hi,

We're trying to use Lightning Connect for a project that uses Analytics Engine and the Journey Engine but our data source does not support OData, only REST.

These links:
https://developer.salesforce.com/page/Apex_Code_Best_Practices
https://help.salesforce.com/apex/HTViewHelpDoc?id=platform_connect_add_external_data_source.htm&language=en_US
http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_forcecom_external_data_apex_adapter.htm

suggest that it is possible for us to create our own adapter.

Am I reading that correctly?
Are there any scalability concerns?
Would this do the same thing that the native OData adapter does or does  the native adapter have additional functionality?
Is there a better way to do this?

Our alternate plan is to create a translation layer using Olingo but I'm worried about the performance implications of having a translation layer.
Hi,

We're trying to use Lightning Connect for a project that uses Analytics Engine and the Journey Engine but our data source does not support OData, only REST.

These links:
https://developer.salesforce.com/page/Apex_Code_Best_Practices
https://help.salesforce.com/apex/HTViewHelpDoc?id=platform_connect_add_external_data_source.htm&language=en_US
http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_forcecom_external_data_apex_adapter.htm

suggest that it is possible for us to create our own adapter.

Am I reading that correctly?
Are there any scalability concerns?
Would this do the same thing that the native OData adapter does or does  the native adapter have additional functionality?
Is there a better way to do this?

Our alternate plan is to create a translation layer using Olingo but I'm worried about the performance implications of having a translation layer.