Omatic Cloud
352 results found
-
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 -
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 -
1: Many, Freeze Incoming Record
If the potential matches in a 1:Many triage bucket record is greater than 5 and you scroll down to see if one of the lower potential matches might be it, the Incoming Record row disappears. It's like working in a spreadsheet where the top row isn't frozen to always display. Can we have something like Freeze Panes in the 1:Many triage buckets?
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 -
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
-
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.
4 votes -
SFTP for P2GL
Please add SFTP capabilities for ingesting files from 3rd party CRM's to P2GL.
4 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 -
Request to add ability to use sub forms in VolunteerHub
Current functionality is to use the "All Users" form when pulling fields for VolunteerHub. It would be nice to use subforms as sometimes we want to simplify the list of fields volunteers are selecting.
4 votes -
Log when a formula is reprocessed in Activity History
Currently the activity history does not show when a formula is reprocessed. This info would be helpful especially when working through the exceptions buckets. it would all use to better track errors that are recurring.
4 votes -
Enforce Default Data Differences Selection During Setup
It would be great to make the "Default Data Differences" selection more transparent to the user during setup. It opens them up to the risk of overwriting data in mass if they are sending records from the "Ready" bucket and have left the default difference as Source and have not switched it to Destination.
4 votes -
Constant Contact Preference Updates
It does not look like there is currently a way to reflect preference/interest updates from CC. You can see who is on a list, but there is no way to see if a contact has been removed or not on a list in CC.
4 votes -
Don't Update Existing Blank Values in Destination when Default Data Difference is Destination
When setting the Default Data Difference to Destination, we'd like to leave an existing destination value that is blank. We would not want to import incoming values in this scenario.
This is happening specifically when a record lands in New, but we know there's a match so we use Override to match to the existing record.4 votes -
Ability to search by Alias for Event Host
Currently, when mapping Event Host information we have the ability to search based on Name or System Record ID. It would be nice to also have the ability to search based on alias so we can search on their ID from the connecting system (Luminate, Classy, Engaging Networks, etc).
4 votes -
Ability to tag and filter formulas in Omatic Cloud
Ability to tag and filter formulas in Omatic Cloud. I have over 60 different formulas and most vary from the same set of rules i.e. we have two formulas for one file so we can adjust fields for new and existing records. Right now the tabs are useful but since they are user specific when I sign up a new user I have to spend time helping them find the right formulas. If there were tags I could assign departments, new vs existing, and formula type to make the search easier. It would also be nice to be able to…
4 votes -
Matching on middle names and birthdates
We have 70,000 individuals in out database, so we get a lot of people who match on common first and last names. Being able to use middle names or birthdays would be a huge help in distinguishing who's who.
4 votes -
Selecting Mailchimp Journeys for Import
We use Mailchimp's Automation Journeys for our emails, we can't see these to select from in the Mailchimp to RE NXT connector. We would like to apply an assigned appeal to these records in RE NXT who have started on a Journey, in that way they are excluded from being selected to import to mailchimp again and tell us who has had comms.
4 votes -
Transformations: Completely delete/remove data field
I would like to see that one of the transformations have the ability to completely delete/remove that field. One of the examples that I have come across is for consistuency codes. We use them if someone is giving at a certain amount annually. But if they are not at that level anymore, we need to delete the code. But I can see this being used for attributes or duplicate pieces of contact information.
4 votes -
Organization Information in "Verify your account" email
When adding a user to an account, it would be helpful to see the Org Name and potentially the tenant name associated with the email verification. The current email does not include any identifying information and makes confirming access challenging. It would be much easier for users to be able to directly click on the OC URL from the "Verify your email/account" email that is sent out when a user is given access to an OC instance.
4 votes
- Don't see your idea?