Omatic Cloud
396 results found
-
Add a DonorDrive bi-directional workflow from SOR>DD
The Native DonorDrive connector with Salesforce is bi-directional, allowing the syncing of constituent/contact updates from NPSP/NPC to DonorDrive
1 vote -
Add to more than one group at a time through the RE-LO Constituent Formula in OC
Would like the ability to add to more than one group through the RE - LO Constituent Export formula type in OC. Currently you can only add one group at a time using the "Add to Groups" field.
5 votes -
Daylight Savings Time
When daylight savings time begins or ends, we're seeing scheduled formulas change - i.e. a formula scheduled to pull at 12:01 AM each day shifts to 11:01 PM when daylight savings goes into effect. Could there be a way for the daylight savings time change be automatically built into Omatic based off time zone? Otherwise to consistently retain the 12:01 AM pull, we have to remember to adjust the formula twice a year.
5 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.
22 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.
36 votes -
Make column order in data grids "sticky" per user
Currently in Omatic Cloud data grids, users can click and drag the columns to the right of the action buttons to re-order them. However, upon leaving the data grid and returning to it the columns reset to their default order (alpha by field name). It would be nice if Omatic Cloud would remember custom column order for each formula for each user. There are many times when it is helpful to refer to specific fields in the data grid when choosing whether to add, match, or delete a record but those fields are way off to the right. So it…
26 votes -
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 -
HubSpot Company Object Formula
Currently, we are only able access data from the Contacts object. It will be helpful to also include the Company object or have separate Company based formulas for this connector.
4 votes -
Another User Role for Running Formulas
There is a User Role in Omatic Cloud for "Formula Producer" that grants "the ability to create, run, and modify all the formulas".
It would be nice to have a role for only running a formula. There are times we want someone to be able to run a formula, but don't want them to edit it.
6 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 -
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.
25 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
19 votes -
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 -
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 -
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
- Don't see your idea?