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!

How can we improve Omatic Cloud?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

364 results found

  1. Build a suppression that does not rely on an Luminate Online group

    Currently we use LO group (query based) for suppression in formula 1 to exclude undesirable records, records only have name and email, records come from facebook signup/donation, etc. However, there are 2 major limitations to these query based LO groups:

    1. Query tool in LO has a very limited selection, and we can not access and use
      'Last Modified By' field. The reason we want to use that field is:
      a. Users (admin) need to update records in LO: merge, update bio info, etc.

      b. Background processes also update LO records: calculate Engagement Factor

    2. Group can only be rebuilt Once per…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  2. Filter function in 1:1 and 1:N

    It would be wonderful to be able to not only discard/ignore certain records below a certain threshold, but it would be super helpful to add a filter function to the MATCH column to be able to filter by what the records are matching on. i.e. only pulling up those records that matched on Email, or Email and Name. This would be particularly helpful for the Mailchimp to Raisers Edge and vice versa formulas.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  3. Matching records in Ready/1:1/1:N WITHOUT it updating the other system

    For example, in a Mailchimp to Raisers Edge connection, there should be an option when setting up a formula to use items for matching but that doesn't meant when the records are matched that Mailchimp updates RE.

    For instance, we have a lot of couples in our database, but they have separate emails so they have separate Mailchimp records. If somehow during triage/Needs Attention I miss that the names are different, or they go through to the Ready bucket and I miss it, then RE has been updated to 1 person's name thereby messing up the database.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  4. Ability to map Luminate online cross references via API in the Omatic Cloud

    Luminate stores values here for its web services and accessing them would make for more efficient, straight forward mapping in the Omatic formulas. Specifically, these cross-reference types would be most helpful to CHLA:

    - Donation Form Cross-Reference
    -Donation Options and Designations
    -TeamRaiser Cross-Reference

    Navigation in Luminate Online: Data Management / Import/Export / Cross-Reference Types

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  5. Archiving constituent attributes when changed by ImportOmatic

    This is a bit of a pie-in-the-sky (and specific) dream, but I'm going to put it out there nonetheless:

    We use Omatic Cloud to update values in an already-existing Constituent Attribute category. Currently, we can use Omatic Cloud to update the Constituent Attribute if the import has a different value than the existing value in the record. However, we want a way to archive the previous value when it is replaced (like how in ImportOmatic, old addresses can be switched to a different category when a new address is found). We've been able to build out a workaround by adding…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  6. Omatic Cloud Encompass Transactions Merchant Account Filter

    We need a filter added to the Encompass transactions cloud connector to be able to filter by merchant account when creating a new transactions profile. It would be in the dropdown for "Do you need to filter the incoming data".

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  7. Add Payout ID and Date to the API

    Payout ID and Payout Date added to the API for reconciling between P2GL and OC integration. It's a critical information requirement.

    0 votes
    Vote

    We're glad you're here

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Able to map Credit Card Brand from Stripe

    requested the Brand name for credit card to be added to the connector.

    0 votes
    Vote

    We're glad you're here

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Request for First and Last Name fields for attendees in Fundraisers profile/formula

    Ability to import first and last names for event attendees as separate fields

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Raiser's Edge NXT  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Request to add more retries to HubSpot endpoint

    No API limit errors between formulas

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Raiser's Edge NXT  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Additional Matching Options for HubSpot

    Currently, there only search scenarios for HubSpot are 1) Email/ID 2) Email 3) ID/Name 4) ID

    The issue with this is that many RENXT records have multiple emails and that is showing up as a new record in HubSpot. Additionally, the ID match is only HubSpot Contact ID. It would be very helpful to have an ID match that allows various IDs like RENXT Lookup ID/Constituent ID.

    A Name search scenario would also be helpful

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  12. ZIP code matching in Salesforce

    Currently, 5-digit ZIP codes and 9-digit ZIP codes (where the first 5 digits are the same) will not match when attempting to match incoming records using address as matching criteria. This allows duplicate contacts to be added to Salesforce since Omatic does not match on the address when ZIP is one of the address field criteria.

    0 votes
    Vote

    We're glad you're here

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Child object matching on address in Salesforce

    Currently, address is not a child object in Salesforce, so when address fields are mapped, address data can be overwritten or duplicate contacts can be added when addresses are different (depending on matching criteria). Child object matching on address would help address this issue.

    0 votes
    Vote

    We're glad you're here

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Need someway to determine what data DID NOT flow through Omatic

    We've had multiple instances of data not flowing from LO through Omatic and into SF. It would be great if there was a list of items that were not pushed through Omatic, so we would know what needed to be moved manually from LO to SF.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  15. Ability to "deactivate" user without deleting in Omatic Cloud

    If a user needs to go on extended leave but should not have access to Omatic Cloud, the only current option is to delete their record (and possible history associated with the record). It would be helpful to have the option to temporarily deactivate a non temporary user.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  16. Engaging Networks P2P Transaction Types

    EN just released new P2P transaction types - when will these be available in Omatic to import?
    https://developer.engagingnetworks.net/site/peer-to-peer/#a_summary_of_the_new_transaction_types

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  17. Name Formats - Custom Checkbox

    It would be helpful for OC to have the "Custom" Checkbox for Name Formats. This is currently supported by the SKYAPI but not yet available in OC. https://developer.sky.blackbaud.com/api#api=56b76470069a0509c8f1c5b3&operation=EditConstituentNameFormat

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  18. Match search on existing relationships within record

    It would be helpful to match on existing relationships that already exist on a record vs the entire database. For example, if there are duplicates of a non constituent organization relationship, it wouldn't be reasonably possible to narrow down which value was the existing relationship without opening up all the records to review first. Use case - schools, company relationships.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  19. 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)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  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)
    Close
    Close

  20. Enhanced override button functionality

    Whenever the override button is utilized to match to an existing CRM record, Omatic does not provide the opportunity to select data that may differ between the LO record and CRM record before confirming the match (as is the case when utilizing "match" button). Is this something that can be addressed in the future?

    Currently, source data overrides destination data when you using the match override; which trigger the need to update records manually outside of the Omatic Cloud so being able to see the data differences for match overrides to pick whether to keep destination data or use source…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  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)
    Close
    Close
1 2 … 15 16 18
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base

(thinking…)