Salsa Engage offers a native integration with Salesforce NPSP, which for the most part works great. But I just finished a Salsa Engage integration with Salesforce, and the documentation didn’t cover a few important things. That meant extra time spent figuring it out, so I’ll try to save you at least one headache by explaining the Gender dilemma.
In Salsa Engage, there is a standard Gender field that isn’t visible or available on the Supporter page. But it exists, and it isn’t mapped to the existing Gender field in Salesforce either.
The integration created a new “Gender (Salsa)” field in Salesforce, even though the system already has one. And the mapping between that new field and the Gender field in Salsa is locked. Even with the field mapping tool, you can’t simply connect the existing Gender field in Salesforce to the standard Gender field in Salsa.
That’s a problem, because now both systems have two Gender fields. Four in total.
To solve it, we used Process Builder to copy the values back and forth. But the whole thing seems avoidable, and it would have been much cleaner if the documentation explained it.
The County field? That’s hidden too.
After too much time wasted, I got this message from Salsa:
“There are a few fields in the same vein, such as County and Timezone that are held by Engage, that can be queried on and changed, they’re just not available to view/edit from a supporter record.”