Omatic Cloud
20 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…
-
Allow same source and destination
OmaticCloud would be more valuable to us if it would allow same data source and destination. For example, data stored in RE membership could be transformed or simply moved to constituent attributes area by an OmaticCloud job when membership data is changed. This will help workaround missing functionality from RE and Omatic to improve our data efficiency and accuracy. Thank you!
8 votesThis is now supported! You will need to connect RENXT as a Data Source twice (once for the "Source" and once for the "Destination"). Once the two data sources are created, you will have the option to select one as source and one as a destination in the wizard. Then, you will have formula types available for those connections.
-
Field Campaign Internal Name Visibility
Ability to view the Internal Campaign name in hosting when attempting to map Classy Recurring gifts,
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 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 -
Add Ability to import Tributes to RENXT
We would like to import Tribute Data through OC, into RENXT.
4 votes -
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 -
RENXT Gift List Formula Type
We would like to have the formula type RENXT Gift List > HubSpot. This would allow for relevant gift information to be transferred back in to HubSpot to determine the ROI on email campaigns.
4 votesSending gift data from RENXT is now available using RENXT Query as a Source!
-
Offering the ability to pull all list types from NXT, not just a Constituent list. (Gifts, Actions, Opportunities)
I need the ability to sync constituents between NXT and Luminate who have given to a particular Package. This is only searchable in NXT through a Gift List.
3 votesThis is now supported, with RENXT Query as a Source. You can create a query in RENXT, and use it as the source of the data to send to Luminate.
-
Add Translations for RENXT Gift Types
Translations for all Gift Types in RENXT would be nice. For example, in the front end the type is "Gift-in-Kind", but the API is expecting "Giftinkind"
1 vote -
Ability to pick a date format for the concatenated date
This is in relation to batch number naming. When we had this feature in V1 it was great for a variety of reasons and it helped when we had to process backlogged donations using run once. Now I'm having to do tons of workarounds.
1 vote -
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 -
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).
-
Add another Relationship (RE NXT)
There are many times when we need to import more than one Relationship at a time. For example, we have flat files that contain both Spouse and Employer information that needs to be mapped separately. I was surprised when I went to map this in a formula and there was no Options dropdown next to Constituent / Relationship. (RE NXT)
0 votesGood news! This request has been addressed on the upgraded Omatic Cloud platform. We are planning to upgrade users to the new platform starting in Q1. Our goal is to ensure a seamless transition for you. You can find more information about all of the new capabilities and FAQs on our resource page: https://help.omaticsoftware.com/omatic-cloud-upgrade
-
Additional Addressee/Salutation imports
It would be great if it were possible to import additional Addressee/Sals. I know this isn't currently possible from RE NXT, but hoping they can make it possible so you can too.
0 votesThis is currently available under the section called "Other Name Format". Blackbaud updated the verbiage for Additional Add/Sals in RENXT to be called "Name Formats". -
Please add ability to export fundraiser information from RE NXT
We need to send the following fields out of RE NXT:
Fundraiser Name
Fundraiser Type
Fundraiser Date FromThanks!
0 votes -
Create new data selection
to be able to choose which date to use for filtering
0 votes -
add import ID routing
need to be able to return fields in data differences,
0 votes -
Ability to send first/latest gift information out of RE NXT
We need the ability to export fund descriptions from our constituent's first and latest gift through the Omatic Cloud connector. Please let us know when this capability is added!
0 votes
- Don't see your idea?