Omatic Cloud
402 results found
-
Include Date Added and Date Processed fields to review bucket export
I love the new fields for Date Added and Date Processed. It would be nice to include these in the Export that we can create from review buckets to help with troubleshooting in excel.
1 vote -
Export Formula Option from Data Queue
It would be helpful to be able to export the formula from the Data Queue screen rather than having to open the formula and navigate to the mapping page. The button location could be below the "Other Options" section on the formula options flyout.
1 vote -
Ability to Overwrite an Entire Data Extension in SFMC
In some cases, it would be great to be able to instead of update the Data Extension, instead having the ability to Overwrite it with all records in a query. So all records not in the query are removed from the Data Extension.
1 vote -
ability to select what fields are updated separate from mapping/matching fields
It would be helpful if we could use fields for matching but then select which ones we actually want to be updated.
For example, match on name or Constituent ID/Donor ID, but only update the email address or web appeal activity information.3 votes -
Multiple Route to Ready Criteria Options
It would be helpful to have the OR operator for "Route to Ready" based on critera.
Ex: If Classy ID matches, Route to Ready
OR
If First Name/Last Name/Email matches, Route to Ready
3 votes -
Need someway to determine what data DID NOT flow through Omatic
We've had multiple instances of data not flowing from LO through Omatic and into SF. It would be great if there was a list of items that were not pushed through Omatic, so we would know what needed to be moved manually from LO to SF.
0 votes -
Omatic Data Service
We currently have a subscription to Omatic Data Service with IOM to find fuzzy match duplicates during import. This service has been critical in reducing the number of duplicates created in the database. Will ODS be available in IOM+? I'm concerned that duplicate records will start to increase without it. This becomes a big issue after year-end when preparing tax receipt letters if donors have gifts spread over multiple records.
2 votes -
Autoreprocess on Destination Exception Queue
It would be helpful to have retry/resend logic on records in the destination exception queue.
Examples: running Classy Recurrings Gifts and Classy Transactions on a continuous schedule, API limits exceeded, etc. This would be very help especially for clients that have to link records to parent records but want continuous functionality.
3 votes -
Additional Object Picker Field Access for Contact Roles
It would be great to have access to additional fields on the object picker when creating Contact Roles in Salesforce. This would allow for the prevention of duplicate Contact Roles being created in Salesforce if a Contact Role already exists for a Contact on an Opportunity.
Our integration is set up to create a TeamRaiser Participant Contact Role in Salesforce in order to soft credit a person who is fundraising and receives a donation. When a person donates to his/her own fundraising efforts, a donor Contact Role is created (as desired) for that person along with a second Contact Role…
1 vote -
Omatic Actions Sync in RENXT from Omatic Cloud to RENXT WebView: Custom fields with a value of a Link to a record
Omatic Actions Sync in RENXT from Omatic Cloud to RENXT WebView: Custom fields with a value of a Link to a record
As you are moving away from DB view, so will Omatic move away from using Profiles in the IOM Database view system. It will start using the cloud version which connects to RENXT Web View.
In DB view you can add Actions with Action Custom Fields that connect to records. I am expecting that this functionality will also be available soon in the Cloud API for Omatic. It is not currently available.
Please make sure that this is…
2 votes -
1 vote
-
Email notification when formula completes or times-out
Have an option to enter an email address (or two) to notify when a formula completes or when the formula times out.
39 votes -
Add ability to specify the Constituent Code sequency (Primary Consituent Code) when adding or editing
Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.
We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.
The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.
The current behaviour appears to add a new constituent code to…
11 votes -
Related Record Queue Display
It would be helpful to see all records in the Related Record Queue by page rather than a scrolling view. This will make review of records faster and more efficient.
1 vote -
Allow matching on fuzzy address formats
Incoming address may be the same as existing, but with different format. We do not want to overwrite the existing address with one that has an incorrect address format and be constantly doing data clean up to correct. Need an option to only update address if it is different from existing address by a percentage. If it is 90% the same, then don't update address. OR it should give value update option, as it does if incoming title is different
136 votes -
When copying a formula, copy all the setting of that formula (summary grid, matching settings, etc.)
2 votes -
Ability to map Action Notepad Type
When importing CC data into NXT via Omatic, the default for Action Notepad Type is "Added via Web View". This default is not effective in allowing us to report to our Board and stakeholders outcomes. After uploading actions we will have to manually change this field.Having the option to define or map this field will give us richer data and better metrics to report on.
6 votes -
Excessive number of duplicates - when donors give twice within same flat file
If a donor donates twice within the same flat file, Omatic Cloud will generate duplicate records for that donor in Raiser's Edge (because it sends records all at once). In contrast, ImportOmatic sends records one at a time, so if a new donor gives twice, it will be matched the second time.
This is especially problematic for events, when a donor will both buy a registration ticket and make a donation within the same flat file. Multiply this by the majority of the attendees for the event and it results in an excessive number of duplicates. This is a big…
2 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.
27 votes -
Allow import or update of gift reference on existing gifts
Allow us to import updated gift reference data on existing gifts
3 votes
- Don't see your idea?