Beyond the Basics: Architecting Robust Salesforce Integrations with Titan Push/Get
Category: Salesforce Integration / Data Integrity
Read Time: 7 Minutes
Introduction
“Real-time integration” is the headline feature of Titan DXP. However, as we detail in our technical deep-dives at Titanixforce, the art isn’t just in moving data, it’s in moving it safely.
In the Titan Academy Forms Essentials, you learn how to map a field to Salesforce. But what happens when that data creates a conflict? What happens when a user creates a Parent and Child record simultaneously? This is where the Order of Execution becomes critical.
The “Get” Strategy: Efficiency First
A common inefficiency I correct in client audits is the “Lazy Get.” This occurs when an implementer queries Salesforce for data they already have accessible.
The Rule: Never use a Get when a parameter can be passed.
The Scenario:
You are sending an email to a customer with a link to update their Case.
- The Amateur Approach: You send a link with just the CaseID. When the form loads, you run a Get to find the Contact Name associated with that Case.
- The Senior Approach: You construct the URL in Salesforce to include both the CaseID AND the ContactName as parameters.
- The Result: The form loads instantly with “Hello, John” without needing to wait for a Salesforce query. It feels snappier and saves API limits.
The “Push” Strategy: Conditional Logic is King
Data integrity is paramount. You never want a web form to accidentally wipe out existing Salesforce data.
1. The “Don’t Overwrite” Rule
In your Push settings, there is a powerful checkbox often overlooked: “Don’t Overwrite if Empty.”
- Why it matters: If a user is updating their profile but leaves the “Mobile Phone” field blank because they didn’t want to type it, a standard Push might send a “null” value to Salesforce, deleting their existing number.
- The Fix: Always enable “Don’t Overwrite if Empty” on non-mandatory fields. This ensures that only new data is saved.
2. Parent-Child Simultaneous Creation
One of the most powerful features of Titan is nested pushes.
- Challenge: You need to create an Account and a Contact at the same time.
- Solution: Use the Titan “Push” nesting.
- Set up the Account Push.
- Inside the Account Push settings, add a “Child” push for the Contact.
- Map the Account ID from the parent push to the AccountId field in the Contact push.
This guarantees that the Account is created first, the ID is generated, and then immediately passed to the Contact, preventing “Orphan records.”
Debugging Your Integration
Even the best architects need to debug. I always recommend enabling the FT Debug Mode during development. It allows you to see exactly what JSON is being sent to Salesforce and what error messages are coming back. If a Push fails, don’t guess, look at the Integration Logs in your Titan Dashboard.
Conclusion
Your integration should be silent and seamless. If your users notice the data transfer, it’s too slow. If your admins notice it, it’s likely breaking validation rules.
Is your Salesforce integration hitting limits or creating duplicate data?
Let the experts at Titanixforce review your Push/Get architecture.
Schedule an Integration Review
