Omatic Cloud
127 results found
-
Increased Email Import Capabilities
We would like the ability for more detailed mapping of emails/phone numbers like it does for address updates. For example, the ability to add an email as a specific type ONLY if it does not already exist on their record. If it does exist, the option to ignore or update the email type. It would also be nice to say if a specific email type exists, add as "Email 1, 2, 3, etc." There are many times during events we get new email addresses but do not want to override an existing email address and do not want 5 of…
36 votes -
Add Title as one of the fields for mapping on VolunteerHub
Add Title as one of the fields for mapping on VolunteerHub on ImportOmatic. Currently this is not one of the available fields: https://omaticsoftware.my.site.com/Support/s/article/What-Fields-are-Available-for-Mapping-from-VolunteerHub
3 votes -
Send to a specific triage bucket based on a Mailchimp status field results returned during matching.
Triage currently takes specific match situations into account but I'd like to send records where Mailchimp returned "Cleaned" or "Unsubscribed" directly to the Exceptions triage bucket regardless of matching criteria. This will allow me to automate the Ready triage bucket instead of needing to review it before sending the record updates to Mailchimp. This matters because I'm trying to reduce the overall number of API transactions (Blackbaud has a threshold over which they charge me extra).
1 vote -
RE NXT-Add or REMOVE Cons Codes and Solicit Codes
We need the ability to remove constituent codes or solicit codes like we do in IOM. There is no option for that in OIC, and the removal character does not work.
63 votes -
Abililty to map Constituent Import ID when importing soft credits in RE NXT
Currently, when importing gifts with soft credits in RE NXT, the only option for matching to existing constituents is to map to 'Constituent Lookup ID'. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID'. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
8 votes -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
3 votes -
Record match search
It would be helpful to also have the option to include a LinkedIn url address as an option for constituent match search for imports.
1 vote -
Match on Existing Consent Records
Similar to how you can match on an existing Address, Email, Con Code it would be great if we could match on existing Consent records to avoid duplicates. If we're sending weekly newsletters/mailings out, when our connector runs it adds a new consent record every time
15 votes -
It would be an improvement if we could have Payout date as an option for mapping.
When bringing gifts over from classy the GL post date is not matching our deposit dates and this is causing issues with finance. If we had the ability to map the payout date to the GL post date that would make the financial process cleaner and much smoother without manual global changes.
6 votes -
Have ability to map to custom attributes for a Participant
We record event specific information against a participant of an event in RE. Could the endpoints for attributes for a Participant be made available to enable us to add/update these.
10 votes -
Update email address type when importing new email
When importing to existing constituent records and matching on email address, it would be great to be able to import non-matching email addresses to a new email type, such as Email 1, Email 2, etc.
24 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
Be able to export CQS transactions from RE to EN via the connector
Opt-in questions with the type “Opt-in Confirmation” (CQS transactions) are not available to be exported to from RE to EN using the connector. Only QCB opt-in transactions appear.
Engaging Networks have implied that this link should help . https://speca.io/engagingnetworks/engaging-network-services?key=726cda99f0551ef286486bb847f5fb5d#add-or-update-supporter . The name in the REST API is Double Opt-in. The type is CONF
4 votes -
Allow formula to run against all dates
We use a constituent formula to sync RE NXT records to LO Donor Groups. Currently, the formula will only sync records modified within the past 30 days, but we may have thousands of records not modified in that date range that still need to be in a particular donor group. Forcing a change in the modified date just unnecessarily increases the volume of records also synced by the Opt In formula. We would like to be able to choose to run the formula against all dates.
5 votes -
Ability to send multiple values to "select multiple" contact field in Emma
We want to map our constituent codes in NXT to a corresponding "select multiple" contact field in Emma, such that all of a given constituent's codes are reflected in their Emma profile. Currently there is no way to format or transform the incoming constituent code data in NXT via Omatic such that it successfully selects multiple choices in the corresponding Emma contact field.
3 votes -
Map to email comments in RE
I would like the ability to write to the email comments field in RENXT through Omatic cloud.
6 votes -
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
-
Make popular / favourited translations available with one click
In Importomatic, to add Proper Casing takes one click. In Omatic Cloud it takes around 7. It would be useful if we could "favourite" certain translations, so that these are able to be applied with a single click.
3 votes -
Classy Transaction Type in the connector section
We need to have the Classy transaction type from the payout report in the connector.
3 votes
- Don't see your idea?