You may ask what are the mappings?
Salesforce and Magento serve different purpose and filling different needs. Based on those differences in most of the cases merchants want to store CRM relevant information in Salesforce and e-commerce related information in Magento, however there is a big overlap and that is where the "mappings" come into play.
Mappings allow merchants to specify what data needs to be shared between both platforms, where it should be stored and when it should be updated. Without such granularity, merchant will end up paying a hefty fee to Salesforce for unnecessary data storage OR store quite a bit of useless information in Magento which makes Magento more difficult to manage.
How did PowerSync solve this common problem? Well, lets take a look at our mappings section for Magento customers.
Picture #1 shows basic mappings for a Magento customer, which includes basic customer information and both (billing and shipping addresses).
First thing you probably notice are icons, which allow you to see which mappings are enabled and disabled. This feature allows you to create any mappings and keep them in the system if you are not ready to use them for any reason or you simply want to temporarily disable a filed mapping.
You will also notice we've added system mappings into the view which we did not display in the past. This feature grants your technical team full transparency into which data attributes will be touched by one or the other system during synchronization process of a record.
Now, lets take a deep dive into a mapping.
Just like before, you are able to specify where data is taken from and where is it written to regardless which system initiates the request, whether its Magento or Salesforce.
Such powerful options allow merchants to map literally anything to anything. "Wow!" you would say and we could not agree more. "With great power, comes great responsibility!" - you would have to be careful as a mapping which is setup incorrectly can easily break your synchronization process. Best advice we can give you is: Make sure your mapped field types match between both systems.
With our latest release v0.01.54.05, you are now able to control what is your system of record at the field level.
- Should Magento be able to send data from this field into Salesforce?
- Should Salesforce be able to send date from this field into Magento?
- Should Magento only update value in Salesforce, if a record already exists or only when a new record is created?
- Should Salesforce only update value in Magento, if a record already exists or only when a new record is created?
- Do you want Magento or Salesforce to overwrite data every time a record is synchronized
All these questions come up in our day to day conversations with merchants and there is not a single approach which fits every business flawlessly.
Would you like to learn more or see if this feature will satisfy your business process and requirements? Contact us via phone or email and we would be happy to discuss this feature in more detail with you and / or your technical team.