Skip to content

Omatic Cloud

Welcome to the Omatic Cloud feedback forum. Do you have an idea to improve the product? Do you recognize a good idea when you see one? You can create your own ideas and also vote on existing ideas. We want to hear from you!

251 results found

  1. Map Custom ID Fields

    It would be ideal to be able to map a custom Salesforce field to the matching ID list for primary contact matching. We currently have fields we use as ID fields that aren't recognized by Omatic Cloud so we cannot match or dedupe incoming data based on these fields, making our importing a lot less effective.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add a Constituency to BBCRM Mapping Formulas

    I would like to suggest the ability to bring in constituencies for new records in our BBCRM constituent revenue type.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. E-Commerce Luminate Online Shipping Address Field Request

    I am requesting the addition of shipping address fields in the E-Commerce Luminate Online connector. I need a record of the shipping address on the E-Commerce gift in Raiser's Edge.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add option to skip New User Creation

    In certain cases, there are reasons that if no user is matched it would be more applicable to skip that user rather than have new users created. It would be nice to add the option to automatically skip/ignore New Users. Currently they do go into a new user bucket, but we have to manually go in and repeatedly empty the bucket.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Ability to spot differences in email

    When I want to match a record from the document I've attached to Raiser's Edge by way of OMATIC, it would be great if there could be functionality that allows me to choose which email address I want to be on RE. For example, when I am matching Beth Paul (from my document) to Elizabeth Paul (how she's listed in RE), I am given the option to select whether I went to import the name "Beth" or stick with the name as listed on RE "Elizabeth". This is great. Would this be possible with email addresses? For example, on my…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Addition of Classy Mode to Classy Connector

    Add "Is Classy Mode" Field to Import Profile. When importing transaction details from Classy to RE, it's important that the fact that a donor covered processing fees is available to be added to the import profile. If a client wants to track whether or not constituents opted to cover service fees and the percentage in service fees they covered in future RE reports, they are unable to do so because these import fields are unavailable.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add Relationship Attributes

    We would like the ability to send relationship attributes through Omatic Cloud to RENXT.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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
  10. Do not promote non-constituent records

    When matching to a non-constituent spouse record, we would like the ability to NOT automatically promote the spouse record to a full record. We would like to add the non-biographical data to the head of household record.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    planned  ·  Emily Dalton responded
    Thanks 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.
  20. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base