Omatic Cloud
269 results found
-
Ability to Write Back Transaction ID when Sending Offline Donations for Luminate and Classy
I would like the ability to send back a transaction ID to an offline gift from either RENXT or SF to (LO or Classy).
Idea:
1. Allow for Filtering of Only Offline Donations from both Luminate and Classy Systems. This will allow us the ability to have formulas dedicated to updating offline donations back in SF. This would not work for RENXT since updating is not available.1 vote -
Make lookup fields external ID friendly
Lookup fields, prior to expanding the object, will only accept the Salesforce GUID, currently. If we want to map to another field, we need to expand the object. Having the lookup field accept any external ID of that object would aid in preventing too many objects mapped and also help to prevent unnecessary related records match work.
4 votes -
RENXT Tags
We would like to be able to use RENXT Tags for mapping to HubSpot. This field is currently available in NXT but not available in RENXT List to HubSpot formulas.
1 vote -
Error Message When OC Mapping Not Saved
It would be great if there was a pop-up error when the mappings are not saved successfully. Right now you can select "Save and Next" and it looks like nothing happens. It does give you a "Saved Successful" message if the mapping saves, but it isn't obvious to a new user if something is causing an error. Specifics on what is causing the error would be helpful too, so you can eliminate the need to click through each section to find the field causing the issue.
1 vote -
Add RE NXT tax declaration to list of available fields
To use Omatic for gift imports in the UK we need to be able to add tax declaration information for the donor. These fields have been added to the Sky API now, so could they also be added for mapping in Omatic Cloud?
1 vote -
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.
5 votes -
Extend date range to allow for pulling data older than 30 days when MailChimp is the data source
Users need to be able to go beyond the thirty-day date-range limit to process older data from MailChimp when it is the data source for the Omatic Cloud formula.
0 votes -
P2GL Activity History
It would be helpful to have Activity History for Post to General Ledger formulas. This would allow for an audit trail when trying to troubleshoot errors or instances when a formula was work previously and is no longer working.
2 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…
7 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 -
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.
3 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.
18 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…
3 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
- Don't see your idea?