Omatic Cloud
418 results found
-
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
-
Need override in all grids
Whether a Match was found or not, we still may need to use override as an option.
Examples are employees who use their cc for transaction yet we know it is meant to be for their employer, and not necessarily the cardholder. This particularly becomes more important for events, as the end donor and their employer are in our CRM separately.2nd Part is when choosing a record to use for Override, the selected record should reflect some information to insure we chose the correct record. Currently if we omit a first and last name because we are entering a…
4 votes -
email notification
Have specified Omatic Cloud users receive notifications when there are gifts pending in the "Needs Attention" queue.
4 votes -
Add individual system Record ID as a match option when importing a Relationship
Expand the matching logic for Relationships to include the Constituent System record ID . The constituent system record ID is unique across RE and is assigned to a record once added in RE. This data point will allow the import for Relationship records to use an alias/alias type and constituent system record IDs to get an exact match and will prevent duplicate/reciprocal relationships to be added in RENXT. Currently ImportOmatc will match on an Alias ID and will not create additional relationships if it exists.
Currently in OmaticCloud, matching on alias id/type will result in unwanted/duplicate relationships added to RENXT.…
4 votes -
Ability to Import Mapping on completed formulas
It would be great to be able to import a mapping into an existing/completed formula. Right now you can only do this if the formula is in "Draft", but there are many times where we need to be able to import a mapping to a completed formula. The workaround is "Copy and Swap", but that only works in some cases.
4 votes -
Allow update to Recurring Gift Status
When a recurring gift plan is terminated due to failed payments, completed or cancelled by the donor, it is necessary to update the status of the recurring gift in RENXT.
Blackbaud's current API for PATCH Gift (Edit) indicates "Posted gifts cannot be modified, except to change recurring gift status".
Please allow for integration of Recurring Gift status updates.
4 votes -
Allow matching on relationship types
Relationship matching needs an option to match on the relationship type.
4 votes -
Enforce imported Name Format order on new constituents in RE NXT
Allow us to set the order that Name Formats are imported into new constituents. Those of us with a standard ordering for addressees and salutations need this. Currently, RE NXT just decides on an order, which makes them hard to review.
4 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.
4 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.
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 -
Add connector for RENXT and Cvent
Add a connector for RE and Cvent to capture new/updated contact and consent updates and event campaign outcomes.
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 -
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 -
Bulk in line edit
Having the ability to bulk in line edit records would be very beneficial.
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?