Omatic Cloud
112 results found
-
Match on Existing Consent Records
Similar to how you can match on an existing Address, Email, Con Code it would be great if we could match on existing Consent records to avoid duplicates. If we're sending weekly newsletters/mailings out, when our connector runs it adds a new consent record every time
8 votes -
Enable Importing Event Registrations from GiveCampus
The GiveCampus integration currently supports only importing gifts. Events is another large use for the platform and one we're looking to leverage. Being able to utilize this would improve our process flows greatly.
8 votes -
Abililty to map Constituent Import ID when importing soft credits in RE NXT
Currently, when importing gifts with soft credits in RE NXT, the only option for matching to existing constituents is to map to 'Constituent Lookup ID'. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID'. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
7 votes -
Import of Fund Relationships
There is currently no functionality to import new Fund Relationships or update existing ones via import. We would like to track scholarship recipients directly on the fund itself. Providing this functionality would allow us to import the students receiving aid, making your solution even more valuable than it already is.
Thank you!7 votes -
List Management available
Given the plan for RE to move to a "total web solution" which will ultimately replace database view, for users of IOM List Management, could this feature be made available through Omatic Cloud?
7 votes -
Build a Connector for Social Tables
Social Tables is a new application released in 2015 for Event Management with incredible functionality. It would be great to have an integration for it.
7 votes -
Applying Gift to Head of Household (HOH)
Would like to apply incoming gift records to the Head of Household in Raiser's Edge, even if the gift matches the email address of the spouse. If the gift matches to the spouse email address, spouse will also receive soft credit.
7 votes -
Include Marketing Source Code and Receipt Stack
Please include the following fields for mapping:
- Marketing Source Code
- Receipt Stack6 votes -
make classy url available in connector
The url of the Classy Fundraiser's Page is not available as a field to map in the Classy Connector and would be most useful to be able to capture. We have suggested this to Classy as well.
6 votes -
Participant guests in Classy
Would like to see the ability to import guests associated with a participant in Classy to RE NXT event record.
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.
6 votes -
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 -
be able to define "Run Once" to within hours or minutes - not only days
sometimes a gift gets accidentally deleted, so we have to use the "Run Once" function to re-run teh formula. It would help if I could run it for just exactly that single transaction I need to import, rather than a whole day of data which could be thousands of gifts
6 votes -
Add connector for Wufoo online forms
It would be worth looking into how to create a connector service to an online forms site where one can easily custom build an online form and link to RE fields. Wufoo is a great site to start with and has an existing API.
6 votes -
Ability to Add Multiple Constituent & Gift Custom Fields in an Import Profile
Need the ability to add multiple custom fields for constituents and gifts. This would be similar to Virtual Fields in ImportOmatic, as it would be very helpful to have that same flexibility and ability of multiple attributes and additional items in Omatic Cloud so we can switch fully to Omatic Cloud.
5 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.
5 votes -
Add connector for Marketo
Add a connector for RE and Marketo to capture consent/solicit changes and campaign results to Actions.
5 votes -
Allow formula to run against all dates
We use a constituent formula to sync RE NXT records to LO Donor Groups. Currently, the formula will only sync records modified within the past 30 days, but we may have thousands of records not modified in that date range that still need to be in a particular donor group. Forcing a change in the modified date just unnecessarily increases the volume of records also synced by the Opt In formula. We would like to be able to choose to run the formula against all dates.
5 votes -
Be able to export CQS transactions from RE to EN via the connector
Opt-in questions with the type “Opt-in Confirmation” (CQS transactions) are not available to be exported to from RE to EN using the connector. Only QCB opt-in transactions appear.
Engaging Networks have implied that this link should help . https://speca.io/engagingnetworks/engaging-network-services?key=726cda99f0551ef286486bb847f5fb5d#add-or-update-supporter . The name in the REST API is Double Opt-in. The type is CONF
4 votes -
Transformations: Completely delete/remove data field
I would like to see that one of the transformations have the ability to completely delete/remove that field. One of the examples that I have come across is for consistuency codes. We use them if someone is giving at a certain amount annually. But if they are not at that level anymore, we need to delete the code. But I can see this being used for attributes or duplicate pieces of contact information.
4 votes
- Don't see your idea?