Omatic Cloud
289 results found
-
Formula Triage Summary - Column Headers
It would be nice if there was a way to tell which of the "Add if not matched" and "Edit if Not Match" headers go to which section. I understand that by default they are meant to be in order but it still can be somewhat confusing on larger formulas. Not sure if color coordinating headers would be a simple solution, or maybe a tool tip containing the section name?
1 vote -
Add Event Registrant Attribute to Cloud import
Would like the ability to map and add an Event Registrant Attribute in BBCRM.
0 votes -
Update existing records only - do not require mapping Constituent fields
When using Alias as another unique identifier to import from another platform, we need the ability to match on Alias without matching on any other pieces. At this point, a top object within the Constituent section needs to be mapped in order to create a valid formula.
0 votes -
Allow Multiple Instances for the Classy Connector
I have two different Classy for two of our affiliate organizations and we have to bring in transactions from each affiliate separately. It would be nice to be able to bring all transactions from both affiliates in one profile.
0 votes -
Ability to add financial account info to recurring gifts (BBCRM)
We currently do not have the ability to add financial information for recurring gifts. We have a file with a mixture of Credit Card and EFT recurring gifts and we are unable to populate EFT information in the recurring gift. We would also like the ability to add new financial relationships if they don't exist on the record also
0 votes -
Access to Email History/Event Registration in NXT
We would like to use Email History in NXT to help determine some engagement factors in Luminate Online on a constituent record. Currently there is no way to map/transform/capture that information.
With the new iOS privacy update, understanding constituent engagement and having a 360 picture of engagement across all platforms is incredibly valuable. We would like to explore accessing those fields to apply an engagement number in LO. In addition, if someone registers for an event in NXT, that should be applied to a different engagement factor field.
0 votes -
Convert old last name to an Alias when adding new
When pushing the Last Name field to BBCRM, it would be more beneficial to have the old last name converted to an Alias rather than simply overwriting the field.
0 votes -
Add ability to export membership data out of RENXT
We were hoping to be able to push data into Raiser's Edge NXT surrounding membership. We would need:
Membership Category
Date Joined
Date Expires0 votes
Emily Dalton
responded
Currently these fields are not available in Blackbaud's SKY API. However"," once they are available"," we will look into adding this information! -
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 -
Additional highlighting in the queue grids
When viewing the queue grids, we would like to have the changed values highlighted across the queue grids. Currently, only the first two columns are highlighted, Luminate and BBCRM.
0 votes -
Do not match to inactive records
When matching incoming records through Omatic Cloud to RE, the system should not match to inactive RE records. Or at least add the option not to match to these record types.
0 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 -
Creating Lists for records imported in Omatic Cloud
One of my favorite features of ImportOmatic is its ability to create queries around new and updated entries after each import, along with exported update files. If something goes awry with an import, this function allows me to have an easily-pulled grouping of any affected records. Right now, the only way I can do this in Omatic Cloud is with an ad hoc workaround (like adding a constituent attribute for when the records were touched by Omatic Cloud). Having the option to have any imported records added to a List in NXT would both be more convenient, and would avoid…
5 votes -
Changing address type when new address is found
In ImportOmatic, when a new address is imported for an existing constituent, there is the ability for the user to determine how the outdated address' type should be changed in Raiser's Edge (e.g. it can be changed from "Home" to "Previous Address") In order to keep data clean and differentiated after imports, I wish that Omatic had a similar functionality.
3 votes -
LO e-commerce formula type
I would like to build an e-commerce formula in Omatic cloud and split gifts by item
0 votes -
Add Delete button to "Multiple matches & data differences" queue
Currently, there's only "Review" button. If the record comes several time, you have to go to each "Review" screen to delete the repeats. It really takes time if there are lots repeated & records.
0 votes -
Ability to modify new or existing records
Ability to choose if I want to make modifications to an existing records while making different modifications to new records all through one formula that are sent to ready. Example: having new records mark new email as primary while existing records do not mark as primary or overwrite.
0 votes -
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 -
Update fields with blank values
We would like to have the functionality for Omatic Cloud to update fields with Blank values in from Luminate --> Salesforce and vice versa from Salesforce --> Luminate. Blank values have meaning in both of our databases so this functionality would be extremely useful.
0 votes -
Export Matches
Would it be possible to allow for exporting the grids from 1to1 or 1 to Many. This would be helpful for when the list could use more insight and the list should be sent to someone else. For Example, between 2 systems it is common for potential duplicate users to be identified and land in the 1 to Many. When this happens, we would like to export the list to send to the team leading that system so they can address that the potential duplicate. During larger groups of records, this list can be larger and is easier to sift…
0 votes
- Don't see your idea?