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

131 results found

  1. Ability to ignore a record

    When pulling data into SF there are times when a user wants to ignore or skip a record and not pull it into SF. Use case for this is a list of contacts or oppts with a field value that indicates they are not valid or at the level required for adding to the SOR.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Steve Brewer responded

    Our users now have custom routing available which will allow users to choose to delete records that fit specific criteria in the source data.

  2. Add Custom Fields to the Fundraise Up Connector

    Custom fields in Fundraise Up hold very important information that allows us to easily integrate this data into Raiser's Edge NXT. Before the connector we were able to pull this information in via the flat file and not having these fields makes it difficult to get our full set of gift data when we import.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Steve Brewer responded

    Custom fields for Fundraise Up donations are now available in the Omatic Cloud mapping page. Note, you will need to use transformations to parse the data from the custom fields list to extract that value that you need.

  3. Field Campaign Internal Name Visibility

    Ability to view the Internal Campaign name in hosting when attempting to map Classy Recurring gifts,

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. New Formula Types

    If I create a second API Connection to my RE/NXT database (called RE Maintenance), I’m hoping to use the primary connection to identify specific maintenance scenarios and the second connection to update the data in RE. (Ie, we have a custom field called Minor (under 18) with a Y/N value. I’d like a formula to automagically change it once they reach their 18th birthday.) I currently do this on a monthly basis for many different maintenance scenarios using RE Database View queries and global changes. Automating would be better, more efficient, and more timely.

    OC will allow me to create…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This is now supported! You will need to connect RENXT as a Data Source twice (once for the "Source" and once for the "Destination"). Once the two data sources are created, you will have the option to select one as source and one as a destination in the wizard. Then, you will have formula types available for those connections.

  5. 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  ·  Admin →

    Page size is now saved within Omatic Cloud. It will be saved per user, per formula. Within a formula, it will be applied to all the buckets. New formulas will still default to 15 records, but once you make the change, it will be saved.

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

    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

  7. Allow records causing exceptions to be edited before resending to destination

    Occasionally a record will be rejected by the destination app because the data violates some data formatting rule in that app. The main example in my setup is my Mailchimp lists do not allow non-US Zip codes, so when Omatic tries to create or update a subscriber whose Altru Zip is from a different country, it throws an exception. The only way to get the subscriber into Mailchimp is to either add them manually or temporarily remove the Zip from Altru and force the record to go through the Omatic formula again. It would save a lot of time if…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Anonymous responded

    The ability to perform inline editing within the Destination Exceptions bucket is now available in Omatic Cloud!

  8. Add a time zone selector like IOM.

    I'm having issues with the LO API sending donations in UTC time, which cannot be changed by the "ignore time zone" tool. Having the wrong dates makes reconciliation difficult and looking for donations with wrong dates and changing the manually is very time consuming.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Salesforce  ·  Admin →
  10. Add default data difference option to Ready

    Ready bucket currently defaults to source for any data differences. Add ability to choose source or destination for data differences so when send all or send page is selected, we have control over what is retained in the destination.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. RENXT Gift List Formula Type

    We would like to have the formula type RENXT Gift List > HubSpot. This would allow for relevant gift information to be transferred back in to HubSpot to determine the ROI on email campaigns.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 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)
    You have left! (?) (thinking…)
    1 comment  ·  Post to GL  ·  Admin →
    completed  ·  Steve Brewer responded

    There is now a field available named Uploaded File Name that you can use to map in any area where mapping is supported in a formula.

  13. Add Ability to import Tributes to RENXT

    We would like to import Tribute Data through OC, into RENXT.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Allow for defaulting Recurring Gift Fields on a Gift when Bringing in Recurring Gift Payment

    When bringing in a Recurring Gift Payment to RENXT I would like the ability to default the fields on the Orginal Recurring Gift. This includes bypassing the error message that Fund ID is required. If the Fund is not populated I would like to populate the Fund with the original recurring gift.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Add Classy payment type filter during import - paypal vs. stripe

    The ability to import paypal gifts only and then stripe gifts only would significantly help during import and reconciliation

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Christina Terracin responded

    This scenario is now supported via Custom Routing in Omatic Cloud. To learn more please view https://support.omaticsoftware.com/s/article/Record-Custom-Routing-Overview

  16. Allow mapping to gift subtype and gift code for pledges

    Allow mapping to gift subtype and gift code for pledges. I currently get a message that this in unavailable for pledges.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Christina Terracin responded

    Hi there! We're pleased to share Omatic Cloud now supports more fields for Pledges and Pledge Payments, you can now perform mapping for the following fields:

    Gift Code

    Gift Constituency

    Gift Subtype

    Omatic Cloud supports these fields for both Batch and non-Batch imports.

  17. Add Education>First Post-Secondary School>Major Field to Luminate Online API Call

    Education fields under First Post-Secondary School and Second Post-Secondary School sections in Luminate Online are not available to be mapped in our Luminate Online to Salesforce formula because the majority of the Education fields are not included in the Luminate Online API call. Because we have limited custom fields to use in Luminate, we are using the Major field for our Undergraduate Major tracking. This is crucial to our reporting inside Salesforce and it is a huge limitation that we cannot map the Major field via Omatic Cloud.

    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 →
    completed  ·  Steve Brewer responded

    We have updated the Luminate Online constituent source endpoint to now include each of the first and second post secondary education fields.  These fields are now available for mapping in your Omatic Cloud formulas.

  18. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Steve Brewer responded

    The Remove Custom Text transformation has been updated to allow a user to remove any character from the beginning of a text string. This can be used to remove all leading zeros, or any other character, from a field's value.

  19. Automatically strip leading/trailing spaces from incoming values/source files

    Please bring back Omatic Cloud automatically stripping leading/trailing spaces from incoming values. The previous version of Omatic Cloud did this and the new version does NOT do this which means any data differences have to be accepted one by one. The only other alternative is adding a transformation to remove the spaces. However, it is not possible to specify leading/trailing spaces so this is problematic for many incoming names!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    In today's release, we have added functionality to automatically remove leading and trailing spaces on ingestion. In addition, you will have an option during routing to count/ignore spaces in the destination as a data difference. Spaces will be indicated in the grids with a purple box surrounding the space. 

    Let us know what you think or if you have any questions after the release!

    Best,

    Kristen Gajdica

    Senior Product Manager

  20. Need more flexibility for filtering records in RE NXT List, in order to export

    RE Query allows for greater flexibility in the output of fields from RE than the List option does. For a client with an email connector, who may be using cons codes, solicit codes, attributes, etc. to segment their audiences this is not possible with the List endpoint in RE 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…)
  • Don't see your idea?

Omatic Cloud

Categories