Omatic Cloud
271 results found
-
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 -
Match on Existing Consent Records
Similar to how you can match on an existing Address, Email, Con Code it would be great if we could match on existing Consent records to avoid duplicates. If we're sending weekly newsletters/mailings out, when our connector runs it adds a new consent record every time
3 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 -
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
-
3 votes
-
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 -
Classy Transaction Filters
I would like to include the following filters in the Classy Transaction Endpoint:
- Company Gifts based on if Company is provided or Individual Gifts Based on if Company is not provided.
- Only Recurring Donations or Only Individual Gifts
- Status: Include Succesful or Pending(ACH)
- Date filters Refund Date, Date Modified, Date Added, or Payout Date.
4 votes -
Separate formula Type for HubSpot Email Subscriptions
Currently, the HubSpot formula "Contacts" handles all subscription information. Could this information to be handled separately in a stand alone formula since the "Contacts" formula handles all changes, not just email subscription changes.
The current process is noisy and creates a high volume of records that are unrelated to email subscription changes. This is also problematic for the HubSpot connector given API hits.
4 votesWe are planning to add this feature in Q4 2023!
-
Classy Transaction Type in the connector section
We need to have the Classy transaction type from the payout report in the connector.
3 votes -
HubSpot Company Object Formula
Currently, we are only able access data from the Contacts object. It will be helpful to also include the Company object or have separate Company based formulas for this connector.
1 vote -
New Records Duplicate Creation
If multiple rows come in for the same person and are routed to the " New Records" bucket because a match is not found in destination, clicking "Send All/Page" sometimes creates duplicate contacts/constituents. We need matching capabilities in the New Records bucket to prevent duplication if all bio data matches exactly.
Currently, the work around is to ensure a unique ID is populated, so that any new records that are duplicates will be sent to exceptions. Those exceptions then need to be reprocessed in order to match. However, this only works when a unique ID field is available from the…
7 votes -
It would be an improvement if we could have Payout date as an option for mapping.
When bringing gifts over from classy the GL post date is not matching our deposit dates and this is causing issues with finance. If we had the ability to map the payout date to the GL post date that would make the financial process cleaner and much smoother without manual global changes.
3 votes -
additional -- useful -- logic operators in P2GL
Can we add some additional -- useful -- logic operators to P2GL?
*Blank
*Not Blank
*Does Not ContainBlank and Not Blank are especially useful. Today, without them, we're forced to use 'Equal' or 'Does Not Equal' and then compare that to an unpopulated field. Sometimes, however, if there are spaces in a field, it might look to be blank but isn't really.
All and all, it's just safer and more efficient to have 'Blank' and 'Not Blank' operators.
'Does Not Contain' is useful for working against alphanumeric data, and would prevent needing to use more complicated 'If/Then' or 'True/False'…
5 votes -
Post to GL outputs for FE NXT
The formula template for posting to FE NXT does not furnish any options for the output files that the formula generates (other than the actual batch in FE NXT). Since a Post-to-GL user may not have direct access to the destination FE NXT system, those output files are very valuable for analysis and troubleshooting.
Currently, they come out as .txt files, which makes analysis challenging even when using an advanced editor. Can the output file that represents the created FE batch be output in .csv format? Or, could the user building the formula be given an option for the format…
2 votes -
Use Bulk API for updating EN
Use the bulk api to upload audiences from Raisers Edge to increase throughput
3 votes
- Don't see your idea?