Omatic Cloud
79 results found
-
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 votesAdditional toast notification feedback can be submitted within the referenced link
-
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 -
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 -
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 -
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 voteThe 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).
-
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- 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
-
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 -
1 vote
This work as been completed and the ability to export the entire "bucket" is now available in production!
-
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 -
ability to use 'if / then / else' logic for mapping fields
My file has some rows with gift data and some rows without gift data. In order to import the gift data, we have to map required fields (ex: gift type). But the rows without gifts are creating exceptions because it is still trying to send in the required field but there are no gifts associated with that row.
Need to the ability to map fields conditionally:
if gift data exists, then add them (with the mapped values), else ignoreIn this case (RE NXT), the exception that was generated was not as clear as it could have been: 'the gift_splits…
14 votesWith 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 gift amount
- Add a "Replace" transformation to transform: "If not Blank" to "True", and "If Blank" to "False" (in that respective order)
- Add a "Concatenation" transformation and add Gift Type
- Add a "Replace" transformation to transform "If contains False" to "Blank"
- Add a remove custom text for "True"
This will ensure that the Gift Type field coming in is only populated if the Gift Amount is populated.
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…
-
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 votesreleased July 2, 2024
-
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 votesThis idea has been implemented via a new feature on the Date/Time Transformation. You can now use a Transformation to add/subtract periods of time from your Date/Times!
To find out more, visit our User Guide: https://omatic-cloud.helpdocsonline.com/transformations$how-to-transform-nbsp-date-and-time-format
-
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 voteHi 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.
-
Ability to filter Salesforce Donations for Posting based on a Salesforce Report (Query)
Currently, the only filters available for gathering Salesforce donation transactions for P2GL posting include Stage, Campaign, and first-class Date fields on the Opportunity object. Very often, clients have data in other objects in Salesforce that drive the post process. (Payment object and custom object data elements are often needed for filtering.)
Ideally it would be nice to be able to export transactions based on a Salesforce report (query). This would only work if there were less than 2000 records due to the limit that Salesforce imposes, but clients could control the records appearing in the report themselves by posting more…
7 votes -
pull pledge payments on pledges with multiple payments
make payments the center of the decision of data to post instead of opportunities
2 votesThis can now be accomplished through the use of the new Salesforce Report as a source functionality.
-
Timestamp update after UTC Conversion
Timestamp to appear with LO time after ignoring UTC conversion clean up.
0 votes -
Parse part of the incoming data
Would like to see the ability to Parse only a part of the incoming data. (ie. In plugin we can use the RegEX Parse First Name dictionary found on the Commonly Used Regular Expressions page to return only the first word in a series of words.) Would like to be able to do that in OC as well, so when the data file contains Mickey & Minnie it imports only Mickey.
8 votesThank you for this idea! There will be a new transformation type being released tomorrow in Omatic Cloud called "Split". With this new transformation type, you can set criteria that parse out values from within a string of data. For example, if you have a string of gift amounts separated by semi colons, you’ll be able to divide those values and return specific items. In order to parse out the first word of a string, you would split the string using space as the separator, and return the first position of text.
Be on the lookout for this new transformation in Omatic Cloud tomorrow!
Best,
Kristen Gajdica
-
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 -
Concatenate mapped field + defined field
Can we add the ability to concatenate mapped fields with defined fields?
3 votesIn the 11/10/22 release, we will be including a new update to the concatenation tool. You will now be able to concatenate a mapped value with a defined value or a current date.
-
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 votesThe ability to perform inline editing within the Destination Exceptions bucket is now available in Omatic Cloud!
- Don't see your idea?