Omatic Cloud
394 results found
-
Autoreprocess on Destination Exception Queue
It would be helpful to have retry/resend logic on records in the destination exception queue.
Examples: running Classy Recurrings Gifts and Classy Transactions on a continuous schedule, API limits exceeded, etc. This would be very help especially for clients that have to link records to parent records but want continuous functionality.
3 votes -
Importing data to a field on a top level object ONLY if the field is blank and ignoring it if it's already populated
We have fields we'd like to import into a top-level object but only want them to import if the field in Salesforce is blank. If the field is already populated, then skip importing that field from Import Omatic.
3 votes -
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 -
Create static query option using Omatic cloud or connector imports like in Classic imports.
BB RENXT now has query and we should have the means to create a static query when we use Omatic Cloud or the connector just like in Database view and omatic classic. It's a nice log of all data imports and it can be used to reverse or for an end user to check that their import afterwards.
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 -
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 -
Pull All Records Through BBCRM Query
Ability for all records to be pulled through BBCRM
3 votes -
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 -
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 -
Print out P2GL formulas
Currently there is no ability to print out P2GL formula configuration or logic threads. Since formulas cannot currently be copied, they have to be replicated manually and the inability to print formula configuration tremendously hampers that effort. This is even true when working to apply logic from one client's formula to another -- since the logic thread cannot be printed, it's challenging to recreate from memory and/or to toggle back and forth between formulas/monitors, etc.
2 votes -
Sample Data (not enough of it)
Sample data provided when configuring new P2GL formulas is limited to 20 or 25 rows of transactions, which typically is not enough sample data to ensure that formula configurations are accurate and doing what the client needs. Two examples:
In one case there were transformations configured that looked right on the first 20 rows of data, but we couldn't see that the logic was incorrect on other rows. It was not until the client ran the post and saw an error on row 190 that we were alerted that the logic needed to be refined.
In another case, skip row…
2 votes -
Date Cleanup Format in mapping for Unix timestamps
We have a handful of connectors, example Hubspot, that save dates in a Unix timestamp format. A cleanup for date fields that will automatically changes dates to this Unix timestamp format would be helpful when integrating with these connectors. This will reduce destination exceptions caused by date format issues.
2 votes
- Don't see your idea?