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!

17 results found

  1. Option to get user input when incoming data doesn't match existing data for specified fields

    We often have enough information to be confident that the incoming data matches a record in Salesforce. However, whether the better quality data for important fields is in Salesforce or the incoming data is unknown. So we can't confidently overwrite data without a manual validation.

    For example, P Ennals might match to Peter Ennals. I am happy this is a valid match and therefore want to set it as a ready record. However, I don't want P to overwrite Peter.

    The functionality could be such that I specify per formula which fields require manual validation. E.g. for records where name…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  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)
  2. Make lookup fields external ID friendly

    Lookup fields, prior to expanding the object, will only accept the Salesforce GUID, currently. If we want to map to another field, we need to expand the object. Having the lookup field accept any external ID of that object would aid in preventing too many objects mapped and also help to prevent unnecessary related records match work.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Delete Field Value Using Dedicated Syntax

    We often have the need to delete/clear a field when importing. It would be great to have a dedicated syntax that we can map to indicate that the mapped field should be replaced with null.

    E.g. if we map {DELETE} it would remove the value in the field in Salesforce that we are updating, leaving it blank.

    This would allow blank fields to be ignored, whilst giving users a way to very intentionally delete a fields.

    Two examples:

    1) We have a file of donor data where invalid/incorrect email addresses and phone numbers have been flagged. We can therefore import…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add a filter option for Classy campaigns.

    Our organization has ALOT of published and unpublished campaigns in Classy. It would be wonderful to have the ability to search and select Classy campaigns by a filter vs. having to select from a very long list of "Campaign Names". It would also be great to have the option to search based on "Internal Campaign Name" since that is the field that is non-donor facing that we customize for our internal data mapping. For example, be able to filter Classy campaigns by their
    campaign name or internal campaign name containing "renew", which for us, would allow us to create a…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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)
    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)
  6. Ability to Schedule Formula to do Refund Pulls in Classy to Update Opportunities in Salesforce.

    We need the ability to pull Refunds from the Transactions Connector on a Scheduled basis. Currently, this would have to be a manual run because when a formula is scheduled it only pulls based on the created date not the Refunded date.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Import from One system of Record into the Same System of Record

    We would like to create a formula that will take a Salesforce (SF) report and update the data in SF automatically. The formula set up page does not have the option "Salesforce Production to Salesforce Production". The only options are "Salesforce Production to Flat file" and "Salesforce production to Salesforce Sandbox"

    Reference case 00094322

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Automatically delete $0 "donations" when importing

    Third party workplace/matching gift platforms (i.e. Benevity) will often provide import documentation that contains either an individual contributions OR a company matching gift - leaving the other field to contain a $0 "donation."

    When uploading those files through Omatic Cloud - the $0 "donation" is pulled into the "Needs Attention" queue and require the user to manually delete.

    Omatic should create a functionality that would allow users to set conditions in their formulas to automatically delete these $0 "donations."

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  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)
  9. Phone format for UK

    In ImportOmatic with the dictionaries we had ability to check if the phone number was less then 11 characters and add a '0' at the beginning of the string

    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  ·  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)
  10. Add a DonorDrive bi-directional workflow from SOR>DD

    The Native DonorDrive connector with Salesforce is bi-directional, allowing the syncing of constituent/contact updates from NPSP/NPC to DonorDrive

    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  ·  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)
  11. 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  ·  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)
  12. 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  ·  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)
  13. 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  ·  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)
  14. Child object matching on address in Salesforce

    Currently, address is not a child object in Salesforce, so when address fields are mapped, address data can be overwritten or duplicate contacts can be added when addresses are different (depending on matching criteria). Child object matching on address would help address this issue.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. ZIP code matching in Salesforce

    Currently, 5-digit ZIP codes and 9-digit ZIP codes (where the first 5 digits are the same) will not match when attempting to match incoming records using address as matching criteria. This allows duplicate contacts to be added to Salesforce since Omatic does not match on the address when ZIP is one of the address field criteria.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Able to map Credit Card Brand from Stripe

    requested the Brand name for credit card to be added to the connector.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add Payout ID and Date to the API

    Payout ID and Payout Date added to the API for reconciling between P2GL and OC integration. It's a critical information requirement.

    0 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 →
    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