Omatic Cloud
32 results found
-
Advanced address processing screen in the Omatic Cloud is needed
We need an advanced address processing screen in the Omatic Cloud. Right now my choices are to import addresses without knowing if they are valid, or ignore addresses We also need to be able to update a new address while saving the old address as a former address. Why? People enter their addresses online incorrectly and sometimes on purpose. (I've seen people who don't include their house number or apartment number, or enter "nowhere" street.") If I allow address information to come in that doesn't match to their current address I could be overwriting good address info in RE with…
77 votes -
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
37 votes -
Add an Eventbrite Connector
Create an eventbrite connector to import event registrants to the RE event Module.
32 votes -
Have a repository for transformations
Can we have a have a repository for transformations so we don't have to rebuild and maintain them on different formulas? That would save a lot of time and double checking. Thanks!
31 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.
28 votes -
Make column order in data grids "sticky" per user
Currently in Omatic Cloud data grids, users can click and drag the columns to the right of the action buttons to re-order them. However, upon leaving the data grid and returning to it the columns reset to their default order (alpha by field name). It would be nice if Omatic Cloud would remember custom column order for each formula for each user. There are many times when it is helpful to refer to specific fields in the data grid when choosing whether to add, match, or delete a record but those fields are way off to the right. So it…
12 votes -
Ability to Override in Formula Exceptions
There should be an option other than Delete in the Formula Exceptions bucket. We should be able to Override it, especially if we know that person IS in Raisers Edge but for some reason the server dropped when looking for the record. This would help so that we aren't relying solely on the ability and capability of the servers to connect records.
11 votes -
Global Add New button in 1:N
Multiple matches are found on Name alone - instead of adding each one-by-one as a new record, add the ability to add all as NEW from 1:Many so once all rows have been determined to not match on anything beyond First/Last name, all can be newly created at once. Could restrict this button only to Name match to prevent sending other potential matches from email, etc.
10 votes -
Allow pulling an unsubscribe list from constant contact
Currently cannot pull this list. We tried to set this up pulling from the edit date, but that date is not updated when a contact unsubscribes. How else can we pull an unsubscribe list from constant contact?
9 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 -
Another User Role for Running Formulas
There is a User Role in Omatic Cloud for "Formula Producer" that grants "the ability to create, run, and modify all the formulas".
It would be nice to have a role for only running a formula. There are times we want someone to be able to run a formula, but don't want them to edit it.
4 votes -
Ability to replace values (including null) with blank values.
The use case for this request is our need to translate a NULL address line in source to blank value in destination.
4 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 -
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 fields only if new record
When a formula imports data for new and existing contacts, there may be fields that should only be populated for new records.
For example, we have source campaign, source, and sub-source to record where a record initially came from. This should only be updated on new records.
Having a 'only if new' option in the mapping would be really useful. I.e. when selected, the incoming data is ignored when updating existing records, and populated when creating new records.
3 votes -
Enforce Unique Formula Names
Formula names should be unique in Omatic Cloud. Multiple formulas with the same name can cause confusion during processing or reporting an issue with support.
3 votes -
Ability to ignore a record
When pulling data into SF there are times when a user wants to ignore or skip a record and not pull it into SF. Use case for this is a list of contacts or oppts with a field value that indicates they are not valid or at the level required for adding to the SOR.
3 votes -
Add reason code to BBCRM Constituent Email
BBCRM Constituent Email Address section has an option to set the "Do Not Email" flag. However, our Bio records team would like us to include a reason code inorder to identify who (in this case from where) set the flag.
Would it possible to add reason code as an option?
We are currently integrating with Emma.
3 votes -
3 votes
-
Add ability to include archived/unpublished donation forms
Add the ability to include archived/unpublished forms to the donation form selection in the "Additional Settings (Source)" step. Currently we cannot unpublish or archive any donation form with a recurring gift option in Luminate (which for us is most pages) because Omatic cloud will not pull those transactions once the page is unpublished/archived. This causes unnecessary page clutter in Luminate.
2 votes
- Don't see your idea?