Omatic Cloud
367 results found
-
Dedup records in triage buckets
I'm finding duplicate records within formula triage buckets which means I either need to process or manually delete each of them. I understand why they sometimes occur but would like within the Reprocess functionality or as a separate action button the ability to remove duplicate records.
3 votes -
Add ability to move data from BBCRM to Omatic Cloud using Export Definitions
We are trying to move data between BBCRM and iModules Encompass using Omatic Cloud and would find it very beneficial to use export definitions to send data back and forth rather than queries. The reason is that with export definitions we can be specific about what data to send back and forth. For example, we use constituency to move data in Encompass from our main community to our sub-communities. Therefore we have a need to pull over constituency code. However, we only want to pull certain ones. In query, when we put constituency code in our output, it brings over…
3 votes -
Use Bulk API for updating EN
Use the bulk api to upload audiences from Raisers Edge to increase throughput
3 votes -
Classy Transaction Type in the connector section
We need to have the Classy transaction type from the payout report in the connector.
3 votes -
Ability to send multiple values to "select multiple" contact field in Emma
We want to map our constituent codes in NXT to a corresponding "select multiple" contact field in Emma, such that all of a given constituent's codes are reflected in their Emma profile. Currently there is no way to format or transform the incoming constituent code data in NXT via Omatic such that it successfully selects multiple choices in the corresponding Emma contact field.
3 votes -
Populate More Example Rows from Luminate Surveys
It would be good to have more example rows populating for Luminate Surveys when working on the Data Mapping page in a formula. When building transformations it's nice to cycle through a few records to make sure the data is transforming as expected.
3 votes -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
3 votes -
Enhanced Mappable fields to Transformations
This was a previous uservoice story but there are still gaps with usability with the if/then ability in transformations. Specifically with if/then/else, the cascading transformations are challenging to build out for most users outside of onboarding.
The ability to include mapable fields directly to a transformation, outside of concatenated replace logic, would be very helpful and would allow for a more intuitive user experience. This is current functionality in P2GL and it would be helpful to have in Omatic Cloud as well.
3 votes -
Add Title as one of the fields for mapping on VolunteerHub
Add Title as one of the fields for mapping on VolunteerHub on ImportOmatic. Currently this is not one of the available fields: https://omaticsoftware.my.site.com/Support/s/article/What-Fields-are-Available-for-Mapping-from-VolunteerHub
3 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 -
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 -
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 -
Allow import or update of gift reference on existing gifts
Allow us to import updated gift reference data on existing gifts
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 -
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 -
Importing data to a field on a top level object ONLY if the field is blank and ignoring it if it's already populated
We have fields we'd like to import into a top-level object but only want them to import if the field in Salesforce is blank. If the field is already populated, then skip importing that field from Import Omatic.
3 votes
- Don't see your idea?