SalesForce integration: Using DataMaps
According to The Gartner Group, corporate developers spend approximately 65 percent of their effort building bridges between applications. Luckily, today’s data integration tools allow even non-technical users to integrate data between systems, databases, and applications.
Today, data integration tools enable users to create integration jobs called DataMaps, link data between the source(s) and the target(s), and schedule one-time or recurring data transformations. These data “mashups” can be saved for future re-use, or sharing, or even re-distribution.
Why is the mapping so critical?
Firstly, you need to point where the source of data is and where the target is.
Secondly, when it comes, for example to SalesForce integration, sometimes you need to transform 3rd-party database table formats to SalesForce.com table formats. For instance, if you have Time or Binary objects at the source and need to save them as text at the target. Using mapping, you tell your data integration tool what transformations you want to do, and where exactly you want them to be done.
However, creating complex data maps and models may slow down the work. Bear in mind, the more simple your models, the more stable they are.
To learn more about DataMaps creation and discover more peculiarities of SalesForce integration look through our whitepaper on “Five Steps to Integrate SalesForce.com with 3rd-Party Systems and Avoid the Most Common Mistakes.“