Omatic Cloud
390 results found
-
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.
7 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…
20 votes -
Audit trail on P2GL formulas
We need a way to identify who (which user) created and last changed a P2GL (including POM) formula. We also need an audit trail to identify who may have deleted a P2GL formula.
1 vote -
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…
21 votes -
Changing address type when new address is found
In ImportOmatic, when a new address is imported for an existing constituent, there is the ability for the user to determine how the outdated address' type should be changed in Raiser's Edge (e.g. it can be changed from "Home" to "Previous Address") In order to keep data clean and differentiated after imports, I wish that Omatic had a similar functionality.
27 votes -
Salesforce Opportunity Name: Only Add if New
When adding a new opportunity SF requires an Opportunity Name, but Salesforce ends up changing the name after the opportunity is added anyway. When an opportunity is updated it will change the name to whatever you have mapped as the Opportunity Name. Then a workflow is needed to change them back.
1 vote -
It would be an improvement if we could have Payout date as an option for mapping.
When bringing gifts over from classy the GL post date is not matching our deposit dates and this is causing issues with finance. If we had the ability to map the payout date to the GL post date that would make the financial process cleaner and much smoother without manual global changes.
6 votes -
Have ability to map to custom attributes for a Participant
We record event specific information against a participant of an event in RE. Could the endpoints for attributes for a Participant be made available to enable us to add/update these.
10 votes -
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.
24 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
16 votes -
3 votes
-
Classy Endpoint API Field Additions
Classy Recurring Giving Plans:
- Company Name (Available for Classy Transactions): This will be used to determine if a Recurring Gift was given by a Company or Individual.
- Primary Source and Secondary Source (Available for Classy Transactions) Needed to populate SF Campaign and GAU Allocation
Classy Transactions:
- ACH Last 4 (Available on Recurring Giving Plans)
4 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Allow all custom questions in a single formula for Classy connector
If "include custom questions" setting is checked, all questions must match identically across campaigns to be in the same formula, resulting in many formulas needing to be processed separately. Allow ability to include all custom questions, regardless of matching to be mapped in a single formula.
8 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
1 vote
-
Phone format for UK
In ImportOmatic with the dictionaries we had ability to check if the phone number was less then 11 characters and add a '0' at the beginning of the string
1 vote -
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 -
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.
12 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.
17 votes
- Don't see your idea?