Omatic Cloud
317 results found
-
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
3 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.
3 votes -
Add unmapped fields to grid options
We would like to show an ID field in the grid options that isn't in both systems.
1 vote -
Update email address type when importing new email
When importing to existing constituent records and matching on email address, it would be great to be able to import non-matching email addresses to a new email type, such as Email 1, Email 2, etc.
8 votes -
Rearrange grid columns & save column order
In the upgraded Omatic Cloud, it'd be nice to be able to rearrange grid columns, and as another user mentioned, have the custom column order persist when a user leaves the page:
https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/46297684-make-column-order-in-data-grids-sticky-per-user6 votes -
Organize formula's in a way that makes sense to me
In Omatic Cloud, on the Integrations page, it already organizes formulas by datasource, but I would like to organize them in a different way that makes more sense to my organization/data flow.
I may want to organize them by business flow (ex: Email Activity formulas vs Constituent formulas).
I propose a way to create a custom organization for my formulas on the Integrations page that allows me to be more efficient in my day to day.
19 votes -
On the Post to GL 'View History' screen, add a column that shows how long a job took to run
On the 'View History' screen, can we see how long a job took to run?
Having the duration data would help clients be able to gauge the duration of future posting processes and even when they should be kicked-off, etc.
Eg, if running 9K records took 80 minutes, and my next posting is 13K records, I should plan for it to take around 2 hours, etc.
1 vote -
Date Cleanup Format in mapping for Unix timestamps
We have a handful of connectors, example Hubspot, that save dates in a Unix timestamp format. A cleanup for date fields that will automatically changes dates to this Unix timestamp format would be helpful when integrating with these connectors. This will reduce destination exceptions caused by date format issues.
2 votes -
Sample Data (not enough of it)
Sample data provided when configuring new P2GL formulas is limited to 20 or 25 rows of transactions, which typically is not enough sample data to ensure that formula configurations are accurate and doing what the client needs. Two examples:
In one case there were transformations configured that looked right on the first 20 rows of data, but we couldn't see that the logic was incorrect on other rows. It was not until the client ran the post and saw an error on row 190 that we were alerted that the logic needed to be refined.
In another case, skip row…
2 votes -
Print out P2GL formulas
Currently there is no ability to print out P2GL formula configuration or logic threads. Since formulas cannot currently be copied, they have to be replicated manually and the inability to print formula configuration tremendously hampers that effort. This is even true when working to apply logic from one client's formula to another -- since the logic thread cannot be printed, it's challenging to recreate from memory and/or to toggle back and forth between formulas/monitors, etc.
2 votes -
Encompass Email Activity Connector needs a option to "Select from Current active Select Campaigns(s) and any future active Select Campaigns
When attempting to bring in Encompass Email Activity we can only select All current campaigns. The problem with this is that when the campaign is added in encompass it is not included when running the next run unless the client manually adds it.
I have attached what is in SFMC Email Activity and Encompass Email Activity to compare.
7 votes -
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 -
Head of Household - RENXT
We would like the ability to map to the "Head of Household" field in RENXT
3 votes -
Omatic Cloud Encompass Transactions Merchant Account Filter
We need a filter added to the Encompass transactions cloud connector to be able to filter by merchant account when creating a new transactions profile. It would be in the dropdown for "Do you need to filter the incoming data".
0 votes -
Archiving constituent attributes when changed by ImportOmatic
This is a bit of a pie-in-the-sky (and specific) dream, but I'm going to put it out there nonetheless:
We use Omatic Cloud to update values in an already-existing Constituent Attribute category. Currently, we can use Omatic Cloud to update the Constituent Attribute if the import has a different value than the existing value in the record. However, we want a way to archive the previous value when it is replaced (like how in ImportOmatic, old addresses can be switched to a different category when a new address is found). We've been able to build out a workaround by adding…
0 votes -
Ability to map Luminate online cross references via API in the Omatic Cloud
Luminate stores values here for its web services and accessing them would make for more efficient, straight forward mapping in the Omatic formulas. Specifically, these cross-reference types would be most helpful to CHLA:
- Donation Form Cross-Reference
-Donation Options and Designations
-TeamRaiser Cross-Reference
Navigation in Luminate Online: Data Management / Import/Export / Cross-Reference Types0 votes -
Matching records in Ready/1:1/1:N WITHOUT it updating the other system
For example, in a Mailchimp to Raisers Edge connection, there should be an option when setting up a formula to use items for matching but that doesn't meant when the records are matched that Mailchimp updates RE.
For instance, we have a lot of couples in our database, but they have separate emails so they have separate Mailchimp records. If somehow during triage/Needs Attention I miss that the names are different, or they go through to the Ready bucket and I miss it, then RE has been updated to 1 person's name thereby messing up the database.
0 votes -
Filter function in 1:1 and 1:N
It would be wonderful to be able to not only discard/ignore certain records below a certain threshold, but it would be super helpful to add a filter function to the MATCH column to be able to filter by what the records are matching on. i.e. only pulling up those records that matched on Email, or Email and Name. This would be particularly helpful for the Mailchimp to Raisers Edge and vice versa formulas.
0 votes -
Custom routing of records
Sometimes records need additional review steps and currently we are capturing those notes in an email/document to work through outside of the formula. We think Custom routing of records may help with this as it would allow us to set criteria (or decided on the fly) to route records to a special bucket, for instance, to review later. This would be a time-saving enhancement.
9 votes -
Enhanced override button functionality
Whenever the override button is utilized to match to an existing CRM record, Omatic does not provide the opportunity to select data that may differ between the LO record and CRM record before confirming the match (as is the case when utilizing "match" button). Is this something that can be addressed in the future?
Currently, source data overrides destination data when you using the match override; which trigger the need to update records manually outside of the Omatic Cloud so being able to see the data differences for match overrides to pick whether to keep destination data or use source…
0 votes
- Don't see your idea?