Omatic Cloud
293 results found
-
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
5 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 -
Comparative Logic for Date Inputs
We would greatly benefit from the addition of a function within transforms to compare a date input with a dynamic date provided at runtime. For example: if End date < Today’s Date then Replace input value with “Inactive”.
In our Raiser’s Edge database, we rely on the Constituent Code “Start date” and “End date” fields to determine when a donor opted into a program and whether they are still active with that program.
Presently, to update the status fields in our destination records, we’re forced to build a distinct NXT List for each pairing of program and status, as well…
20 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 -
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 -
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 -
Integrations/Formulas | Mapping | Total Sum of Two Cells/Columns from an Import File
Built-in feature that allows combining two column headings to create a total sum during the mapping process.
Example: scenarios of summing platform fees and transaction fees.
1 vote -
Include non-mapped source fields in summary fields to help with decision making.
We don't want to update fields in LO but want to see the source fields (which are not used in the mapping) in summary fields to assist in making decisions.
1 vote -
1 vote
-
1 vote
-
We would like the ability to sort data in the Needs attention bucket. This is the way they used to be ordered.
Previous order was:
1. 1:1 Matches
2. Multiple Matches
3. New Records
4. Destination Exceptions
5. Formula Exceptions1 vote -
1 vote
-
Deceased indicator
Display a deceased indicator in the data differences columns of the triage buckets, similar to displaying Mailchimp contact status. This will help with decisions without me needing to step into the record just to find out they're deceased.
1 vote -
Enable Importing Event Registrations from GiveCampus
The GiveCampus integration currently supports only importing gifts. Events is another large use for the platform and one we're looking to leverage. Being able to utilize this would improve our process flows greatly.
6 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 -
Add connector for AlumnIQ
Would like a connector for AlumIQ for BBCRM OC
https://www.alumniq.com/1 vote -
Feedback requested for cascading toast notifications
With the release on July 2, 2024, we greatly reduced the cascading toast notifications and moved the notifications to the center of the page, as to not impede with interactions within the application. We want to continue to make incremental updates to notifications, so we'd love your feedback!
What information would you like to see in the notifications? Where and how would you like to access the notifications? How do you use the information to change a behavior or interaction within Omatic Cloud? What else?
0 votes -
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 -
Include flat file name on omatic cloud formula history page
Include flat file name on omatic cloud formula history page. Currently the page shows information like "Formula file upload started," "formula ingestion completed," and "export completed" for the Event column, and details on the number of records processed in the Description column, but it would be nice to include the name of the uploaded file in the Description column so you can easily identify which file was being handled. We use a flat file formula pretty frequently, with unique file names, and this would be very useful.
13 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
- Don't see your idea?