Omatic Cloud
272 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 -
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 -
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 -
Skip Days for Scheduling (Allow for weekday only)
Currently, you can only select daily or weekly. I think it would be beneficial to have it only run on Weekdays. That way records don't pile up over the weekend and risk duplicate records from showing up if multiple changes happened. This has happened when people submit multiple surveys or they have multiple scheduled gifts. And there is no way from the interface to tell which record is the latest.
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 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 -
Add ability to filter transactions from Engaging Networks
It would be nice to be able to filter incoming Engaging Networks transactions by the status. The status being returned from Engaging Networks is either "success" or "reject" and we'd like to be able to filter the declined, or rejected, transactions.
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
- Don't see your idea?