- 5.1K All Categories
- 9 Introduce Yourself!
- 331 Community Feedback - NEW! (No Product Questions)
- 78 General Community Platform Concerns/Kudos/Feedback
- 67 Community Platform Bug Reports
- 71 How Do I Use the Community?
- 16 Where is the...? (Community Platform Locations)
- 13 Ideas and Suggestions for the Community Platform
- 66 Personal Document & Blog Archive
- 2 Community Programs
- 2 Get-Togethers
- 4.7K Certification Community
- 4.6K Certification Community Discussions
- 20 Oracle Certified Master Profiles
- 28 Oracle Database 12c Administrator Certified Master Profiles
- 53 Visual Builder Cloud Service
What do you do when you have multiple instances of Eloqua and multiple CRMs
What do you do when you have multiple instances of Eloqua and multiple CRMs?
The Challenge . . .
As a global company, we have multiple instances of Eloqua used throughout the different regions, and multiple CRMs. So, we were faced with the challenge of ensuring the data from our global instance of Eloqua passes to other regional instances of Eloqua.
Not only did we need to make sure the data would get passed, but we needed to make sure the required data would get passed. Some contact fields were needed in the local instance of Eloqua that were not required in the global instance. And, some fields had different formats in the different instances.
First step: in Program Builder, we created a program to look at the contact’s product. If the product on the contact record is one that needs to pass to a regional instance of Eloqua, the contact gets added to a Campaign Canvas.
Second step: once the contact is passed to the Campaign Canvas, after waiting 0.01 hours, that contact then moves to a Listener step on a Program Canvas.
Third step: when the contact enters the Program Canvas, it passes to an Update Rule. The purpose of the Update Rule is to ensure that the required Tactic ID that’s needed in the regional CRM for our sales team is populated in both the Global and Regional instance of Eloqua. The Update Rule looks at the contact’s record, and if the Last SFDC Campaign ID is in the Update Rule, then the Last Tactic ID field will be updated accordingly.
Let’s take a closer look at the Update Rule. In the ‘Select a field to update’ step, we selected the Last Tactic ID contact field. Then set ‘Select an update action’ to ‘Set to value’ and make the rule conditional based on the Last SFDC Campaign ID.
The second Update Rule needed is make sure the country field is passed. In our Global instance of Eloqua, the SFDC Standard Country must be spelled out. But, in the Regional instance of Eloqua the Country field must be 2-digits. The Update rule looks at the SFDC Standard Country field and sets the Country field accordingly.
Once those update rules have been run, the Campaign Program passes the contact to a Form Submit step.
Let’s take a closer look at the form. It needed to have all of the necessary form fields for both instances of Eloqua. Be sure that all needed form fields are included. On the Form Processing Steps, we added the step Post Data to Server, and set it to Constant Value. Then we set the Constant Value with the Eloqua Site ID URL, and the form name of the Eloqua instance to post to. It would look something like this:
In the Field Mappings section, be sure that the Target Fields are entered correctly for the instance of Eloqua that you’re posting the form data to. Most likely the field names are not the same in both instances.
Be sure to test, test, test. Check the Regional instance of Eloqua to ensure that the data is being passed, and that it’s being passed correctly.
Helpful Eloqua course – B2B: Develop and Design, Advanced Editing and Form Processing section. B2B: Program Canvas.