Omatic Cloud
414 results found
-
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 -
RENXT Record Type Displayed in Buckets
It would be helpful to see what kind of record type (Constituent/Non-constituent/Relationship) a record was while reviewing in the 1-Many matches bucket. This would speed up the process of determining which record is the correct match. This could be done through an extra column (that might be hidden if not wanted) or font formatting.
12 votes -
Ability to review all data being imported
Any field that might be touched through the Omatic import should be displayed on one screen to be approved by the importer. The current data difference grid only shows a couple fields. We should have the ability to see the two side by side (current BBCRM data & new Form Data) and decide which to keep untouched, and which to update with new data, and also have the ability to make edits to the new data before import.
17 votes -
Be able to export CQS transactions from RE to EN via the connector
Opt-in questions with the type “Opt-in Confirmation” (CQS transactions) are not available to be exported to from RE to EN using the connector. Only QCB opt-in transactions appear.
Engaging Networks have implied that this link should help . https://speca.io/engagingnetworks/engaging-network-services?key=726cda99f0551ef286486bb847f5fb5d#add-or-update-supporter . The name in the REST API is Double Opt-in. The type is CONF
4 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 -
Update existing records only - do not require mapping Constituent fields
When using Alias as another unique identifier to import from another platform, we need the ability to match on Alias without matching on any other pieces. At this point, a top object within the Constituent section needs to be mapped in order to create a valid formula.
21 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 -
Able to map Credit Card Brand from Stripe
requested the Brand name for credit card to be added to the connector.
0 votes -
Pull All Records Through BBCRM Query
Ability for all records to be pulled through BBCRM
3 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 -
Map to email comments in RE
I would like the ability to write to the email comments field in RENXT through Omatic cloud.
6 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 -
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
-
Additional Matching Options for HubSpot
Currently, there only search scenarios for HubSpot are 1) Email/ID 2) Email 3) ID/Name 4) ID
The issue with this is that many RENXT records have multiple emails and that is showing up as a new record in HubSpot. Additionally, the ID match is only HubSpot Contact ID. It would be very helpful to have an ID match that allows various IDs like RENXT Lookup ID/Constituent ID.
A Name search scenario would also be helpful
1 vote
- Don't see your idea?