Omatic Cloud
317 results found
-
Enhanced Mappable fields to Transformations
This was a previous uservoice story but there are still gaps with usability with the if/then ability in transformations. Specifically with if/then/else, the cascading transformations are challenging to build out for most users outside of onboarding.
The ability to include mapable fields directly to a transformation, outside of concatenated replace logic, would be very helpful and would allow for a more intuitive user experience. This is current functionality in P2GL and it would be helpful to have in Omatic Cloud as well.
2 votes -
Request to add ability to use sub forms in VolunteerHub
Current functionality is to use the "All Users" form when pulling fields for VolunteerHub. It would be nice to use subforms as sometimes we want to simplify the list of fields volunteers are selecting.
4 votes -
Add percentage of match results to ready buckets
The older version of Omatic Cloud displayed the percentage of matching information between records in our systems (Altru and Constant Contact). This was very helpful to us as we could minimize the amount of data being sent by only sending records with a percentage match under 100%. We would love to have this feature available again.
13 votes -
Release Note Subscriptions
Allow users to subscribe for Release Notification emails and maybe even default that they're sent to client site admins. It could be as simple as a quick email saying when there will be a new release and a link to your Release Notes webpage (https://omatic-cloud.helpdocsonline.com/release-notes).
With other vendors, I add these notes to my work calendar so it's on my radar when changes are coming and helps me triage when something hiccups unexpectedly.
1 vote -
Record match search
It would be helpful to also have the option to include a LinkedIn url address as an option for constituent match search for imports.
1 vote -
Option to get user input when incoming data doesn't match existing data for specified fields
We often have enough information to be confident that the incoming data matches a record in Salesforce. However, whether the better quality data for important fields is in Salesforce or the incoming data is unknown. So we can't confidently overwrite data without a manual validation.
For example, P Ennals might match to Peter Ennals. I am happy this is a valid match and therefore want to set it as a ready record. However, I don't want P to overwrite Peter.
The functionality could be such that I specify per formula which fields require manual validation. E.g. for records where name…
6 votes -
Pull Tribute Data from the Encompass Transactions
Currently, the Tribute Data is not being pulled from the Encompass Transactions Endpoint. We need that information to import.
6 votes -
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 -
Allow pulling an unsubscribe list from constant contact
Currently cannot pull this list. We tried to set this up pulling from the edit date, but that date is not updated when a contact unsubscribes. How else can we pull an unsubscribe list from constant contact?
9 votes -
Allow for email campaigns to be excluded from data push to database of record
Would love to be able to exclude email campaigns that are pushing back from Constant Contact to Altru.
9 votes -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
3 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.
6 votes -
Populate More Example Rows from Luminate Surveys
It would be good to have more example rows populating for Luminate Surveys when working on the Data Mapping page in a formula. When building transformations it's nice to cycle through a few records to make sure the data is transforming as expected.
3 votes -
Ability to apply non biographical data to full constituent spouse/HOH when matched on non-constituent spouse.
In Import Omatic we have this option but not in Omatic Cloud.
4 votes -
SFTP for P2GL
Please add SFTP capabilities for ingesting files from 3rd party CRM's to P2GL.
4 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Abilitly to do relationship matching in RE NXT based on Constituent Import ID
Currently, when importing relationships to existing constituents in RE NXT, the only option for matching to existing constituents is to map to either 'Constituent Lookup ID' or System Record 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' nor the System Record ID. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
10 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 -
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
- Don't see your idea?