Omatic Cloud
367 results found
-
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 -
Allow for email campaigns to be excluded from data push to database of record
Would love to be able to exclude email campaigns that are pushing back from Constant Contact to Altru.
9 votes -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
3 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.
10 votes -
Populate More Example Rows from Luminate Surveys
It would be good to have more example rows populating for Luminate Surveys when working on the Data Mapping page in a formula. When building transformations it's nice to cycle through a few records to make sure the data is transforming as expected.
3 votes -
Ability to apply non biographical data to full constituent spouse/HOH when matched on non-constituent spouse.
In Import Omatic we have this option but not in Omatic Cloud.
4 votes -
SFTP for P2GL
Please add SFTP capabilities for ingesting files from 3rd party CRM's to P2GL.
4 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 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 -
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 -
1 vote
-
Phone format for UK
In ImportOmatic with the dictionaries we had ability to check if the phone number was less then 11 characters and add a '0' at the beginning of the string
1 vote -
Add to more than one group at a time through the RE-LO Constituent Formula in OC
Would like the ability to add to more than one group through the RE - LO Constituent Export formula type in OC. Currently you can only add one group at a time using the "Add to Groups" field.
5 votes -
Daylight Savings Time
When daylight savings time begins or ends, we're seeing scheduled formulas change - i.e. a formula scheduled to pull at 12:01 AM each day shifts to 11:01 PM when daylight savings goes into effect. Could there be a way for the daylight savings time change be automatically built into Omatic based off time zone? Otherwise to consistently retain the 12:01 AM pull, we have to remember to adjust the formula twice a year.
5 votes -
Email notification when formula completes or times-out
Have an option to enter an email address (or two) to notify when a formula completes or when the formula times out.
34 votes -
Record Routing / Advanced Matching Working Together
Currently, if Advanced matching settings are enabled, it interacts with routing in a way that unintentionally disrupts routing to ready based on Primary match. It would be helpful to include "Primary" matching in routing rules. Due to the current interaction, it probably wouldn't be recommended to use primary matching on one field if the route to ready rules are based on multiple fields.
1 vote -
Every Action Enhancement: Add Origin Form Name
Can we please add Origin Form Name as a mappable field in the Contributions endpoint for Every Action?
0 votes -
Audit trail on P2GL formulas
We need a way to identify who (which user) created and last changed a P2GL (including POM) formula. We also need an audit trail to identify who may have deleted a P2GL formula.
1 vote -
Salesforce Opportunity Name: Only Add if New
When adding a new opportunity SF requires an Opportunity Name, but Salesforce ends up changing the name after the opportunity is added anyway. When an opportunity is updated it will change the name to whatever you have mapped as the Opportunity Name. Then a workflow is needed to change them back.
1 vote -
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
- Don't see your idea?