Omatic Cloud
439 results found
-
Update FE NXT Batch Desicription on import error
Post to GL creates the JE batch and then progresses through importing the transactions. If a transaction results in an error, Post to GL stops the import process—however, it may have completed a partial import, and that partial import may be "in balance."
It would be helpful if, when Post to GL fails due to a transaction error, the JE batch description could be updated to append an error message so Finance is aware that the batch was not created successfully.
3 votes -
Add Ability to Clear Fields in Luminate Online
Currently, we are unable to clear fields in Luminate Online when we know data no longer exists or is inactive. It is a risk to not enable a way to clear data in Luminate Online, as the data could flow back into RE undoing the data staff changed. A null value should not clear a field, rather use a character like ~ to indiciate a field should be cleared. This should work for any data type (date, text).
3 votes -
Allow import or update of gift reference on existing gifts
Allow us to import updated gift reference data on existing gifts
3 votes -
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 -
Engaging Networks P2P Transaction Types
EN just released new P2P transaction types - when will these be available in Omatic to import?
https://developer.engagingnetworks.net/site/peer-to-peer/#a_summary_of_the_new_transaction_types3 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 -
Formula Tabs Across Users
At the moment organising the formulas in tabs is a per user setting.
When working in a team, it is useful to categorise them to assist with daily processes, systems, frequencies, etc...
It would be great to be able to have the tabs shared across all users in the environment.
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
- Don't see your idea?