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!
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

73 results found

  1. Add connector for RENXT and Cvent

    Add a connector for RE and Cvent to capture new/updated contact and consent updates and event campaign outcomes.

    3 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)
  2. Add connector for Marketo

    Add a connector for RE and Marketo to capture consent/solicit changes and campaign results to Actions.

    5 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)
  3. 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.

    6 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)
  4. Allow phone match as a search scenario

    Currently, OC does not have phone number available as a search scenario even when phone is mapped within a formula. This is essential to have because we otherwise wind up with unnecessary duplicates that could have been prevented.

    2 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)
  5. 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)
  6. Show "Incoming Date/Time" of Record During Matching

    We currently have a problem if the record comes in multiple times, we don't know which record is the latest one. You almost have to export the data and review it column to column for an individual.
    It would be nice to include the date/time when the record was added to the matching screen. Right now we can see date/time for exceptions, so it would be nice to see that on the matching.

    3 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)
  7. Skip Days for Scheduling (Allow for weekday only)

    Currently, you can only select daily or weekly. I think it would be beneficial to have it only run on Weekdays. That way records don't pile up over the weekend and risk duplicate records from showing up if multiple changes happened. This has happened when people submit multiple surveys or they have multiple scheduled gifts. And there is no way from the interface to tell which record is the latest.

    3 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)
  8. Enforce Default Data Differences Selection During Setup

    It would be great to make the "Default Data Differences" selection more transparent to the user during setup. It opens them up to the risk of overwriting data in mass if they are sending records from the "Ready" bucket and have left the default difference as Source and have not switched it to Destination.

    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)
  9. Excessive number of duplicates - when donors give twice within same flat file

    If a donor donates twice within the same flat file, Omatic Cloud will generate duplicate records for that donor in Raiser's Edge (because it sends records all at once). In contrast, ImportOmatic sends records one at a time, so if a new donor gives twice, it will be matched the second time.

    This is especially problematic for events, when a donor will both buy a registration ticket and make a donation within the same flat file. Multiply this by the majority of the attendees for the event and it results in an excessive number of duplicates. This is a big…

    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)
  10. Split gift by percentage

    Add the ability to transform gifts by a set percentage of the gift amount in order to create a split gift with multiple funds. Example, 80% of the gift to one fund, 20% to another

    3 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)
  11. Advanced Name Processing for Omatic Cloud

    Currently there is only a way to have exact matches on records. It would be helpful to have an Advanced Name matching option in Omatic Cloud, which is similar to the IOM option to score likelihood that a similar record exists in the system.

    When a similar record is found, the records could go to Needs Attention for review, with an option to create New or Match.

    The example of this is if a last name has an extra space or with multiple last names with a hyphen separating them.

    It is faster for me to review Needs Attention records,…

    8 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. Add ability to specify the Constituent Code sequency (Primary Consituent Code) when adding or editing

    Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.

    We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.

    The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.

    The current behaviour appears to add a new constituent code to…

    3 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)
  13. Exclude Administrators

    Currently, LO connector imports administrators to Raiser's Edge. However, you can't update Luminate Administrators with LO connector, which is good.

    The profile should ONLY work with constituents, NOT user accounts. Filtering out administrators should be an option without a group filter from the profile settings.

    3 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. Integrations/Formulas | Mapping | Total Sum of Two Cells/Columns from an Import File

    Built-in feature that allows combining two column headings to create a total sum during the mapping process.

    Example: scenarios of summing platform fees and transaction fees.

    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)
  15. Deceased indicator

    Display a deceased indicator in the data differences columns of the triage buckets, similar to displaying Mailchimp contact status. This will help with decisions without me needing to step into the record just to find out they're deceased.

    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)
  16. 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.

    4 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)
  17. 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.

    4 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)
  18. Adding opportunity_ID to link actions to opportunities (proposals)

    In reviewing the SKY API documentation on importing Actions into RENXT, there is a field called “opportunity_id” that would allow us to link actions and opportunities/proposals. That field is not available when mapping an Omatic Formula. That would be huge.

    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)
  19. Add Title as one of the fields for mapping on VolunteerHub

    Add Title as one of the fields for mapping on VolunteerHub on ImportOmatic. Currently this is not one of the available fields: https://omaticsoftware.my.site.com/Support/s/article/What-Fields-are-Available-for-Mapping-from-VolunteerHub

    3 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)
  20. Send to a specific triage bucket based on a Mailchimp status field results returned during matching.

    Triage currently takes specific match situations into account but I'd like to send records where Mailchimp returned "Cleaned" or "Unsubscribed" directly to the Exceptions triage bucket regardless of matching criteria. This will allow me to automate the Ready triage bucket instead of needing to review it before sending the record updates to Mailchimp. This matters because I'm trying to reduce the overall number of API transactions (Blackbaud has a threshold over which they charge me extra).

    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)
← Previous 1 3 4
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base