Omatic Cloud
317 results found
-
Classy Endpoint API Field Additions
Classy Recurring Giving Plans:
- Company Name (Available for Classy Transactions): This will be used to determine if a Recurring Gift was given by a Company or Individual.
- Primary Source and Secondary Source (Available for Classy Transactions) Needed to populate SF Campaign and GAU Allocation
Classy Transactions:
- ACH Last 4 (Available on Recurring Giving Plans)
4 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 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 -
Allow all custom questions in a single formula for Classy connector
If "include custom questions" setting is checked, all questions must match identically across campaigns to be in the same formula, resulting in many formulas needing to be processed separately. Allow ability to include all custom questions, regardless of matching to be mapped in a single formula.
8 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 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 -
HubSpot Email Information Subscription Dates
It would be very helpful to have Subscription status > history > dates available in the HubSpot Contacts formula. This would allow us to bring in more accurate data when managing email subscriptions
8 votes -
Custom routing of records
Sometimes records need additional review steps and currently we are capturing those notes in an email/document to work through outside of the formula. We think Custom routing of records may help with this as it would allow us to set criteria (or decided on the fly) to route records to a special bucket, for instance, to review later. This would be a time-saving enhancement.
9 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 -
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 -
Creating Lists for records imported in Omatic Cloud
One of my favorite features of ImportOmatic is its ability to create queries around new and updated entries after each import, along with exported update files. If something goes awry with an import, this function allows me to have an easily-pulled grouping of any affected records. Right now, the only way I can do this in Omatic Cloud is with an ad hoc workaround (like adding a constituent attribute for when the records were touched by Omatic Cloud). Having the option to have any imported records added to a List in NXT would both be more convenient, and would avoid…
12 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 -
Additional Scheduling Options
Right now, we have 3 scheduling options generally (weekly, daily, continuous). A client has requested that we have additional scheduling options, example: twice daily, twice weekly, every two weeks.
2 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.
13 votes -
Allow multiple bank accounts to be selected for template
We have 120+ Affiliates/bank accounts. When we cut checks, we will do it for 25-50 different ones on 1 day. Being able to select multiple Affiliates/banks would save us so much time instead of entering 1 at a time and then getting a template to upload at our bank. 1 upload for 25+ affiliates would be great! (Upload our information and then the screen would have boxes to 'check mark' and empty boxes to fill in the check # range.
3 votesThank you Missy for the idea. This is definitely an interesting use case. I am assuming that the Bank is the same for all 25 affiliates, and the only difference is the account in FE. And you would expect 1 file to be generated that has checks for all of your affiliates that are uploaded to your bank via that 1 file. Can you confirm my understanding?
For the update I would think we would need to make available all of the settings for each account you choose from FE such as starting/ending check number, include voids, and any other settings that is required for the bank format.
-
Display RE Table Entries in Formula Mapping
Similar to picklist options for OC Salesforce formulas, it would be very helpful to display table options in the actual mapping.
1 vote -
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 -
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
- Don't see your idea?