Omatic Cloud
347 results found
-
Improve CSV Export Format for Web Front-End Exceptions
When exceptions occur in the web front end, users can export the affected records to a CSV file. However, the exported file does not match the format used by the system's formula, preventing direct external corrections and re-import.
Currently, users must manually look up ID numbers in the original file, extract the rows, make corrections, and then re-import—adding unnecessary steps to the workflow. While small numbers of errors can be fixed directly in the web view, handling large batches this way is impractical.
Proposed Solution:
Provide the option to export the csv data so that it aligns with the format…3 votes -
Ability to map to Mailing ID and Finder Number on gift record
These fields aren't available through the Blackbaud API, but we have numerous queries and reports that rely on them, dating back to when we first started using RE. We use the Mailing ID field to track the platform through which a gift was made, and the Finder Number field to identify constituents from acquisition mailing finder files. If we can't map to these fields in Omatic Cloud, it will require significant changes to our existing workflows. Currently, I'm adding this data to gift records with a Blackbaud import after importing through IOM+, which is not an efficient process.
3 votes -
Add the functionality to map 'Class Notes Status' in the Notes field section
The 'Class Notes Status' field is used in RE Database view. We are unable to use Omatic Cloud to import class notes because this field isn't mapped.
3 votes -
Activate the links/update gift list to allow linking of pledge payments in RENXT batches..
RENXT now accepts Pledge Payments in batch. Even though the Original pledge Lookup ID is mapped the formula still returns a Destination error saying pledge payments are not supported. This capability needs to be activated.
3 votes -
Update Transaction Schedule when Recurring Gift Payments are imported into RENXT batch
Gifts for payments to recurring gifts can be linked at time of import into RENXT batch. The gif shows up in the list of transactions and the amount Received is updated, but the Next transaction due: is not. This causes problems with our reminder process. The transaction schedule needs to be incremented as well.
3 votes -
Add Event Registrant Attribute to Cloud import
Would like the ability to map and add an Event Registrant Attribute in BBCRM.
3 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.
3 votes -
Pull All Records Through BBCRM Query
Ability for all records to be pulled through BBCRM
3 votes -
3 votes
-
Release Note Subscriptions
Allow users to subscribe for Release Notification emails and maybe even default that they're sent to client site admins. It could be as simple as a quick email saying when there will be a new release and a link to your Release Notes webpage (https://omatic-cloud.helpdocsonline.com/release-notes).
With other vendors, I add these notes to my work calendar so it's on my radar when changes are coming and helps me triage when something hiccups unexpectedly.
3 votes -
Review specific fields that don't match the source destination
When importing we are overriding values in our destination system that we may not want to. For example, field X has a value of A in the source data and value of B in the destination - we'd like a way to review this prior to sending to the destination (similar to data differences) so we can make a choice if it's overridden or not. Ideally we'd be able to define these fields as they are unique to our organization and business rules.
This is similar to the following idea but seemed a little different. Other idea: https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/48105404-option-to-get-user-input-when-incoming-data-doesn
4 votes -
Add option to skip New User Creation
In certain cases, there are reasons that if no user is matched it would be more applicable to skip that user rather than have new users created. It would be nice to add the option to automatically skip/ignore New Users. Currently they do go into a new user bucket, but we have to manually go in and repeatedly empty the bucket.
3 votes -
Classy Attendee Connector
I need a connector that pulls attendee data from Classy events.
3 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 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
3 votes -
Add ability to route to "ignore" and filter records from processing
When building a formula, it would be extremely helpful to define a set of criteria or matching rules that would automatically route a record to Ignore or a queue to Confirm Ignore.
3 votes -
ability to select what fields are updated separate from mapping/matching fields
It would be helpful if we could use fields for matching but then select which ones we actually want to be updated.
For example, match on name or Constituent ID/Donor ID, but only update the email address or web appeal activity information.3 votes -
Ability to ignore a record
When pulling data into SF there are times when a user wants to ignore or skip a record and not pull it into SF. Use case for this is a list of contacts or oppts with a field value that indicates they are not valid or at the level required for adding to the SOR.
3 votes -
Add ability to filter transactions from Engaging Networks
It would be nice to be able to filter incoming Engaging Networks transactions by the status. The status being returned from Engaging Networks is either "success" or "reject" and we'd like to be able to filter the declined, or rejected, transactions.
3 votes
- Don't see your idea?