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.

245 results found

  1. Include non-mapped source fields in summary fields to help with decision making.

    We don't want to update fields in LO but want to see the source fields (which are not used in the mapping) in summary fields to assist in making decisions.

    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

  2. Prevent the page from updating/refreshing after every action.

    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

  3. Make inline editing available in 1:Many Matches

    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

  4. We would like to set the default value instead of it going to 15 each time (preferably to 100) in the data queue pages.

    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…)
    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. We would like the ability to sort data in the Needs attention bucket. This is the way they used to be ordered.

    Previous order was:
    1. 1:1 Matches
    2. Multiple Matches
    3. New Records
    4. Destination Exceptions
    5. Formula Exceptions

    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

  6. Would like the ability to freeze 1st 4 columns ; Without these frozen, they are losing sight of data point information.

    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

  7. Deceased indicator

    Display a deceased indicator in the data differences columns of the triage buckets, similar to displaying Mailchimp contact status. This will help with decisions without me needing to step into the record just to find out they're deceased.

    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

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

    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…)
    under review  ·  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

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

  10. Add connector for AlumnIQ

    Would like a connector for AlumIQ for BBCRM OC
    https://www.alumniq.com/

    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  ·  Blackbaud CRM  ·  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. Support "starts with" or "ends with" in Transformations

    When translating data we need more supported options for translating data, for example, "starts with" or "ends with" at minimum.

    7 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

  12. Feedback requested for cascading toast notifications

    With the release on July 2, 2024, we greatly reduced the cascading toast notifications and moved the notifications to the center of the page, as to not impede with interactions within the application. We want to continue to make incremental updates to notifications, so we'd love your feedback!

    What information would you like to see in the notifications? Where and how would you like to access the notifications? How do you use the information to change a behavior or interaction within Omatic Cloud? What else?

    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

  13. 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)
    Close
    Close
    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)
    Close
    Close

  14. Include Uploaded file name in PostToGL FE NXT Batch Description

    To help identify the contents of a FE NXT Journal Entry, it would be helpful if the Journal Description could include the file name of the uploaded file.

    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…)
    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)
    Close
    Close
    under review  ·  AdminSteve Brewer (Product Manager, Omatic) responded

    Thanks JPP for the idea.  We can look at providing the file name as a field that you could choose to use as desired, including using the field as part of a batch description that you could be dynamically building.

  15. Include flat file name on omatic cloud formula history page

    Include flat file name on omatic cloud formula history page. Currently the page shows information like "Formula file upload started," "formula ingestion completed," and "export completed" for the Event column, and details on the number of records processed in the Description column, but it would be nice to include the name of the uploaded file in the Description column so you can easily identify which file was being handled. We use a flat file formula pretty frequently, with unique file names, and this would be very useful.

    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…)
    under review  ·  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. Add/Update Gift Data as part of PostOmatic Processing

    We often use PostOmatic (POM) to apply complex logic, concatenating data from multiple sources in RE to determine the final Debit/Credit accounts to which transactions should be written in our financial systems.

    There is no simple way to look at a gift in RE and say, "This is the Debit/Credit that was used."

    While the output data from POM can be re-imported to RE, currently, this is a secondary manual process. Could POM be updated to include an option for automatically adding the final Debit/Credit outputs to the source gift record?

    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…)
    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
    AdminSteve Brewer (Product Manager, Omatic) responded

    Thanks for the idea JPP.  Can you be more specific about where you want the debit and credit used to be added back to the gift?  There are certainly limitations as to where data could be written back to the gift due to field size constraints as well as considering all of the output that is typically in Post to General Ledger files. 


    Here are a few more questions for consideration:

    What is the goal of having this data in RE/how would that data be used?

    Should there be any considerations if an adjustment is being posted due to adjustments creating reversing entries to reverse out what was previously posted and then having new journal entries created for the updated information?

    What other scenarios might we need to account for if we added a write-back feature?


    Thank you

    Steve Brewer

    Product Manager 

  17. Update Matching with Encompass Connector

    When going from BBCRM to Encompass Matching only allows for custom options and pre-populates with ALL currently mapped fields.

    While this is trying to be helpful, if there are 30 mapped fields it will default to matching all 30. At that point it would be more helpful to not pre-configure matching and let the user configure the matching.

    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  ·  Blackbaud CRM  ·  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. Log when a formula is reprocessed in Activity History

    Currently the activity history does not show when a formula is reprocessed. This info would be helpful especially when working through the exceptions buckets. it would all use to better track errors that are recurring.

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

  19. Ability to map Action Notepad Type

    When importing CC data into NXT via Omatic, the default for Action Notepad Type is "Added via Web View". This default is not effective in allowing us to report to our Board and stakeholders outcomes. After uploading actions we will have to manually change this field.Having the option to define or map this field will give us richer data and better metrics to report on.

    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…)
    1 comment  ·  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

  20. Review specific fields that don't match the source destination

    When importing we are overriding values in our destination system that we may not want to. For example, field X has a value of A in the source data and value of B in the destination - we'd like a way to review this prior to sending to the destination (similar to data differences) so we can make a choice if it's overridden or not. Ideally we'd be able to define these fields as they are unique to our organization and business rules.

    This is similar to the following idea but seemed a little different. Other idea: https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/48105404-option-to-get-user-input-when-incoming-data-doesn

    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…)
    under review  ·  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)
    Close
    Close
← Previous 1 3 4 5 … 12 13
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base

(thinking…)