Omatic Cloud
284 results found
-
Trash bucket for deleted record rows
When we delete a record from the ready or needs attention bucket it would be nice to have a notification or send records to a new bucket we can review later. It is so easy to accidentally hit the delete icon.
0 votes -
Include user name for API reset or login so you can see who reset the API
Hello I am looking for a quick way to confirm who (what user) reset or set the API. Would it be possible to add in a user ID to the reset? See attached screen shot.
0 votes -
Add Relationship Attributes
We would like the ability to send relationship attributes through Omatic Cloud to RENXT.
0 votes
Emily Dalton
responded
Hi Anna, In RENXT, if you add an attribute to a relationship, it requires that relationship to be a full constituent. This is a bit different than how relationship attributes functioned in RE7. By mapping relationship attributes through RENXT, would you be okay with those records automatically being promoted to full constituents? Best, Kristen -
Settings to manage SF use of API calls...
There may be situations (testing) or initial synching where records in a source system or in Salesforce itself may trigger lots of records to synch. when running continuously, this has the potential to consumer a LOT of API calls where no one would notice. maxing out API calls in SF may cause other business critical functions to fail. so is there a way to tell omatic cloud what the limit of API calls is or set some threshold for omatic cloud to keep track of and not exceed in a 24 hour period. suggest allowing a few settings: * threshold…
0 votes -
Ability for end users to reset last modified cutoff date on Mailchimp-source formulas
Please add the ability for end users to set the "last run" date and time formulas will use when determining which records to pull from Mailchimp. This way if some process is run affecting a lot of Mailchimp records at once we can avoid getting thousands of records in our Mailchimp-sourced formulas that don't really need to be processed, by setting the "last run" date and time to a point after the Mailchimp process was run.
0 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…
22 votes -
Allow Groups filter to exclude a group instead of include
Thank you for implementing my idea about limiting the records processed in Mailchimp-sourced formula to just records in a certain Mailchimp interest group. More helpful to us than this would be the ability to exclude records in an interest group. This is because we do want the formula to include new records that were added to Mailchimp via a signup form, and those records would not be in the group in question yet (we are using this feature with a hidden group, so subscribers can't select it when signing up). Thank you for considering this feature enhancement. Bill
0 votes -
Setting Formatting for Primary Addressee & Salutation for New Constituents Only
Ability to set the formatting for Primary Addressee and Salutation for new Constituents only, or be able to review those as data differences for existing constituents.
26 votes -
Do not create a child object if the value is blank
When creating an Address, Attribute or Note, there are some fields which sometimes need to be defined such as Address Type, Preferred, Attribute Category, and Note Type. This causes these related records to be created as blank records with only the defined values. It would be helpful if these could function similarly to the Email and Phone related records, where if the value is blank, even if the type is defined, the record is not created.
0 votes -
Delete Interests from Altru record when subscriber no longer meets criteria
To the extent the Altru API allows this, it would be useful if an Omatic formula could remove an Interest from the matching Altru record when a Mailchimp subscriber leaves the Group associated with that Interest. Otherwise the Interests on the Altru constituent side will likely become out of sync with the Groups on the Mailchimp subscriber side.
0 votes -
Add ability to map Email Type and Primary Email for new Altru records only
We would like the ability to set the Email Type and Primary Email flag in Altru only if a new constituent is being added to Altru in an OIC formula. As it stands now, we have those fields unmapped because we don't want to risk OIC changing a record's existing Email Type or Primary Email Address. This means we have to go into any new records created by the formula and manually set the Email Type and Primary Email flag.
0 votes -
Add option for formulas to consider null vs non-null a match
Currently if a mapped field is configured to be checked for data differences and that field is NULL in either the source or destination record but not the other, the field is flagged as a data difference. In some formulas it would be nice to be able to choose whether to consider NULL vs NOT NULL as a match for each field instead of always defaulting it to a data difference. This is especially relevant when matching on Altru Alt Lookup IDs since those will often be NULL in Altru until they are first populated by an OIC formula.
0 votesThanks for bringing this to our attention! We've got this on the slate to be researched, along with other ways we can improve the handling of common/consistent Data Differences. -
Add the ability to triage on ZIP and other mapped fields
Some of our Mailchimp signup forms collect subscribers' ZIP codes. When pulling those into Altru, it would be helpful to be able to set up the formula to put potential matches in Needs Attention if the Mailchimp ZIP code is different from the mapped Altru ZIP code. Ideally, any mapped field that exists in both MC and Altru should be available to triage on.
0 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 -
Add Team Captain Name and Participant Name Fields to LO TeamRaiser Gift
The IDs for gift linking are awesome, but many clients also need to associate the participant name and team captain name with the gift as well (usually a gift attribute or reference). These fields are available through standard LO reports, could these two fields also come down through the connector API?
0 votes -
Add 'Accounting Code' field to available field mapping for LO Calendar Event Profile
Many users are using the 'Accounting Code' to associate RE gift coding with a specific LO Calendar Event - This field does not appear to be an available mapping option on the Calendar Event Attendee profile.
13 votes -
Have an export profile in the LO Connector that allows for TeamRaiser registrations to be exported from RE to LO.
Omatic has gotten TeamRaiser donations to flow really well from Re to LO, but the missing piece is still the offline registrations that need to go from RE to LO. Currently we have to use Blackbaud's arcaic upload system and then still rely on RELO to pull them down into RE because the import for registrations either does not have the ability to recognize offline registrations or cannot recognize the time stamp the LO uses for offline uploads of registrations.
3 votes -
MailChimp Connector for Adobe Campaign
Please add a connector for Adobe Campaign
1 vote -
Provide the ability to overwrite an existing value with a null value in MailChimp
Currently, date fields with null values are not sent through the MC connector. I'm not sure if this also applies to other types of fields.
This means that if a date field is populated in MC, then updated to a null value in RE, the date will not be overwritten in MC with the new value.
Because we use these date fields (expiration date, date joined, etc) as segmentation criteria, this affects our marketing campaigns to targeted audiences and can cause significant problems.
3 votes -
For the VolunteerHub connector, change the date range field from "registration date" to "event date"
When bringing in Volunteer information from VolunteerHub, it would make more sense for the date range to be "event date" rather than "registration date" because the date someone registers for an event doesn't really matter. With this current set-up, it misses people who signed up for an even event before the date range even if they actually volunteered during the date range.
28 votes
- Don't see your idea?