Omatic Cloud
79 results found
-
Please add "Creditcard holder name" field to Luminate Online Connector Profiles
This very important field is missing and we need it - thanks!
15 votesAre you referring to the Donations profile type or other ones? According to the field documentation we've compiled from Luminate's API resources, the following fields are pulled from the credit card itself:
Payment - BillingName - FirstName
Payment - BillingName - MiddleName
Payment - BillingName - LastName
Payment - BillingName - Suffix
All of these fields are provided across all of our profile types containing credit card transaction info. Does this resolve the issue? If not, can you provide more detail?
Thanks! -The Omatic Team
-
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…
-
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
-
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
-
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 -
Post Salesforce Payments in Post-to-GL
My current understanding is that the P2GL API for Salesforce does not allow posting of payment records that are not themselves SF Opportunities, eg, pledge payments (ie, the pledge is the Opportunity, and payments are payments against the pledge but not Opps themselves. We need to be able to post payments that are not Opportunities.
When considering pledge fundraising and the ability to properly account for pledge payments against pledge commitments, the payment, and not the opportunity is the fundamental basis for pulling Salesforce data.
7 votesThis can now be accomplished through the use of the new Salesforce Report as a source functionality.
-
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 -
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 -
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 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 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
-
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!
-
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 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 -
Allow for defaulting Recurring Gift Fields on a Gift when Bringing in Recurring Gift Payment
When bringing in a Recurring Gift Payment to RENXT I would like the ability to default the fields on the Orginal Recurring Gift. This includes bypassing the error message that Fund ID is required. If the Fund is not populated I would like to populate the Fund with the original recurring gift.
4 votes -
SF Leads Matching on Contacts and If the Contact does not exist create a Lead
When attempting to add Leads to Salesforce using the Any Objects Formula, we would like the ability to look for Contacts first to see if a match exists. if no contact is found we would like to add them as a lead.
Use Case: When bringing in a file of Leads they may or may not exist in SF. If they exist as a contact in SF we would not want that lead to be created. If no contact is found we would like to have them as a lead rather than a contact.
4 votes -
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 votesWe 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.
-
Make BBCRM Data Forms Available with SFTP Connector
Currently the SFTP connector only allows for 1 constituent import option. While this option does have a variety of fields, there a few non-constituent based imports we would like to use the SFTP connector for.
The regular flat file option allows for connecting to any single data form in BBCRM. This is a helpful tool for infrequent imports. However, being able to use this same logic while having the convivence of the SFTP scheduled auto imports would save us a lot of time and allow us to connect Omatic to many more 3rd parties that do not have dedicated connectors…
3 votesHi Michael - We have updated our SFTP to BBCRM formula types to include a new one for you: SFTP to BBCRM Data Form. You should be able to then setup a SFTP folder location and have it go to a BBCRM Data Form.
Let us know if you notice any problems by submitting a support ticket and we can review.
-
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 votesIn 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
-
Activity History UI Suggestions
With the new 'activity history' feature, it would be extremely useful to be able to export the activity history to a file (.csv ideally). This would be especially nice because it would give users a way to 'backup' older activity history before it becomes unretrievable per the 60 day limitation. Lastly, it would also be awesome to see a specific column in activity history for the 'Formula Name', which would grant the added bonus ability to sort on it and mean that users won't have to try to find the formula name from within the text in the description column.…
3 votes -
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
-
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.
- Don't see your idea?