Omatic Cloud
70 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
58 votes -
Add ability to only add certain mapped fields to new records
We would like to be able to decide specific criteria only applicable for new records added, not existing. Similar to applying default settings to new records in Importomatic.
Examples:
-Add addressee/salutation styles to new records
-Only add constituent code to new record
-Only add preferred name to new record52 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 -
Enable Short vs Long Formatting for Address Lines
Currently, the replace function will impact the entire string. Example: When formatting an address, 111 West 3rd Street, I want to replace West with W & Street with St. In this scenario, the current functionality will give me an output of “W”. I would like to request the functionality to replace individual elements of a string. Example: When formatting an address, 111 West 3rd Street, I’d like to replace both West with W and Street with St, giving me an output of 111 W 3rd St. Without this additional functionality it is impossible to keep aligned with our database standards…
23 votes -
Add 'Accounting Code' field to available field mapping for LO Calendar Event Profile
Many users are using the 'Accounting Code' to associate RE gift coding with a specific LO Calendar Event - This field does not appear to be an available mapping option on the Calendar Event Attendee profile.
13 votes -
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…
11 votes -
Abilitly to do relationship matching in RE NXT based on Constituent Import ID
Currently, when importing relationships to existing constituents in RE NXT, the only option for matching to existing constituents is to map to either 'Constituent Lookup ID' or System Record 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' nor the System Record ID. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
10 votes -
Sync Entire RENXT List to Data Source
Right now when using a connector to sync records from RENXT to a data source Omatic considers the "Modified Date" in addition to the RENXT List that the record is on. For lists that are created more ad hoc, such as events, the records may not have necessarily been modified recently, so they're either missed in the sync or you would need to force a modification on all records in the date via a Global Change. It would be awesome to the have the option to sync the entire list for certain formulas, so that all records on the list…
9 votes -
Add Ticketmaster Connector
Direct, one-step integration from Ticketmaster would allow non-profit theatres to easily import ticket buyer information directly into Raiser's Edge.
9 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.
7 votes -
Build a Connector for Social Tables
Social Tables is a new application released in 2015 for Event Management with incredible functionality. It would be great to have an integration for it.
7 votes -
Field Campaign Internal Name Visibility
Ability to view the Internal Campaign name in hosting when attempting to map Classy Recurring gifts,
6 votes -
Shorten Data Transformation - add ability to shorten from front or back
Current transformation only allows us to drop values from the end of a string. We also need the ability to drop values from the front of the screen.
6 votes -
Add connector for Wufoo online forms
It would be worth looking into how to create a connector service to an online forms site where one can easily custom build an online form and link to RE fields. Wufoo is a great site to start with and has an existing API.
6 votes -
make classy url available in connector
The url of the Classy Fundraiser's Page is not available as a field to map in the Classy Connector and would be most useful to be able to capture. We have suggested this to Classy as well.
6 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 -
Advanced Name Processing for Omatic Cloud
Currently there is only a way to have exact matches on records. It would be helpful to have an Advanced Name matching option in Omatic Cloud, which is similar to the IOM option to score likelihood that a similar record exists in the system.
When a similar record is found, the records could go to Needs Attention for review, with an option to create New or Match.
The example of this is if a last name has an extra space or with multiple last names with a hyphen separating them.
It is faster for me to review Needs Attention records,…
5 votes -
List Management available
Given the plan for RE to move to a "total web solution" which will ultimately replace database view, for users of IOM List Management, could this feature be made available through Omatic Cloud?
5 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
- Don't see your idea?