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

13 results found

  1. GiveCampus: Adding Time Zone Selector

    All gifts from GiveCampus are currently coming over with UTC timestamps, making the gift dates inaccurate on some gifts. We need the ability to specify the time zone the gift dates should be in

    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)

    The date/time transform in Omatic Cloud is able to handle the source time format so this suggestion will be closed. A separate User Voice ticket may need to be opened for Classic products (IOM).

  2. GiveCampus: Adding "Donor Covered Fees" as a field

    Donor Covered Fees is a field available in GiveCampus, but not yet available to map in either IOM or OC. Organizations would like this available to track in RE/RENXT.

    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)
  3. add import ID routing

    need to be able to return fields in data differences,

    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)
  4. Create new data selection

    to be able to choose which date to use for filtering

    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)
  5. Select mapped fields in transformations

    It would be of incredible added value if it were possible to select a mapped field in the data transformation option, which would give incredible flexibility to the process of mapping and transforming data between information systems.

    example>

    If the field Appeal = "A" then take the value of the field "Date", if the field Appeal <> "A" then the field = BLANK.

    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)

    With the recently released updates to Transformations, you can accomplish this use case by stacking different types of transformations together.

    For example, to populate Gift Type only if the incoming Gift Amount is not blank you would:

    • Map Appeal
    • Add a "Concatenation" transformation to add Date
    • Add a "Replace" transformation to transform "If does not contain A" to "Blank"
    • Add a remove custom text for "A"


    This will ensure that the Date field coming in is only populated if the Gift Appeal is A.


    Depending on your incoming data, there are many variations and approaches you could take to setting up this transformation logic. We will continue to look into adding new Transformation Types in the future to improve efficiency and capabilities.

    You can find more information about transformations here: http://omatic-cloud.helpdocsonline.com/transformations

  6. Add Translations for RENXT Gift Types

    Translations for all Gift Types in RENXT would be nice. For example, in the front end the type is "Gift-in-Kind", but the API is expecting "Giftinkind"

    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)
  7. Ability to pick a date format for the concatenated date

    This is in relation to batch number naming. When we had this feature in V1 it was great for a variety of reasons and it helped when we had to process backlogged donations using run once. Now I'm having to do tons of workarounds.

    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)
  8. ability to use 'if / then / else' logic for mapping fields

    My file has some rows with gift data and some rows without gift data. In order to import the gift data, we have to map required fields (ex: gift type). But the rows without gifts are creating exceptions because it is still trying to send in the required field but there are no gifts associated with that row.

    Need to the ability to map fields conditionally:
    if gift data exists, then add them (with the mapped values), else ignore

    In this case (RE NXT), the exception that was generated was not as clear as it could have been: 'the gift_splits…

    14 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)

    With the recently released updates to Transformations, you can accomplish this use case by stacking different types of transformations together.


    For example, to populate Gift Type only if the incoming Gift Amount is not blank you would: 

    • Map gift amount
    • Add a "Replace" transformation to transform: "If not Blank" to "True", and "If Blank" to "False" (in that respective order)
    • Add a "Concatenation" transformation and add Gift Type
    • Add a "Replace" transformation to transform "If contains False" to "Blank"
    • Add a remove custom text for "True"

    This will ensure that the Gift Type field coming in is only populated if the Gift Amount is populated.


    Depending on your incoming data, there are many variations and approaches you could take to setting up this transformation logic. We will continue to look into adding new Transformation Types in the future to improve efficiency and capabilities. 


    You can find more information about transformations…

  9. Add another Relationship (RE NXT)

    There are many times when we need to import more than one Relationship at a time. For example, we have flat files that contain both Spouse and Employer information that needs to be mapped separately. I was surprised when I went to map this in a formula and there was no Options dropdown next to Constituent / Relationship. (RE NXT)

    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)
    completed  ·  Emily Dalton responded

    Good news! This request has been addressed on the upgraded Omatic Cloud platform.  We are planning to upgrade users to the new platform starting in Q1. Our goal is to ensure a seamless transition for you. You can find more information about all of the new capabilities and FAQs on our resource page: https://help.omaticsoftware.com/omatic-cloud-upgrade

  10. Additional Addressee/Salutation imports

    It would be great if it were possible to import additional Addressee/Sals. I know this isn't currently possible from RE NXT, but hoping they can make it possible so you can too.

    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)
    completed  ·  Emily Dalton responded
    This is currently available under the section called "Other Name Format". Blackbaud updated the verbiage for Additional Add/Sals in RENXT to be called "Name Formats".
  11. Please add ability to export fundraiser information from RE NXT

    We need to send the following fields out of RE NXT:

    Fundraiser Name

    Fundraiser Type

    Fundraiser Date From

    Thanks!

    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 to send first/latest gift information out of RE NXT

    We need the ability to export fund descriptions from our constituent's first and latest gift through the Omatic Cloud connector. Please let us know when this capability is added!

    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)
  13. Please add "Creditcard holder name" field to Luminate Online Connector Profiles

    This very important field is missing and we need it - thanks!

    15 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)
    completed  ·  Emily Dalton responded

    Are you referring to the Donations profile type or other ones? According to the field documentation we've compiled from Luminate's API resources, the following fields are pulled from the credit card itself: 

    Payment - BillingName - FirstName 

    Payment - BillingName - MiddleName 

    Payment - BillingName - LastName 

    Payment - BillingName - Suffix  


    All of these fields are provided across all of our profile types containing credit card transaction info.  Does this resolve the issue? If not, can you provide more detail? 


    Thanks!  -The Omatic Team

  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base