Omatic Cloud
82 results found
-
Support "starts with" or "ends with" in Transformations
When translating data we need more supported options for translating data, for example, "starts with" or "ends with" at minimum.
7 votes -
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 votesThere 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.
-
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 -
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
-
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
-
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).
-
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 -
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 reason code to BBCRM Constituent Email
BBCRM Constituent Email Address section has an option to set the "Do Not Email" flag. However, our Bio records team would like us to include a reason code inorder to identify who (in this case from where) set the flag.
Would it possible to add reason code as an option?
We are currently integrating with Emma.
1 voteHi Michael - We released this last sprint. You should now see the Reason Code on the email object and be able to map this field.
-
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.
-
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 votesThis field is available when the BBCRM Constituent Revenue is the destination endpoint for BBCRM integrations.
-
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.
-
add import ID routing
need to be able to return fields in data differences,
0 votes -
Create new data selection
to be able to choose which date to use for filtering
0 votes -
Timestamp update after UTC Conversion
Timestamp to appear with LO time after ignoring UTC conversion clean up.
0 votes -
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
-
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
- Don't see your idea?