Omatic Cloud
392 results found
-
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 -
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 -
Update field labels for Classy FMV and Tax Deductible Amount
In the Classy Connector, Raw Overhead Net Amount = Fair Market Value & Raw Donation Gross Amount = Tax Deductible Amount. These labels are not intuitive for mapping. Can they be reworded to exactly what they are?
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 -
Be able to export CQS transactions from RE to EN via the connector
Opt-in questions with the type “Opt-in Confirmation” (CQS transactions) are not available to be exported to from RE to EN using the connector. Only QCB opt-in transactions appear.
Engaging Networks have implied that this link should help . https://speca.io/engagingnetworks/engaging-network-services?key=726cda99f0551ef286486bb847f5fb5d#add-or-update-supporter . The name in the REST API is Double Opt-in. The type is CONF
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
-
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 -
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 -
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).
4 votes -
Adding opportunity_ID to link actions to opportunities (proposals)
In reviewing the SKY API documentation on importing Actions into RENXT, there is a field called “opportunity_id” that would allow us to link actions and opportunities/proposals. That field is not available when mapping an Omatic Formula. That would be huge.
4 votes
- Don't see your idea?