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!

393 results found

  1. Release Note Subscriptions

    Allow users to subscribe for Release Notification emails and maybe even default that they're sent to client site admins. It could be as simple as a quick email saying when there will be a new release and a link to your Release Notes webpage (https://omatic-cloud.helpdocsonline.com/release-notes).

    With other vendors, I add these notes to my work calendar so it's on my radar when changes are coming and helps me triage when something hiccups unexpectedly.

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

    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)
  3. Option to get user input when incoming data doesn't match existing data for specified fields

    We often have enough information to be confident that the incoming data matches a record in Salesforce. However, whether the better quality data for important fields is in Salesforce or the incoming data is unknown. So we can't confidently overwrite data without a manual validation.

    For example, P Ennals might match to Peter Ennals. I am happy this is a valid match and therefore want to set it as a ready record. However, I don't want P to overwrite Peter.

    The functionality could be such that I specify per formula which fields require manual validation. E.g. for records where name…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  1 comment  ·  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)
  4. additional -- useful -- logic operators in P2GL

    Can we add some additional -- useful -- logic operators to P2GL?

    *Blank
    *Not Blank
    *Does Not Contain

    Blank and Not Blank are especially useful. Today, without them, we're forced to use 'Equal' or 'Does Not Equal' and then compare that to an unpopulated field. Sometimes, however, if there are spaces in a field, it might look to be blank but isn't really.

    All and all, it's just safer and more efficient to have 'Blank' and 'Not Blank' operators.

    'Does Not Contain' is useful for working against alphanumeric data, and would prevent needing to use more complicated 'If/Then' or 'True/False'…

    5 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  ·  Post to GL  ·  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. Support for line break character (/n)

    Right now we can add line breaks through Concatenation, but there isnt a simple way to force a line break in some more complex situations.

    We use this particularly for notepad text, where we want to summarise a few cells of data into a single notepad, e.g.

    'Signed up for Email Newsletter on the website. /n
    First Name Provided: Alex /n
    Surname Provided: Bishop-Thorpe /n
    Email address provided: alex.bishop-thorpe@'

    Importimatic supported '/n' as a line break character, but this isnt supported by Omatic Cloud. Instead it just renders the text '/n'. If we use the line break as the separator…

    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)
  6. Daylight Savings Time

    When daylight savings time begins or ends, we're seeing scheduled formulas change - i.e. a formula scheduled to pull at 12:01 AM each day shifts to 11:01 PM when daylight savings goes into effect. Could there be a way for the daylight savings time change be automatically built into Omatic based off time zone? Otherwise to consistently retain the 12:01 AM pull, we have to remember to adjust the formula twice a year.

    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)
  7. Add to more than one group at a time through the RE-LO Constituent Formula in OC

    Would like the ability to add to more than one group through the RE - LO Constituent Export formula type in OC. Currently you can only add one group at a time using the "Add to Groups" field.

    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)
  8. 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…

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

    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)
  10. 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)
  11. Pull Opt-Outs from Specific Subscription Lists in Emma

    Currently, there is no way to tell how the connectors are configured if someone opts out of a specific subscription list.

    USE CASE: We would like to add Solicit Codes/Attributes in RE based on if they unsubscribed from a specific list to manage preferences.

    Issue: No way to tell in SOR what preferences have changed.

    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)
  12. Enable File-to-File Transformation & Export in Omatic Cloud

    Currently, Omatic Cloud only allows transformations when importing data into Raiser’s Edge or other connected systems. However, it would be extremely beneficial to have a file-to-file processing option. This would allow users to:

    Upload a spreadsheet, apply transformations, and export the transformed data as a new file (CSV, Excel, etc.).
    Use Omatic’s powerful transformation tools without requiring integration with an external database.
    Improve data cleaning and preparation workflows for reporting, imports, and other external processes.
    This feature would save time and expand Omatic Cloud’s usability beyond direct imports. Please consider adding this functionality in a future update!

    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)
  13. Ability to tag and filter formulas in Omatic Cloud

    Ability to tag and filter formulas in Omatic Cloud. I have over 60 different formulas and most vary from the same set of rules i.e. we have two formulas for one file so we can adjust fields for new and existing records. Right now the tabs are useful but since they are user specific when I sign up a new user I have to spend time helping them find the right formulas. If there were tags I could assign departments, new vs existing, and formula type to make the search easier. It would also be nice to be able to…

    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)
  14. Matching on middle names and birthdates

    We have 70,000 individuals in out database, so we get a lot of people who match on common first and last names. Being able to use middle names or birthdays would be a huge help in distinguishing who's who.

    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)
  15. Transformations: Completely delete/remove data field

    I would like to see that one of the transformations have the ability to completely delete/remove that field. One of the examples that I have come across is for consistuency codes. We use them if someone is giving at a certain amount annually. But if they are not at that level anymore, we need to delete the code. But I can see this being used for attributes or duplicate pieces of contact information.

    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)
  16. Enforce Unique Formula Names

    Formula names should be unique in Omatic Cloud. Multiple formulas with the same name can cause confusion during processing or reporting an issue with support.

    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)
  17. Allow for the Import of Gift Aid Declarations in Omatic Cloud

    Absolutely critical for clients in the UK doing any gift importing. This is a feature that is UK specific but needed to move IOM profiles to OC.

    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)
  18. Allow formula to run against all dates

    We use a constituent formula to sync RE NXT records to LO Donor Groups. Currently, the formula will only sync records modified within the past 30 days, but we may have thousands of records not modified in that date range that still need to be in a particular donor group. Forcing a change in the modified date just unnecessarily increases the volume of records also synced by the Opt In formula. We would like to be able to choose to run the formula against all dates.

    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)
  19. Make lookup fields external ID friendly

    Lookup fields, prior to expanding the object, will only accept the Salesforce GUID, currently. If we want to map to another field, we need to expand the object. Having the lookup field accept any external ID of that object would aid in preventing too many objects mapped and also help to prevent unnecessary related records match work.

    4 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  ·  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)
  20. Classy Endpoint API Field Additions

    Classy Recurring Giving Plans:

    1. Company Name (Available for Classy Transactions): This will be used to determine if a Recurring Gift was given by a Company or Individual.
    2. Primary Source and Secondary Source (Available for Classy Transactions) Needed to populate SF Campaign and GAU Allocation

    Classy Transactions:

    1. ACH Last 4 (Available on Recurring Giving Plans)
    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)
  • Don't see your idea?

Omatic Cloud

Categories