Omatic Cloud
439 results found
-
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.
6 votesWe’re planning to enhance the GoFundMe Pro connector to bring in Payout ID, Payout Created Date, and Payout Deposit Date for each transaction.
Once available, these fields can be mapped in your formulas so that gifts align with your bank deposit dates, without manual global changes. Work is expected to begin in the next few weeks, and we’ll share another update once it’s underway.
-
Option to get user input when incoming data doesn't match existing data for specified fields
We often have enough information to be confident that the incoming data matches a record in Salesforce. However, whether the better quality data for important fields is in Salesforce or the incoming data is unknown. So we can't confidently overwrite data without a manual validation.
For example, P Ennals might match to Peter Ennals. I am happy this is a valid match and therefore want to set it as a ready record. However, I don't want P to overwrite Peter.
The functionality could be such that I specify per formula which fields require manual validation. E.g. for records where name…
6 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?
5 votes
Steve Brewer
responded
Thanks 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 matching on relationship types
Relationship matching needs an option to match on the relationship type.
5 votes -
Export transformation values from Omatic Cloud to csv AND more efficient sorting
I would like to be able to export transformation values from Omatic Cloud to csv to easily review all transformation values. The window in Omatic Cloud is too small to thoroughly review values when we have hundreds of transformations within one category (for example, we use the "replace" transformation for hundreds of Appeals, each of which may have multiple corresponding Luminate form IDs to replace).
Also would like more efficient options to sort transformations. The drag and drop is very slow and again, the small size of the window is problematic for this task.
5 votes -
Auto-delete/omit new records
Allow processing to delete New Records bucket automatically or omit new records. I don't want new records added to my system.
5 votes -
Ability to map Action Note fields during an import
Omatic currently uses the Actions API to import actions into RE NXT, which works well. We'd like the ability to map the Action Note at a more granular level, specifically the Action Note Type rather than relying on the default.
Current behaviour
When an action note is created via import, the Note Type defaults to "Added via Web View". There's no way to set it during mapping, so every imported note carries the same generic type regardless of what the note actually is.Requested enhancement
Allow the Action Note fields to be mapped on import, either from the source file…5 votes -
Add to more than one group at a time through the RE-LO Constituent Formula in OC
Would like the ability to add to more than one group through the RE - LO Constituent Export formula type in OC. Currently you can only add one group at a time using the "Add to Groups" field.
5 votes -
SFTP for P2GL
Please add SFTP capabilities for ingesting files from 3rd party CRM's to P2GL.
5 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.
5 votes -
Add connector for Marketo
Add a connector for RE and Marketo to capture consent/solicit changes and campaign results to Actions.
5 votes -
Duplicate data checks between columns
It would be helpful to have the ability to compare fields in different columns to each other, to check for duplicate values. For example, when we're working with files that contain more than one address, email, phone etc. while being able to either blank out the value if its a duplicate of another field, or keep it if it isn't.
5 votes -
Pull Opt-Outs from Specific Subscription Lists in Emma
Currently, there is no way to tell how the connectors are configured if someone opts out of a specific subscription list.
USE CASE: We would like to add Solicit Codes/Attributes in RE based on if they unsubscribed from a specific list to manage preferences.
Issue: No way to tell in SOR what preferences have changed.
5 votes -
Enable File-to-File Transformation & Export in Omatic Cloud
Currently, Omatic Cloud only allows transformations when importing data into Raiser’s Edge or other connected systems. However, it would be extremely beneficial to have a file-to-file processing option. This would allow users to:
Upload a spreadsheet, apply transformations, and export the transformed data as a new file (CSV, Excel, etc.).
Use Omatic’s powerful transformation tools without requiring integration with an external database.
Improve data cleaning and preparation workflows for reporting, imports, and other external processes.
This feature would save time and expand Omatic Cloud’s usability beyond direct imports. Please consider adding this functionality in a future update!5 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…
5 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.
5 votes -
Enforce Unique Formula Names
Formula names should be unique in Omatic Cloud. Multiple formulas with the same name can cause confusion during processing or reporting an issue with support.
5 votes -
Allow for the Import of Gift Aid Declarations in Omatic Cloud
Absolutely critical for clients in the UK doing any gift importing. This is a feature that is UK specific but needed to move IOM profiles to OC.
5 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 -
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
- Don't see your idea?