Discussions
Product Notice: Support for Native Salesforce Integration Ending Feb 1, 2021
View to see a recap of Eloqua's App-based integration with Salesforce, recent enhancements, and recommendations on the migration process planning and execution.
Original Recording date: July 20,
Overview
Effective February 1, 2021, Oracle will no longer support the Oracle Eloqua native Salesforce integration. Note: This does not impact the Salesforce Integration app that was introduced in Feb. 2019 with the Eloqua 19A release and Eloqua continues to support customers using Salesforce.com CRM.
What’s Changing?
In light of the arrival of the new Salesforce Integration app (released in Feb. 2019), Oracle announced the end of support for the ‘native’ Eloqua integration for Salesforce.com CRM on Feb. 1, 2021. It is recommended that you start to evaluate your current native integration setup and configuration and map it to the Salesforce integration app.
The Salesforce integration app includes numerous enhancements and benefits, including:
- Incredibly fast lead flow, using Program Canvas
- A simplified user interface, easing setup, and maintenance
- Frequent inbound updates from Salesforce.com to Eloqua
- Works with multiple Salesforce.com CRM instances
- An expanded set of objects, including:
- Bi-directional support of Salesforce.com Leads, Contacts, Accounts, Opportunities, Custom Objects, and more
- Eloqua Opportunities – used for Eloqua's Closed-Loop Reporting
- Bi-directional support of Eloqua Custom Objects
- And new features in future releases to ease administration, introduce new capabilities, and more – watch the Eloqua Release Center for updates.
Timeline
- Now: Start evaluating your current native integration setup and determine an action plan to move to the Salesforce Integration app
- Feb. 1, 2021: Oracle Eloqua ceases support of the native Salesforce.com integration
Webinars
The Oracle Eloqua Product Team has hosted several webinars to prepare for the native Salesforce.com integration and the new app-based integration. All sessions have been recorded for on-demand viewing if you were not able to attend:
- 1st Session: February 19, 2020 - Watch Here
- 2nd Session: May 22, 2020 - Watch Here
- 3rd Session: November 19, 2020 - Watch Here
- 4th Session: July 20, 2021 - Watch Here
Next Steps
Customers should evaluate their Salesforce.com integration configuration and map it to the new integration app. Some elements will map closely, while others may need to be adjusted based on new approaches in the integration of related elements such as Program Builder (native integration) and Program Canvas (new integration). Please see the Eloqua Help Center for details on configuring the Oracle Eloqua Salesforce.com Integration app.
In addition, the OracleU Eloqua/SFDC Integration App Intro course has been made generally available and does not require an Oracle University subscription, thus it's free to watch! This course provides an overview of the new Salesforce Integration App, demonstrates how to configure and use the application, and explores a common case for use.
Additional Resources
- Oracle Eloqua Help Center
- Oracle Cloud Marketplace Listing
- On-Demand Video: CRM Integrations and Extensibility (features the new Salesforce Integration App!)
- New Free Oracle University Course: The Eloqua/SFDC Integration App Intro course is now absolutely free and available to everyone here.
FAQs
Q: Where can I find the new Salesforce integration app?
A: The new integration app can be found here. The Marketplace listing contains screenshots, links to documentation, general information about the integration, and a button to install the app in Eloqua.
Q: Is there documentation for the new integration app?
A: Yes! Documentation can be found here.
Q: When is Oracle Eloqua Salesforce.com's native integration support ending? Can I still use it?
A: Support will end on February 01, 2021. After it ends, all active native Salesforce.com integrations will continue to work, however, Oracle Eloqua Support will no longer accept related inquiries or requests.
Q: How do I transition from the Native Integration to the new App?
A: Once the App is installed and the connection to Salesforce is configured, you need to add new Imports and Actions in the App that follow the same object and field mapping rules as defined in existing Native Integration Assets. In addition, you need to add any applicable Actions to a Campaign or Program Canvas.
Q: Can the installation of the App be done when the native one is still running? Can we connect the new App with Sandbox and continue using the native App with production, so that we can migrate to the new App with no downtime?
A: Yes, it can.
Q: Are there any prerequisites I need to be aware of?
A: The new Oracle Eloqua Salesforce.com Integration App requires Salesforce 18-character record IDs. If the app is installed on an instance that is using 15-character IDs, it will not work properly. Please refer to the Topliners page for more details about updating Salesforce record IDs in Eloqua.
Q: How is the new integration more secure?
A: The new integration uses OAuth 2.0 authentication method, which includes a one-time authentication process on the Salesforce app that uniquely identifies the App and does not store the username or password on the Eloqua site.
Q: Can existing CRM configuration be migrated automatically?
A: Some existing CRM configurations can be migrated through a simple sequence of steps in the new App. Please refer to the documentation above for more details.
Q: Does the new integration have auto-syncs like the old integration, importing data from Salesforce.com into Oracle Eloqua? Do you have the same ability to filter the new inbound syncs the same way you can with auto-syncs?
A: Yes. Auto-syncs (native integration) are named Imports in the integration app. Once created and enabled, imports run every 15 minutes automatically. In addition, the filter can be tested without running the import.
Q: Does the new integration have internal events and external calls for lead creation?
A: Yes. Internal events/external calls (native integration) are combined and named Actions in the integration app.
Q: Can the new integration app be used within Program Builder?
A: Program Builder (native integration) cannot be used with the new integration app. Program Canvas replaces Program Builder and delivers faster CRM update workflow evaluation.
Q: Can a form submit put a contact into Program Canvas instead of Program Builder?
A: Yes. The form processing step “Add to Program” is used to add contacts who submit a form directly to any listener step on a Program Canvas program.
Q: Is there a way to allow the App to be used only by customer admins?
A: The app catalog has security controls in place to control access to select users/groups. Actions placed on a Canvas are available to any user that has access to the Canvas. We are evaluating adding security controls to govern access to action placement on a Canvas.
Q: Does the new App allow us to test as we do with the current native App (currently, we can push one record at a time while testing)?
A: Yes, this functionality is available.
Q: Will the reporting of error be much easier for debugging use? The old reporting was very static and cumbersome for debugging.
A: Full error responses are included in the Integration App. We believe this is better in many ways compared to Native Integration, and we will continue to make improvements as we received feedback.
Comments
-
Since nobody from Oracle has, would you be able to address the concerns raised here?
- https://community.oracle.com/docs/DOC-1029561#comment-1060801
- https://community.oracle.com/docs/DOC-1029561#comment-1061392
Also, would you be able to provide a status on these enhancements requests, raised in summer 19?
- 30037131 - Request for the SFDC Integration APP: Import Options - Delete Contacts
- 30002203 - Request: SFDC Integration APP - have 'Advanced' Settings for imports
- 29944167 - Have ability to assign new CRM APP for SFDC to update 'Last Modified by the CRM'
- 29972914 - Request: Provide ability to set order of imports in new SFDC Integration APP
- 29972922 - Request: Be able to link Integration History from SFDC APP to Contact Record
Thanks.
-
Since nobody from Oracle has, would you be able to address the concerns raised here?
- https://community.oracle.com/docs/DOC-1029561#comment-1060801
- https://community.oracle.com/docs/DOC-1029561#comment-1061392
Also, would you be able to provide a status on these enhancements requests, raised in summer 19?
- 30037131 - Request for the SFDC Integration APP: Import Options - Delete Contacts
- 30002203 - Request: SFDC Integration APP - have 'Advanced' Settings for imports
- 29944167 - Have ability to assign new CRM APP for SFDC to update 'Last Modified by the CRM'
- 29972914 - Request: Provide ability to set order of imports in new SFDC Integration APP
- 29972922 - Request: Be able to link Integration History from SFDC APP to Contact Record
Thanks.
1. https://community.oracle.com/docs/DOC-1029561#comment-1060801 has been addressed
2. https://community.oracle.com/docs/DOC-1029561#comment-1061392 I hope we could confirm it with @stephaniepence shortly
As for enhancement requests, please reach out to me directly.
Thank you,
Nathan
-
1. https://community.oracle.com/docs/DOC-1029561#comment-1060801 has been addressed
2. https://community.oracle.com/docs/DOC-1029561#comment-1061392 I hope we could confirm it with @stephaniepence shortly
As for enhancement requests, please reach out to me directly.
Thank you,
Nathan
@Nathan Nemirovski-Oracle
1. - 1060801 : would you be able to share the findings, as they may be related to #2?2. - 1061392 : which is not related to stephaniepence's question, has not been addressed.
Re. enhancement requests: Will do, thanks.
-
Hi,
in native integration is possible to include systems "Form submit Link" in external call: "Create Task: Form Submit - Lead". Is this possible with Salesforce Integration app?
-
Hi,
in native integration is possible to include systems "Form submit Link" in external call: "Create Task: Form Submit - Lead". Is this possible with Salesforce Integration app?
The "Form Submit" functionality is currently in development and it is scheduled for 20B release (May 2020).
-
The "Form Submit" functionality is currently in development and it is scheduled for 20B release (May 2020).
This seems to tie in with one of the questions raised in https://community.oracle.com/docs/DOC-1029561#comment-1061392.
Would be great to get your feedback on the below, thanks.
claudiazoglmann wrote:Hi Nathan Nemirovski-Oracle,
By when do you expect the app to reach feature parity with the native integration?And how will you address the persistent instability of the apps (especially on pod 3) to ensure frictionless app integration?Thanks. -
This seems to tie in with one of the questions raised in https://community.oracle.com/docs/DOC-1029561#comment-1061392.
Would be great to get your feedback on the below, thanks.
claudiazoglmann wrote:Hi Nathan Nemirovski-Oracle,
By when do you expect the app to reach feature parity with the native integration?And how will you address the persistent instability of the apps (especially on pod 3) to ensure frictionless app integration?Thanks.Hi @claudiazoglmann,
1. The SFDC App offers functionalities and performance far superior to the Native Integration and it is designed to replace it. As I mentioned in my previous reply, I will comment on your enhancement requests.
2. We address questions and inquiries on a case by case basis. Please reach out to me directly if you have specific concerns.
Thank you,
Nathan
-
The new integration is app is pretty cool, I have used it before and its a lot faster but there are some complications that can arise because it is very fast! For more information on migrating please there is more information here: https://greg-staunton.com/eloqua-salesforce-integration-migration
-
Hi @claudiazoglmann,
1. The SFDC App offers functionalities and performance far superior to the Native Integration and it is designed to replace it. As I mentioned in my previous reply, I will comment on your enhancement requests.
2. We address questions and inquiries on a case by case basis. Please reach out to me directly if you have specific concerns.
Thank you,
Nathan
Nathan,
I don't disagree that the new App performance will be superior (faster, more robust, more scalable, using modern APIs, etc).
However, I think the feature functionality parity question is fair. Is the new SFDC App at parity with the native Eloqua to Salesforce Integration that exists today? If not, we will want to be careful because switching to the new SFDC App could result in a gap in functionality that could lead to unintended consequences.
After watching the Feb 19 webinar, I'm learning that the actual integration paradigm is shifting with the SFDC App. It might be useful to create a document that compares functionality between the Native integration and the new SFDC App so that clients can see what is necessary to be configured in order to achieve "parity" as part of switching from the Native integration to the SFDC App.
Nathan - perhaps we can connect directly - [email protected].
Karim
Post edited by Unknown User on -
Nathan,
I don't disagree that the new App performance will be superior (faster, more robust, more scalable, using modern APIs, etc).
However, I think the feature functionality parity question is fair. Is the new SFDC App at parity with the native Eloqua to Salesforce Integration that exists today? If not, we will want to be careful because switching to the new SFDC App could result in a gap in functionality that could lead to unintended consequences.
After watching the Feb 19 webinar, I'm learning that the actual integration paradigm is shifting with the SFDC App. It might be useful to create a document that compares functionality between the Native integration and the new SFDC App so that clients can see what is necessary to be configured in order to achieve "parity" as part of switching from the Native integration to the SFDC App.
Nathan - perhaps we can connect directly - [email protected].
Karim
Thank you, Karim! I will get in touch with you.
Nathan
-
Nathan,
I don't disagree that the new App performance will be superior (faster, more robust, more scalable, using modern APIs, etc).
However, I think the feature functionality parity question is fair. Is the new SFDC App at parity with the native Eloqua to Salesforce Integration that exists today? If not, we will want to be careful because switching to the new SFDC App could result in a gap in functionality that could lead to unintended consequences.
After watching the Feb 19 webinar, I'm learning that the actual integration paradigm is shifting with the SFDC App. It might be useful to create a document that compares functionality between the Native integration and the new SFDC App so that clients can see what is necessary to be configured in order to achieve "parity" as part of switching from the Native integration to the SFDC App.
Nathan - perhaps we can connect directly - [email protected].
Karim
We've run into at least two items that are not within the new app and it was recommended these be submitted for enhancement requests. Makes it very difficult to make the switch.
-
We've run into at least two items that are not within the new app and it was recommended these be submitted for enhancement requests. Makes it very difficult to make the switch.
Hi Laura, could you please send me related details?
Thank you,
Nathan
-
Hello I was wondering, we use the program builder I think that's common between all instances SFDC2.3 SYSTEM - CRM Update (Point of Interest) (Bulk Mode).
Until the moment we use the same process where every single day the program is evaluated with the content from a feeder, and the feeder itself follow the rules inside a shared filter to add the leads into the program. I think that's quite old, since it's the native functionality, don't now if anyone beside us use like that still.
My main doubt about the migration process, (I've already started to talk since not only the process described above will change but all the others) is about that specific migration from the program SFDC2.3 SYSTEM - CRM Update (Point of Interest) (Bulk Mode), it will be migrated to the program canvas in the same way we have it today in the program builder?
-
Hello I was wondering, we use the program builder I think that's common between all instances SFDC2.3 SYSTEM - CRM Update (Point of Interest) (Bulk Mode).
Until the moment we use the same process where every single day the program is evaluated with the content from a feeder, and the feeder itself follow the rules inside a shared filter to add the leads into the program. I think that's quite old, since it's the native functionality, don't now if anyone beside us use like that still.
My main doubt about the migration process, (I've already started to talk since not only the process described above will change but all the others) is about that specific migration from the program SFDC2.3 SYSTEM - CRM Update (Point of Interest) (Bulk Mode), it will be migrated to the program canvas in the same way we have it today in the program builder?
Andre,
You will need to create a program using Program Canvas that represents the same logic (or similar) in your Program Builder program in order to leverage the new SFDC App. It should be something that you can migrate relatively easily. However, it won't happen automatically. You'll need to create it and test it. Nathan can comment as well.
Karim
-
Andre,
You will need to create a program using Program Canvas that represents the same logic (or similar) in your Program Builder program in order to leverage the new SFDC App. It should be something that you can migrate relatively easily. However, it won't happen automatically. You'll need to create it and test it. Nathan can comment as well.
Karim
Thank you, Karim! This is correct.
The official docs are here: https://docs.oracle.com/en/cloud/saas/marketing/eloqua-user/Help/ProgramCanvas/ProgramCanvas.htm
Tip: During the transition period, it might be easier to use both tools. You can push contacts from a Canvas to the Program Builder (but not the other way around).
Nathan
-
Thank you, Karim! This is correct.
The official docs are here: https://docs.oracle.com/en/cloud/saas/marketing/eloqua-user/Help/ProgramCanvas/ProgramCanvas.htm
Tip: During the transition period, it might be easier to use both tools. You can push contacts from a Canvas to the Program Builder (but not the other way around).
Nathan
There is a workaround where you can move Contacts from Program Builder to Campaign Canvas to Program Canvas. Depending on the use case, this can be helpful.
-
There is a workaround where you can move Contacts from Program Builder to Campaign Canvas to Program Canvas. Depending on the use case, this can be helpful.
Thank you, since this native program builder SFDC2.3 SYSTEM - CRM Update (Point of Interest) (Bulk Mode) is quite old, but this is what the platform bring to since the first access, my main doubt now when you say:
This is not as easy as it seems, when I saw in the documentation the migration button, I was hopping that not only this main program would be created automatic but also one auto synch that we are using today Get Leads from Salesforce, are you saying that the migration process do not create those assets in the new app? And since you commented the above from all those years of hundred of companies using that template program we don't have a image/tutorial/wiki/beforeafter hahaha anything that can help us to keep all the steps/decisions etc?
-
Given that Eloqua continues to experience inadequate performance with apps in general (just this week alone an increase in contacts being stuck in app steps as "being processed by external service", even after improvements were to be made with 20B, SR3-23141671821), how can Oracle justify ending support of the native integration which doesn't exhibit such issues? Essentially you are asking customers to move to an architecture that requires people to check programs daily and manually move contacts/datacards?
-
Given that Eloqua continues to experience inadequate performance with apps in general (just this week alone an increase in contacts being stuck in app steps as "being processed by external service", even after improvements were to be made with 20B, SR3-23141671821), how can Oracle justify ending support of the native integration which doesn't exhibit such issues? Essentially you are asking customers to move to an architecture that requires people to check programs daily and manually move contacts/datacards?
Am waiting for Product Management to suggest discussing your concerns further via direct email...
-
Given that Eloqua continues to experience inadequate performance with apps in general (just this week alone an increase in contacts being stuck in app steps as "being processed by external service", even after improvements were to be made with 20B, SR3-23141671821), how can Oracle justify ending support of the native integration which doesn't exhibit such issues? Essentially you are asking customers to move to an architecture that requires people to check programs daily and manually move contacts/datacards?
@kevin.hughes, Would you be able to share which improvements had been announced in SR 3-23141671821, given that I can't seem to find anything around this in the 'New Feature Summary'? Thank you.
-
Hi @kevin.hughes,
I'm sorry to hear about your experience.
Thank you for your patience while we work to resolve the issue. It is isolated and observed by a small number of customers. By all means, we do not expect people to move contacts manually. If we can apply any learnings to the platform in general, I will be happy to share them here.
Nathan
-
@kevin.hughes, Would you be able to share which improvements had been announced in SR 3-23141671821, given that I can't seem to find anything around this in the 'New Feature Summary'? Thank you.
the SR i cited has to do with contacts stuck in app steps. My understanding is that 20B was to help with detection/routing of contacts with app issues, but it has only gotten worse after 20B
-
Hi @kevin.hughes,
I'm sorry to hear about your experience.
Thank you for your patience while we work to resolve the issue. It is isolated and observed by a small number of customers. By all means, we do not expect people to move contacts manually. If we can apply any learnings to the platform in general, I will be happy to share them here.
Nathan
Unofrtunately Nathan this has been an issue for over a year from original SR. I still would like to understand why Oracle is ending support for a native integration that does not exhibit such issues, while the app architecture is still in the same end state (stuck contacts) for over a year now. We are less than a year from the native integration ending support. With releases intended to fix this instead ending up in a worse state, i believe it is time for Oracle to reconsider.
-
Unofrtunately Nathan this has been an issue for over a year from original SR. I still would like to understand why Oracle is ending support for a native integration that does not exhibit such issues, while the app architecture is still in the same end state (stuck contacts) for over a year now. We are less than a year from the native integration ending support. With releases intended to fix this instead ending up in a worse state, i believe it is time for Oracle to reconsider.
I would fully second this comment and the concerns raised.
Cloud Apps have had these kinds of issues since they have been introduced, with an apparent spike on pod 3 in 2019.
User concerns around insufficient Cloud App performance can be found all over Topliners and in SRs, e.g. https://community.oracle.com/ideas/13434
Still, Oracle does not seem to acknowledge the fundamental issues but presses on with the decommissioning of native integration and the introduction of an inferior App...
-
Hi Team ,
can any one explain why the scheduled contact import is not working as expected please find below screen grab,
the newly created contacts or updated contacts are not getting sync with Eloqua
Does this something org level time mismatch or any other issue
-
Hi Team ,
can any one explain why the scheduled contact import is not working as expected please find below screen grab,
the newly created contacts or updated contacts are not getting sync with Eloqua
Does this something org level time mismatch or any other issue
Abhijeet Revadkar
The import is running as expected now. Please contact me directly for any related issues.
Thank you.
Nathan
-
Another day...another release (last Saturday) and issue yesterday with contacts/records stuck in app steps...customers have to come and reflow them through.
hey oracle, stop ignoring these comments. I've commented on this thread numerous times...why would ANYONE move to the SFDC app that uses this horrible app architecture?
-
Hi everyone. I have written a blog article which outlines what you need to to migrate to the SFDC app. Here it is https://greg-staunton.com/eloqua-salesforce-integration-migration
I am a contractor and I have done this a few times before. EVERYTHING you need to know is in here. I am a contractor so I will make the sales pitch. If you need helpwith it reach out to me on my website - sales pitch done. Like I said before so please don't slam me for a sales pitch, everything you need to know to migrate is in there fellow devs. If any of you want a half hour or so call to talk through it because I have done I am more than happy to pick up the phone. Especially since I have been out of work since April so in fact you would be doing me a favour!
Also - Just because they are discontinuing support doesn't mean it wont work. Personally even after the migration I would keep the native integration and keep updating for disaster recovery. If the Eloqua SFDC integration app goes down- which I have see on the Eloqua OSC one - it took Oracle THREE weeks to sort it out - imagine what your sales team would do with no synch for three weeks?
-
Hi everyone. I have written a blog article which outlines what you need to to migrate to the SFDC app. Here it is https://greg-staunton.com/eloqua-salesforce-integration-migration
I am a contractor and I have done this a few times before. EVERYTHING you need to know is in here. I am a contractor so I will make the sales pitch. If you need helpwith it reach out to me on my website - sales pitch done. Like I said before so please don't slam me for a sales pitch, everything you need to know to migrate is in there fellow devs. If any of you want a half hour or so call to talk through it because I have done I am more than happy to pick up the phone. Especially since I have been out of work since April so in fact you would be doing me a favour!
Also - Just because they are discontinuing support doesn't mean it wont work. Personally even after the migration I would keep the native integration and keep updating for disaster recovery. If the Eloqua SFDC integration app goes down- which I have see on the Eloqua OSC one - it took Oracle THREE weeks to sort it out - imagine what your sales team would do with no synch for three weeks?
sounds like oracle needs to cancel this february date. thanks greg
-
Hi everyone. I have written a blog article which outlines what you need to to migrate to the SFDC app. Here it is https://greg-staunton.com/eloqua-salesforce-integration-migration
I am a contractor and I have done this a few times before. EVERYTHING you need to know is in here. I am a contractor so I will make the sales pitch. If you need helpwith it reach out to me on my website - sales pitch done. Like I said before so please don't slam me for a sales pitch, everything you need to know to migrate is in there fellow devs. If any of you want a half hour or so call to talk through it because I have done I am more than happy to pick up the phone. Especially since I have been out of work since April so in fact you would be doing me a favour!
Also - Just because they are discontinuing support doesn't mean it wont work. Personally even after the migration I would keep the native integration and keep updating for disaster recovery. If the Eloqua SFDC integration app goes down- which I have see on the Eloqua OSC one - it took Oracle THREE weeks to sort it out - imagine what your sales team would do with no synch for three weeks?
@greg.staunton nobody will slam you for a sales pitch, however please stick to the facts. As communicated earlier, the native integration will continue to work after Feb 01, 2021, however related support inquiries will not be processed. In addition, I'm not aware of any recent or non-recent SFDC or OSC Apps outages that lasted three weeks. If you have other information, please share it here or contact me directly.
Thank you,
Nathan
