Omatic Cloud
418 results found
-
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 Expires6 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 -
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…
21 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.
42 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.
1 vote -
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.
2 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 -
Add "Send to Needs Attention" button in Ready Bucket
Similar to adding an Override button to the Ready bucket, similarly it would be nice to have a "send to 1:1" button when filtering through those matches in the Ready bucket.
0 votes -
Add the option Send Page to Needs Attention 1:1
Having the option to Send Page in 1:1 would be helpful.
3 votes -
Ability to Override in Formula Exceptions
There should be an option other than Delete in the Formula Exceptions bucket. We should be able to Override it, especially if we know that person IS in Raisers Edge but for some reason the server dropped when looking for the record. This would help so that we aren't relying solely on the ability and capability of the servers to connect records.
39 votes -
Conditionally Ingore Records
I would like to pitch an idea to conditionally ignore entire records based on a specific field value or set of values. For example: - If a specific field is of type date and a specific date is found then that record would be ignored. - If the profile field "Marital Status" is equal to married than ignore - If the specific value matches the same field in the destination source, then ignore the record
1 vote -
BBCRM > LO Formulas - Would like additional fields such as address data to be returned for matching.
Currently in BBCRM >LO Formulas when matching records,the address info does not appear in the grids so we can't use that to decipher what the correct matched record is without going into each potential match which is very time consuming. Mailing address would be helpful for the following reasons: 1) LO and CRM may have different emails for a same person (with same address). 2) LO may have duplicated records for a same person but the system can't tell they are duplicates. E.g. - Incoming CRM record (same name) mailing address match one LO record and email address match another…
0 votes -
Request to have TeamRaiser revenue formulas mimic the same behavior as non-TeamRaiser formulas when it comes to revenue exclusion.
Hi Omatic Team, Formula type: TeamRaiser Registration and Donation to BBCRM Constituent/Revenue & Luminate TeamRaiser Donations to BBCRM Constituent Revenue
Request to have TeamRaiser revenue formulas mimic the same behavior as non-TeamRaiser formulas when it comes to revenue exclusion. Currently, we can exlucde "offline" gifts from coming over via our Revenue formula (type=Luminate DOnations to BBCRM Constituent/Revenue),
but this behavior is not consistent with TeamRaiser revenue formulas. While we have safeguarded these from coming over to CRM, it would be more user-friendly to not see them in queue at all.0 votes -
Support for refunds from Luminate to BBCRM
Omatic Support confirmed that refunds are not supported in any way currently (including flat files) by Omatic Cloud for Luminate to BBCRM. Since handling refunds and adjustments is such a standard revenue workflow, having support added for it would be most helpful.
0 votes
- Don't see your idea?