Product: Omatic Cloud


Environment: All

Versions: All

Video instructions:


Have you ever wanted to send data to different fields than your formulas allow?  For example, maybe you have a question on your donation forms about volunteer interests, but you can't map to your volunteer-related objects and fields in the preconfigured gift formulas.  Now you can!

Omatic Cloud now has the ability to send to "Any Object" in some integrations, like sending Flat Files to Salesforce.  We plan to continue expanding this functionality to other integrations, so make sure to follow the Omatic Cloud Updates forum to keep up with the latest changes.  As more integrations offer this feature, we will update this solution to include important information about each.

Using the Object Picker with Salesforce:

Tip: Given the flexibility of this formula type, including the ability to use custom objects, we strongly recommend testing with a small data file, and using your Salesforce sandbox first.  This will ensure that you can thoroughly review the records that are created, updated, and related to each other before impacting your production org.
  1. Start by creating a File Upload formula with your sandbox org from the Integrations/Formulas page.

  2. Select the Import Contacts and Any Object formula type or the Import Accounts and Any Object* formula type.
    *The remaining instructions will focus on Contact formulas for simplicity, but the information is applicable to Account formulas too. In the Troubleshooting section below, we have mentioned a couple Account-specific considerations.

  3. On the Data Mapping screen, you will see the Contact object and some of its fields displayed by default.  

  4. Click Add/remove objects to open the Object Picker:

  5. The Object Picker will display all objects that relate to your Contacts (since we use the Contact for matching, we always start there):

  6. When you expand an object node, all of the fields in that object will display for selection.  If you select the entire object, all fields will be selected too.  You can deselect the object to pick and choose which fields you want to add to the Field Map.  If you select an object that has its own child objects, those will be automatically added to the list for you to explore and add.  The rest of your objects are still there too, just scroll down or use the search field at the top!

  7. Once you've picked the objects and fields you want to include, save your selections to return to the Data Mapping screen.  If you forgot something, you can return later to add it.

  8. As you are mapping your objects and fields, pay attention to which objects include their own matching rules, like Opportunities. By default, these are set to "add new," but you can adjust the settings to match existing objects based on any combination of the available fields.

  9. When you finish your formula, go ahead and use a small data file to test the configuration.  Make sure to thoroughly explore how records were matched and updated, including relationships between objects.  If anything looks out of place, check to see if adjusting your formula can resolve it.  If you are unable to resolve the issue, let us know!  We're looking for feedback from users on where we can improve this new, flexible formula type.

Promoting a formula from sandbox to production is not currently supported on this formula type.  You will need to manually recreate the formula within your production integration, following the steps above.  


  • How does Omatic Cloud know what objects are in my Salesforce org, and how does it know how to relate them to each other?  

When you create a formula, Omatic Cloud was already reaching out to Salesforce to make sure we had access to all of the fields you may need to use.  Similarly, Omatic Cloud can go a step higher to see what objects you may need to use and how they relate to each other.  This data about how you store data is called "metadata."  We store metadata in the background, in your Object Relationship database.  By storing this info, you can quickly make edits to formulas without waiting on metadata to load.


  • When I click on Add/remove objects, nothing happens.  I'm unable to open the Object Picker.

If the Object Picker doesn't open, create a case with Omatic Support.  We will refresh your Object Relationship database in the background, which will resolve this issue quickly.  In the near future, you will be able to update your Object Relationship database without contacting Support.

  • Some of the objects in my Import Accounts and Any Object formula look very similar; which should I use?

Opportunities versus NPSP Opportunity: We recommend using Opportunities, because NPSP Opportunity will add the objects to Salesforce, but they will not be linked properly.

Contacts versus Primary Contact: Of these two, we advise using Contacts, because Primary Contact will trigger a request error.  However, you should review whether the child object matching options in the Data Mapping screen are robust enough for you to confidently update/create Contacts in Salesforce.  Contacts created in this manner will not be processed through the full Contact or Account Matching rules you set on the next screen in the formula wizard..

  • I added new objects or fields, but they are not showing in the Object Picker yet.

If the Object Picker doesn't display your new objects/fields, you may need to refresh the list.  Open the Object Picker and click on the link to refresh.  This process will take about five minutes, and you do not need to keep the window open while it works.  When you reopen the window, you should see the new objects, as long as they are accessible by the Salesforce User you used to create the connection with Omatic Cloud.  If you do not see the object or fields after 15 minutes, create a case with Omatic Support.  
Note: Each time you click the link, it queues up another refresh process and adds 5 more minutes.  To avoid unnecessary delays, do not click the link more than once.

  • Some of my Salesforce objects and fields are missing from the Object Picker, but they are not new.

Currently, the Object Picker will only display objects that relate to either Contacts or Accounts, since we use those top-level Objects for matching.  For example, we do not display the General Accounting Unit object (meaning you cannot add a new GAU via this type of formula), but we do display the GAU Allocation object since it rolls up to the Contact via Opportunities.

Additionally, we only display objects with editable fields to prevent confusion.  In the future, we will be expanding this feature to include more flexibility.  We're welcoming feedback for improvements, so make sure to add your thoughts to the Omatic Cloud Ideas forum!