Omatic Cloud
294 results found
-
Separate formula Type for HubSpot Email Subscriptions
Currently, the HubSpot formula "Contacts" handles all subscription information. Could this information to be handled separately in a stand alone formula since the "Contacts" formula handles all changes, not just email subscription changes.
The current process is noisy and creates a high volume of records that are unrelated to email subscription changes. This is also problematic for the HubSpot connector given API hits.
4 votesWe are planning to add this feature in Q4 2023!
-
HubSpot Email Information Subscription Dates
It would be very helpful to have Subscription status > history > dates available in the HubSpot Contacts formula. This would allow us to bring in more accurate data when managing email subscriptions
8 votes -
Add NIN to Omatic cloud
For importing Standing Order payments from the bank the only way we can link to Constituents is by a unique ref. We currently store this in the NIN field. Could we get this field added to the omatic cloud when it is added to the SKY API (raised with Blackbaud as well). Thanks
1 vote -
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.
9 votes -
Organization Information in "Verify your account" email
When adding a user to an account, it would be helpful to see the Org Name and potentially the tenant name associated with the email verification. The current email does not include any identifying information and makes confirming access challenging. It would be much easier for users to be able to directly click on the OC URL from the "Verify your email/account" email that is sent out when a user is given access to an OC instance.
1 vote -
Additional Scheduling Options
Right now, we have 3 scheduling options generally (weekly, daily, continuous). A client has requested that we have additional scheduling options, example: twice daily, twice weekly, every two weeks.
2 votes -
Delete Field Value Using Dedicated Syntax
We often have the need to delete/clear a field when importing. It would be great to have a dedicated syntax that we can map to indicate that the mapped field should be replaced with null.
E.g. if we map {DELETE} it would remove the value in the field in Salesforce that we are updating, leaving it blank.
This would allow blank fields to be ignored, whilst giving users a way to very intentionally delete a fields.
Two examples:
1) We have a file of donor data where invalid/incorrect email addresses and phone numbers have been flagged. We can therefore import…
3 votes -
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
- Don't see your idea?