Omatic Cloud
352 results found
-
Fuzzy Organization Name Matching
Currently, Omatic Cloud does not support fuzzy name matching for organizations. Organizations can only be matched on name exactly. In this case, if you were to try and import employment data, minor variations in organization name will force you to manually match with existing organizations or you will end up with multiple duplicate organizations within your database. Fuzzy organisation name matching would make this process much simpler and streamlined.
15 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…
15 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
15 votes -
Include flat file name on omatic cloud formula history page
Include flat file name on omatic cloud formula history page. Currently the page shows information like "Formula file upload started," "formula ingestion completed," and "export completed" for the Event column, and details on the number of records processed in the Description column, but it would be nice to include the name of the uploaded file in the Description column so you can easily identify which file was being handled. We use a flat file formula pretty frequently, with unique file names, and this would be very useful.
14 votes -
Add ability to import perpetual recurring donations from Encompass
Perpetual recurring donations is a separate endpoint in Encompass. We would like to be able to import these transactions.
13 votes -
Add 'Accounting Code' field to available field mapping for LO Calendar Event Profile
Many users are using the 'Accounting Code' to associate RE gift coding with a specific LO Calendar Event - This field does not appear to be an available mapping option on the Calendar Event Attendee profile.
13 votes -
Add percentage of match results to ready buckets
The older version of Omatic Cloud displayed the percentage of matching information between records in our systems (Altru and Constant Contact). This was very helpful to us as we could minimize the amount of data being sent by only sending records with a percentage match under 100%. We would love to have this feature available again.
13 votes -
New Records Duplicate Creation
If multiple rows come in for the same person and are routed to the " New Records" bucket because a match is not found in destination, clicking "Send All/Page" sometimes creates duplicate contacts/constituents. We need matching capabilities in the New Records bucket to prevent duplication if all bio data matches exactly.
Currently, the work around is to ensure a unique ID is populated, so that any new records that are duplicates will be sent to exceptions. Those exceptions then need to be reprocessed in order to match. However, this only works when a unique ID field is available from the…
13 votes -
Add text fields to facilitate documentation of formula configuration background
For each group heading in an ImportOmatic+ formula (in the mapping section of its definition), add text fields to allow the addition of notes by the creators/managers of the formula. This would improve the product by providing a mechanism for documentation directly within the formula. Information that could be included could be explanations of why certain configuration decisions were made, idiosyncrasies and deficiencies expected in the data, where to find current mappings/value lists from data source systems, and other considerations etc.
13 votes -
Add Table Entry If It Doesn't Exist
It would be very helpful if Omatic Cloud could add a table entry during the import if it doesn't already exist. This is IOM functionality that is needed in Omatic Cloud.
12 votes -
RENXT Record Type Displayed in Buckets
It would be helpful to see what kind of record type (Constituent/Non-constituent/Relationship) a record was while reviewing in the 1-Many matches bucket. This would speed up the process of determining which record is the correct match. This could be done through an extra column (that might be hidden if not wanted) or font formatting.
11 votes -
Ability to review all data being imported
Any field that might be touched through the Omatic import should be displayed on one screen to be approved by the importer. The current data difference grid only shows a couple fields. We should have the ability to see the two side by side (current BBCRM data & new Form Data) and decide which to keep untouched, and which to update with new data, and also have the ability to make edits to the new data before import.
11 votes -
Global Add New button in 1:N
Multiple matches are found on Name alone - instead of adding each one-by-one as a new record, add the ability to add all as NEW from 1:Many so once all rows have been determined to not match on anything beyond First/Last name, all can be newly created at once. Could restrict this button only to Name match to prevent sending other potential matches from email, etc.
10 votes -
allow to import non-constituent participant records
We would like to be able to load non-constituents into events as participants via the cloud integration.
10 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
10 votes -
More intuitive relationship matching
Relationship matching and routing works great IF the primary constituent mapped is already in RE.
If the constituent is BRAND new then you are forced to go through the entire data flow for relationships even if the relationship is already in RE and is a 1:1 match. Meaning many unnecessary and inefficient additional clicks.
10 votes -
Abilitly to do relationship matching in RE NXT based on Constituent Import ID
Currently, when importing relationships to existing constituents in RE NXT, the only option for matching to existing constituents is to map to either 'Constituent Lookup ID' or System Record ID. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID' nor the System Record ID. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
10 votes -
MailChimp Automated Campaign Activity in Omatic Cloud
One of the benefits of Mailchimp automations is that you can set them up and they run in the background without needing human intervention. There is similar functionality in Omatic Cloud related to stand-alone campaigns but but not for Automated Campaigns. I'd like to have that functionality so that I can see all the Mailchimp email activity to a constituent without needing to trigger or manually manage when the data gets populated in RE/NXT.
10 votes -
Allow for email campaigns to be excluded from data push to database of record
Would love to be able to exclude email campaigns that are pushing back from Constant Contact to Altru.
9 votes -
Add Ticketmaster Connector
Direct, one-step integration from Ticketmaster would allow non-profit theatres to easily import ticket buyer information directly into Raiser's Edge.
9 votes
- Don't see your idea?