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!

326 results found

  1. Provide the ability to overwrite an existing value with a null value in MailChimp

    Currently, date fields with null values are not sent through the MC connector. I'm not sure if this also applies to other types of fields.

    This means that if a date field is populated in MC, then updated to a null value in RE, the date will not be overwritten in MC with the new value.

    Because we use these date fields (expiration date, date joined, etc) as segmentation criteria, this affects our marketing campaigns to targeted audiences and can cause significant problems.

    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. Have an export profile in the LO Connector that allows for TeamRaiser registrations to be exported from RE to LO.

    Omatic has gotten TeamRaiser donations to flow really well from Re to LO, but the missing piece is still the offline registrations that need to go from RE to LO. Currently we have to use Blackbaud's arcaic upload system and then still rely on RELO to pull them down into RE because the import for registrations either does not have the ability to recognize offline registrations or cannot recognize the time stamp the LO uses for offline uploads of registrations.

    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)
  3. Participant Summary Note suggestions

    I have a new formula to add Event Participants based on event related email activity. I've got it adding/updating the Participant info correctly but would like to track some of the email specific information (ie, which email, sent when, sent/opened/clicked/etc.) in the Participant Summary Note. I am intentionally not tracking this email information as an Assigned Appeal or an Action as those records have specific functions within my database that do not apply to events. Does anyone have a way to automate getting the information into the Participant Summary Note or any other suggestions for how I might want 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…)
    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)
  4. Dedup records in triage buckets

    I'm finding duplicate records within formula triage buckets which means I either need to process or manually delete each of them. I understand why they sometimes occur but would like within the Reprocess functionality or as a separate action button the ability to remove duplicate records.

    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)
  5. Add ability to move data from BBCRM to Omatic Cloud using Export Definitions

    We are trying to move data between BBCRM and iModules Encompass using Omatic Cloud and would find it very beneficial to use export definitions to send data back and forth rather than queries. The reason is that with export definitions we can be specific about what data to send back and forth. For example, we use constituency to move data in Encompass from our main community to our sub-communities. Therefore we have a need to pull over constituency code. However, we only want to pull certain ones. In query, when we put constituency code in our output, it brings over…

    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)
  6. Use Bulk API for updating EN

    Use the bulk api to upload audiences from Raisers Edge to increase throughput

    3 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Have ability to map to custom attributes for a Participant

    We record event specific information against a participant of an event in RE. Could the endpoints for attributes for a Participant be made available to enable us to add/update these.

    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. Classy Transaction Type in the connector section

    We need to have the Classy transaction type from the payout report in the connector.

    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)
  9. Ability to send multiple values to "select multiple" contact field in Emma

    We want to map our constituent codes in NXT to a corresponding "select multiple" contact field in Emma, such that all of a given constituent's codes are reflected in their Emma profile. Currently there is no way to format or transform the incoming constituent code data in NXT via Omatic such that it successfully selects multiple choices in the corresponding Emma contact field.

    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)
  10. Populate More Example Rows from Luminate Surveys

    It would be good to have more example rows populating for Luminate Surveys when working on the Data Mapping page in a formula. When building transformations it's nice to cycle through a few records to make sure the data is transforming as expected.

    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. FindOmatic email search

    We would like to use FindOmatic to search for records using email addresses.

    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)
  12. Enhanced Mappable fields to Transformations

    This was a previous uservoice story but there are still gaps with usability with the if/then ability in transformations. Specifically with if/then/else, the cascading transformations are challenging to build out for most users outside of onboarding.

    The ability to include mapable fields directly to a transformation, outside of concatenated replace logic, would be very helpful and would allow for a more intuitive user experience. This is current functionality in P2GL and it would be helpful to have in Omatic Cloud as well.

    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. Add additional "Actions" to Ready Bucket

    Have the other actions that you can do in Needs Attention available in the ready bucket (ie. The Add, Override and Delete button).

    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. 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)
  15. Post-to-GL: Create New Journal or Append to Existing Journal

    The process of uploading a file to Post-toGL creates blank or incomplete JE in FE NXT if there are data entry errors in the document that cause the transaction import to fail.

    Could the Post-toGL connection be updated to provide the options / ask the question if the user wants to:

    1. Create a New Journal Entry
    2. Append to an Existing Journal Entry

    This update would reduce the number of empty or incorrect JE that have to be deleted from FE NXT.

    3 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  ·  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)
  16. Provide a merge option for records merged in RENXT and corresponding records updating in Engaging Networks

    Provide a merge option for records merged in RENXT and corresponding records updating in Engaging Networks

    3 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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)
  18. Update FE NXT Batch Desicription on import error

    Post to GL creates the JE batch and then progresses through importing the transactions. If a transaction results in an error, Post to GL stops the import process—however, it may have completed a partial import, and that partial import may be "in balance."

    It would be helpful if, when Post to GL fails due to a transaction error, the JE batch description could be updated to append an error message so Finance is aware that the batch was not created successfully.

    3 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  ·  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)
  19. 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)
  20. Add Ability to Clear Fields in Luminate Online

    Currently, we are unable to clear fields in Luminate Online when we know data no longer exists or is inactive. It is a risk to not enable a way to clear data in Luminate Online, as the data could flow back into RE undoing the data staff changed. A null value should not clear a field, rather use a character like ~ to indiciate a field should be cleared. This should work for any data type (date, text).

    3 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  ·  Admin →
    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

Feedback and Knowledge Base