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!

79 results found

  1. OC Date transformation for D/M/YYYY

    Currently there is a transformation for M/D/YYYY but not D/M/YYYY
    Seeing a lot of "data differences" simply because of OC adding back in a zero when we do not want one.

    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  ·  1 comment  ·  Admin →
  2. Ability to silence or "x" out toast notifications in Omatic Cloud

    Toast notifications can be distracting especially when multiple users are in an Omatic Cloud instance. The notification blocks the "X" button on the formula and prevents another user from closing a formula. When those notifications stack or another user is processing records, it can be a long wait.

    It would be helpful to silence those notifications per user and have the ability to close out of the notification before the processing bar is completed.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Update fields only if new record

    When a formula imports data for new and existing contacts, there may be fields that should only be populated for new records.

    For example, we have source campaign, source, and sub-source to record where a record initially came from. This should only be updated on new records.

    Having a 'only if new' option in the mapping would be really useful. I.e. when selected, the incoming data is ignored when updating existing records, and populated when creating new 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…)
    0 comments  ·  Salesforce  ·  Admin →
    • With the July 2, 2024 release, we added new options for child object matching to add, update, or ignore incoming values depending on whether the child object is matched
  4. 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…)

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

  5. 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…)
  6. Add ability to include archived/unpublished donation forms

    Add the ability to include archived/unpublished forms to the donation form selection in the "Additional Settings (Source)" step. Currently we cannot unpublish or archive any donation form with a recurring gift option in Luminate (which for us is most pages) because Omatic cloud will not pull those transactions once the page is unpublished/archived. This causes unnecessary page clutter in Luminate.

    2 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  ·  Admin →
  7. Add Salesforce Production to Salesforce Production option to Formula Setup

    Would like the ability to create a report in Salesforce Production and have omatic pull that report and make the updates noted in the formula in Salesforce production at a scheduled time. At this time, I can only schedule automatic updates from Salesforce Production to Salesforce Sandbox, which is useless when trying to keep the data clean in the live database

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Salesforce  ·  Admin →
  8. 1 vote
    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 →
  9. POM/P2GL: Summarize Filtered Rows

    POM/P2GL can summarize transactions, creating a GL import file that contains 1 bank line and X revenue lines. This functionality is applied at the configuration level - and, therefore, impacts the entire file output.

    We don't currently have a way of identifying selected transactions (e.g. Adj/Rev) where we do not want these summary transactions to be applied.

    I'd like to see the ability to apply filters to the summary criteria to help drive when the summary should be applied.

    1 vote
    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 →

    Hi JP,


    Thank you for submitting the idea.  I wanted to make you aware that Post to GL currently supports this use case and summarization can be configured to summarize some transactions and not others.  The only requirement is having the information available in the source data to be able to configure the scenarios needed.


    I know I have seen clients have formulas configured with the following scenarios:

    1.  Summarize non-adjustments but not adjustment transactions

    2. Summarize debit transactions but not credit transactions

    3. Summarize specific account numbers but not other account numbers

    4. Summarize transactions for specific funds but not other funds


    There are definitely others that could be considered.

  10. Need Solicit Code End Date field added to BBCRM Fields in OIC/OC

    using Solicit codes to track opt-ins for email subscriptions. The field for Solicit Code End Date isn't available in the fields to map to in OIC.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. pull pledge payments on pledges with multiple payments

    make payments the center of the decision of data to post instead of opportunities

    2 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 →
  12. 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…)
  13. 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…)
  14. Timestamp update after UTC Conversion

    Timestamp to appear with LO time after ignoring UTC conversion clean up.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Salesforce  ·  Admin →
  15. Match & Update - Don't Add

    Salesforce formulas need a setting like RENXT on child objects to allow for control over what happens when a match is or is not found so users can choose not to add new if matches are not found and leave destination as-is if matches are found.

    Example1: Salesforce users importing Benevity files link opportunities between employee and employer via a lookup field with the transaction ID. If the employee or employer doesn't give ($0 gift), we're not creating an opportunity. Destination exceptions present because transaction ID is always present and there's no way to make one blank if it's a…

    2 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  ·  Salesforce  ·  Admin →
  16. 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…)
  17. Add optional questions to fundraisers formula type (classy defined and user defined) to OC

    IOM has Option Questions available to map, but they are missing from OC. Please add these to allow more formula usage.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  18. 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

  19. 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 →

    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.

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

← Previous 1 3 4
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base