Omatic Cloud
269 results found
-
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.
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!
-
Make lookup fields external ID friendly
Lookup fields, prior to expanding the object, will only accept the Salesforce GUID, currently. If we want to map to another field, we need to expand the object. Having the lookup field accept any external ID of that object would aid in preventing too many objects mapped and also help to prevent unnecessary related records match work.
4 votes -
Add Classy payment type filter during import - paypal vs. stripe
The ability to import paypal gifts only and then stripe gifts only would significantly help during import and reconciliation
4 votes -
4 votes
-
Search Functionality in 1:1, 1:Many, New Record Queues
It would be helpful to search function across all the record queues to find certain points of data. This could operate similar to a Ctrl F but across all pages within that bucket.
4 votes -
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 -
Ability to remove special non-ASCII characters aka Emojis
It would be helpful to be able to remove nonstandard characters or Emoticons using the "remove custom text" field.
Use Case - Email subject lines often include these unreadable/unusable characters.
4 votes -
Multiple Route to Ready Criteria Options
It would be helpful to have the OR operator for "Route to Ready" based on critera.
Ex: If Classy ID matches, Route to Ready
OR
If First Name/Last Name/Email matches, Route to Ready
4 votes -
Add/Update Gift Data as part of PostOmatic Processing
We often use PostOmatic (POM) to apply complex logic, concatenating data from multiple sources in RE to determine the final Debit/Credit accounts to which transactions should be written in our financial systems.
There is no simple way to look at a gift in RE and say, "This is the Debit/Credit that was used."
While the output data from POM can be re-imported to RE, currently, this is a secondary manual process. Could POM be updated to include an option for automatically adding the final Debit/Credit outputs to the source gift record?
4 votesThanks for the idea JPP. Can you be more specific about where you want the debit and credit used to be added back to the gift? There are certainly limitations as to where data could be written back to the gift due to field size constraints as well as considering all of the output that is typically in Post to General Ledger files.
Here are a few more questions for consideration:
What is the goal of having this data in RE/how would that data be used?
Should there be any considerations if an adjustment is being posted due to adjustments creating reversing entries to reverse out what was previously posted and then having new journal entries created for the updated information?
What other scenarios might we need to account for if we added a write-back feature?
Thank you
Steve Brewer
Product Manager
-
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.
3 votes -
Add additional "Actions" to Ready Bucket
Have the other actions that you can do in Needs Attention available in the ready bucket (ie. The Add, Override and Delete button).
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.
-
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 -
Add Title as one of the fields for mapping on VolunteerHub
Add Title as one of the fields for mapping on VolunteerHub on ImportOmatic. Currently this is not one of the available fields: https://omaticsoftware.my.site.com/Support/s/article/What-Fields-are-Available-for-Mapping-from-VolunteerHub
3 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 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.
3 votes -
Provide the ability to overwrite an existing value with a null value in MailChimp
Currently, date fields with null values are not sent through the MC connector. I'm not sure if this also applies to other types of fields.
This means that if a date field is populated in MC, then updated to a null value in RE, the date will not be overwritten in MC with the new value.
Because we use these date fields (expiration date, date joined, etc) as segmentation criteria, this affects our marketing campaigns to targeted audiences and can cause significant problems.
3 votes -
Sample Data (not enough of it)
Sample data provided when configuring new P2GL formulas is limited to 20 or 25 rows of transactions, which typically is not enough sample data to ensure that formula configurations are accurate and doing what the client needs. Two examples:
In one case there were transformations configured that looked right on the first 20 rows of data, but we couldn't see that the logic was incorrect on other rows. It was not until the client ran the post and saw an error on row 190 that we were alerted that the logic needed to be refined.
In another case, skip row…
3 votes -
Have an export profile in the LO Connector that allows for TeamRaiser registrations to be exported from RE to LO.
Omatic has gotten TeamRaiser donations to flow really well from Re to LO, but the missing piece is still the offline registrations that need to go from RE to LO. Currently we have to use Blackbaud's arcaic upload system and then still rely on RELO to pull them down into RE because the import for registrations either does not have the ability to recognize offline registrations or cannot recognize the time stamp the LO uses for offline uploads of registrations.
3 votes
- Don't see your idea?