Omatic Cloud
10 results found
-
Allow matching on fuzzy address formats
Incoming address may be the same as existing, but with different format. We do not want to overwrite the existing address with one that has an incorrect address format and be constantly doing data clean up to correct. Need an option to only update address if it is different from existing address by a percentage. If it is 90% the same, then don't update address. OR it should give value update option, as it does if incoming title is different
65 votes -
Add an Eventbrite Connector
Create an eventbrite connector to import event registrants to the RE event Module.
32 votes -
For the VolunteerHub connector, change the date range field from "registration date" to "event date"
When bringing in Volunteer information from VolunteerHub, it would make more sense for the date range to be "event date" rather than "registration date" because the date someone registers for an event doesn't really matter. With this current set-up, it misses people who signed up for an even event before the date range even if they actually volunteered during the date range.
29 votes -
More intuitive relationship matching
Relationship matching and routing works great IF the primary constituent mapped is already in RE.
If the constituent is BRAND new then you are forced to go through the entire data flow for relationships even if the relationship is already in RE and is a 1:1 match. Meaning many unnecessary and inefficient additional clicks.
5 votes -
allow to import non-constituent participant records
We would like to be able to load non-constituents into events as participants via the cloud integration.
4 votes -
Enable Importing Event Registrations from GiveCampus
The GiveCampus integration currently supports only importing gifts. Events is another large use for the platform and one we're looking to leverage. Being able to utilize this would improve our process flows greatly.
4 votes -
Need more flexibility for filtering records in RE NXT List, in order to export
RE Query allows for greater flexibility in the output of fields from RE than the List option does. For a client with an email connector, who may be using cons codes, solicit codes, attributes, etc. to segment their audiences this is not possible with the List endpoint in RE NXT.
3 votesBlackbaud has recently added functionality that enables us to potentially pull data from Query as a Source. We are reviewing this option an looking into adding the functionality to Omatic Cloud.
-
Update the Engaging Networks / Raiser's Edge connector to allow mapping to the Origin Source field in Engaging Networks
There is a field in Engaging Networks called Origin Source which shows what caused someone to sign up to our mailing list. I would like to be able to bring this information from EN to RE, as well as push information from RE to EN if we are uploading new records).
2 votesHi Sonia,
Thanks for your suggestion here. We are currently reviewing this idea. From our research it appears as though the Origin Source may only come from the Bulk Export API (which is what Omatic uses to pull data from Engaging Networks) on the transaction that created the constituent in Engaging Networks. I am trying to find more information about this. As a result, I want to confirm how you intend to use this field so we can be sure we are considering your use case.
Can you share when you intend to use this origin source data? Is this donation transactions or some other type of transaction that you are pulling from Engaging Networks that you hope to have this field available to use? Anything else you can share about your intent and intended use would be helpful.
Thanks again.
Steve Brewer
-
Custom Fields in Every Action Connector on Contributions
It looks like custom fields are available for Contributions in the EveryAction connector, but we can't access the Contribution custom fields that are available on the Recurring Commitment formulas. Example--we're looking for a custom "Fund" field that has been created to further breakout gifts, but we are not able to map to this right now for recurring commitments. The custom field is available on the contribution.
1 vote -
Turn on the Engaging Networks QueryResult connector
Turn on the Engaging Networks QueryResult connector so we can import custom query results from EN to RE. At the moment it asks for a login email address and password when you try to use it, as well as the website URL of your EN instance. But when we try to use it with our details it says "Invalid Credentials! Authentication Failed! Username/Password is incorrect" even though we are using our correct details.
1 vote
- Don't see your idea?