Omatic Cloud
280 results found
-
Post-to-GL: Create New Journal or Append to Existing Journal
The process of uploading a file to Post-toGL creates blank or incomplete JE in FE NXT if there are data entry errors in the document that cause the transaction import to fail.
Could the Post-toGL connection be updated to provide the options / ask the question if the user wants to:
- Create a New Journal Entry
- Append to an Existing Journal Entry
This update would reduce the number of empty or incorrect JE that have to be deleted from FE NXT.
3 votes -
Provide a merge option for records merged in RENXT and corresponding records updating in Engaging Networks
Provide a merge option for records merged in RENXT and corresponding records updating in Engaging Networks
3 votes -
Exclude Administrators
Currently, LO connector imports administrators to Raiser's Edge. However, you can't update Luminate Administrators with LO connector, which is good.
The profile should ONLY work with constituents, NOT user accounts. Filtering out administrators should be an option without a group filter from the profile settings.
3 votes -
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 specify the Constituent Code sequency (Primary Consituent Code) when adding or editing
Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.
We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.
The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.
The current behaviour appears to add a new constituent code to…
3 votes -
Fuzzy text string matching
Human beings are imperfect and ever-changing, and I expect OC to accommodate that variability the same way IOM does. If OC cannot find a potential Constituent or Relationship match between nearly identical strings like "Rachel Bailey" and "Rachael Bailey," then I'm forced to use IOM until it does. In the meantime, my organization is paying extra for a software that creates multiple duplicate Constituent, Relationship, and Address Records. See also https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/46745101-allow-matching-on-fuzzy-address-formats
3 votes -
Split gift by percentage
Add the ability to transform gifts by a set percentage of the gift amount in order to create a split gift with multiple funds. Example, 80% of the gift to one fund, 20% to another
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 -
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 -
Show "Incoming Date/Time" of Record During Matching
We currently have a problem if the record comes in multiple times, we don't know which record is the latest one. You almost have to export the data and review it column to column for an individual.
It would be nice to include the date/time when the record was added to the matching screen. Right now we can see date/time for exceptions, so it would be nice to see that on the matching.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 -
Allow import or update of gift reference on existing gifts
Allow us to import updated gift reference data on existing gifts
3 votes -
Allow phone match as a search scenario
Currently, OC does not have phone number available as a search scenario even when phone is mapped within a formula. This is essential to have because we otherwise wind up with unnecessary duplicates that could have been prevented.
3 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.
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 -
Include Marketing Source Code and Receipt Stack
Please include the following fields for mapping:
- Marketing Source Code
- Receipt Stack3 votes -
Duplicate data checks between columns
It would be helpful to have the ability to compare fields in different columns to each other, to check for duplicate values. For example, when we're working with files that contain more than one address, email, phone etc. while being able to either blank out the value if its a duplicate of another field, or keep it if it isn't.
3 votes -
Ability to Add Multiple Constituent & Gift Custom Fields in an Import Profile
Need the ability to add multiple custom fields for constituents and gifts. This would be similar to Virtual Fields in ImportOmatic, as it would be very helpful to have that same flexibility and ability of multiple attributes and additional items in Omatic Cloud so we can switch fully to Omatic Cloud.
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 -
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
- Don't see your idea?