Omatic Cloud
284 results found
-
1 vote
-
1 vote
-
Enforce Default Data Differences Selection During Setup
It would be great to make the "Default Data Differences" selection more transparent to the user during setup. It opens them up to the risk of overwriting data in mass if they are sending records from the "Ready" bucket and have left the default difference as Source and have not switched it to Destination.
4 votes -
Excessive number of duplicates - when donors give twice within same flat file
If a donor donates twice within the same flat file, Omatic Cloud will generate duplicate records for that donor in Raiser's Edge (because it sends records all at once). In contrast, ImportOmatic sends records one at a time, so if a new donor gives twice, it will be matched the second time.
This is especially problematic for events, when a donor will both buy a registration ticket and make a donation within the same flat file. Multiply this by the majority of the attendees for the event and it results in an excessive number of duplicates. This is a big…
1 vote -
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 -
Mailchimp Unsubscribe Formula - campaign information missing
In the unsubscribe export file on Mailchimp, it lists the email campaign that prompted the user to unsubscribe under the 'UNSUB[underscore]CAMPAIGN[underscore]TITLE' field. Unfortunately this campaign field is currently not information available within the unsubscribe connector API. Neither is UNSUB[underscore]TIME. it would be good to be able to add this information to RE through Omatic Cloud as it is vital additional context on unsubscribes.
1 vote -
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 -
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 -
Advanced Name Processing for Omatic Cloud
Currently there is only a way to have exact matches on records. It would be helpful to have an Advanced Name matching option in Omatic Cloud, which is similar to the IOM option to score likelihood that a similar record exists in the system.
When a similar record is found, the records could go to Needs Attention for review, with an option to create New or Match.
The example of this is if a last name has an extra space or with multiple last names with a hyphen separating them.
It is faster for me to review Needs Attention records,…
11 votes -
Add text fields to facilitate documentation of formula configuration background
For each group heading in an ImportOmatic+ formula (in the mapping section of its definition), add text fields to allow the addition of notes by the creators/managers of the formula. This would improve the product by providing a mechanism for documentation directly within the formula. Information that could be included could be explanations of why certain configuration decisions were made, idiosyncrasies and deficiencies expected in the data, where to find current mappings/value lists from data source systems, and other considerations etc.
12 votes -
Partial string 'Replace' transformation
It was a sad day when I realized that there wasn't a Transformation for address abbreviation standardization like there is in IOM (https://support.omaticsoftware.com/s/article/RegularExpressionDictionaryforAddressAbbreviations) and sadder still when I learned that I couldn't create a transformation of my own. While the 'Replace' transformation will IDENTIFY a field value containing a qualifying text string just fine, it will also replace the ENTIRE field value (not just the identified text string) with whatever replacement value you designate. Thought you could use a transformation for common address standardizations like replacing "Street" with "St"? Think again, because the way it exists now will…
4 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 -
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
- Don't see your idea?