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.

9 results found

  1. HubSpot Email Information Subscription Dates

    It would be very helpful to have Subscription status > history > dates available in the HubSpot Contacts formula. This would allow us to bring in more accurate data when managing email subscriptions

    9 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…)
    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)
    Close
    Close

  2. Custom routing of records

    Sometimes records need additional review steps and currently we are capturing those notes in an email/document to work through outside of the formula. We think Custom routing of records may help with this as it would allow us to set criteria (or decided on the fly) to route records to a special bucket, for instance, to review later. This would be a time-saving enhancement.

    6 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…)
    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)
    Close
    Close

  3. OC Date transformation for D/M/YYYY

    Currently there is a transformation for M/D/YYYY but not D/M/YYYY
    Seeing a lot of "data differences" simply because of OC adding back in a zero when we do not want one.

    6 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…)
    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)
    Close
    Close

  4. SF Leads Matching on Contacts and If the Contact does not exist create a Lead

    When attempting to add Leads to Salesforce using the Any Objects Formula, we would like the ability to look for Contacts first to see if a match exists. if no contact is found we would like to add them as a lead.

    Use Case: When bringing in a file of Leads they may or may not exist in SF. If they exist as a contact in SF we would not want that lead to be created. If no contact is found we would like to have them as a lead rather than a contact.

    4 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…)
    planned  ·  2 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

  5. Separate formula Type for HubSpot Email Subscriptions

    Currently, the HubSpot formula "Contacts" handles all subscription information. Could this information to be handled separately in a stand alone formula since the "Contacts" formula handles all changes, not just email subscription changes.

    The current process is noisy and creates a high volume of records that are unrelated to email subscription changes. This is also problematic for the HubSpot connector given API hits.

    4 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…)
    2 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. Name fields from Stripe to populated

    Stripe specific parsing reques

    3 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…)
    planned  ·  2 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

  7. Ability to Map to "Activist Code" in EveryAction Connector

    The Activist Code is not available in the EveryAction connector right now, but we need it in order to create Constituent Codes in RENXT. Ideally this would sit in a Contact/Bio formula in the case that the Con Code is required to create new Constituents.

    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

  8. Custom Fields in Every Action Connector on Contributions

    It looks like custom fields are available for Contacts in the EveryAction connector, but we can't access them on the Contribution formulas. Example--we're looking for a custom "Fund" field that has been created to further breakout gifts, but we are not able to map to this right now

    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  ·  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

  9. 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)
    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
    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.
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base

(thinking…)