Omatic Cloud
36 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…
139 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!
97 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
73 votes -
Add an Eventbrite Connector
Create an eventbrite connector to import event registrants to the RE event Module.
37 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 -
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.
25 votes -
Include flat file name on omatic cloud formula history page
Include flat file name on omatic cloud formula history page. Currently the page shows information like "Formula file upload started," "formula ingestion completed," and "export completed" for the Event column, and details on the number of records processed in the Description column, but it would be nice to include the name of the uploaded file in the Description column so you can easily identify which file was being handled. We use a flat file formula pretty frequently, with unique file names, and this would be very useful.
13 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 -
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.
7 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.
6 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.
6 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.
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 -
Classy Attendee Connector
I need a connector that pulls attendee data from Classy events.
4 votes -
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 -
Review specific fields that don't match the source destination
When importing we are overriding values in our destination system that we may not want to. For example, field X has a value of A in the source data and value of B in the destination - we'd like a way to review this prior to sending to the destination (similar to data differences) so we can make a choice if it's overridden or not. Ideally we'd be able to define these fields as they are unique to our organization and business rules.
This is similar to the following idea but seemed a little different. Other idea: https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/48105404-option-to-get-user-input-when-incoming-data-doesn
3 votes -
Add ability to filter transactions from Engaging Networks
It would be nice to be able to filter incoming Engaging Networks transactions by the status. The status being returned from Engaging Networks is either "success" or "reject" and we'd like to be able to filter the declined, or rejected, transactions.
3 votes
- Don't see your idea?