Omatic Cloud
258 results found
-
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 -
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…
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 -
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 -
Need more flexibility for filtering records in RE NXT List, in order to export
RE Query allows for greater flexibility in the output of fields from RE than the List option does. For a client with an email connector, who may be using cons codes, solicit codes, attributes, etc. to segment their audiences this is not possible with the List endpoint in RE NXT.
3 votesBlackbaud has recently added functionality that enables us to potentially pull data from Query as a Source. We are reviewing this option an looking into adding the functionality to Omatic Cloud.
-
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 -
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
3 votes -
Keep 'Remove batch if validation fails during processing checkbox' checked
After checking the box to "Remove batch if validation fails during processing checkbox" it would be nice if that remained check for each subsequent posting job.
3 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
Make unmapped fields used in Record Match Search available in Summary Grid View
address, email, and phone are all helpful in identifying matches, but unless the fields are mapped, we can't access them in Summary Grid View. Please also allow fields used in Record Match Search to be added to grid view for ease in identifying correct matches
3 votes -
Head of Household - RENXT
We would like the ability to map to the "Head of Household" field in RENXT
2 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 -
Update email address type when importing new email
When importing to existing constituent records and matching on email address, it would be great to be able to import non-matching email addresses to a new email type, such as Email 1, Email 2, etc.
2 votes -
P2GL Activity History
It would be helpful to have Activity History for Post to General Ledger formulas. This would allow for an audit trail when trying to troubleshoot errors or instances when a formula was work previously and is no longer working.
2 votes -
Post to GL outputs for FE NXT
The formula template for posting to FE NXT does not furnish any options for the output files that the formula generates (other than the actual batch in FE NXT). Since a Post-to-GL user may not have direct access to the destination FE NXT system, those output files are very valuable for analysis and troubleshooting.
Currently, they come out as .txt files, which makes analysis challenging even when using an advanced editor. Can the output file that represents the created FE batch be output in .csv format? Or, could the user building the formula be given an option for the format…
2 votes
- Don't see your idea?