Omatic Cloud
25 results found
-
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.
-
NXT to NXT
Imagine if you could continuously transform NXT data without running a global update (or other manual methods, like a flat file).
Example: OC formula that begins with NXT Action List. When an action fitting the criteria is added, transform it into a Consent Table entry and write it back to the NXT constituent record. Run it continuously.
Current capabilities of RE business rules or NXT Workflow don't extend this far or offer this much flexibility. Even if NXT Workflow eventually grows into this space, I doubt it'll offer the full fields OC does.1 voteHi Kelly! This is possible today! You just need to set up two RENXT data sources (to the same RENXT instance). Then, you can pick one as your source and one as your destination in your formula!
Best,
Kristen
-
Show "Incoming Date/Time" of Record During Matching
We currently have a problem if the record comes in multiple times, we don't know which record is the latest one. You almost have to export the data and review it column to column for an individual.
It would be nice to include the date/time when the record was added to the matching screen. Right now we can see date/time for exceptions, so it would be nice to see that on the matching.3 votes -
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.
-
Shorten Data Transformation - add ability to shorten from front or back
Current transformation only allows us to drop values from the end of a string. We also need the ability to drop values from the front of the screen.
39 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 -
Sync Entire RENXT List to Data Source
Right now when using a connector to sync records from RENXT to a data source Omatic considers the "Modified Date" in addition to the RENXT List that the record is on. For lists that are created more ad hoc, such as events, the records may not have necessarily been modified recently, so they're either missed in the sync or you would need to force a modification on all records in the date via a Global Change. It would be awesome to the have the option to sync the entire list for certain formulas, so that all records on the list…
9 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).
-
Field Campaign Internal Name Visibility
Ability to view the Internal Campaign name in hosting when attempting to map Classy Recurring gifts,
6 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…
-
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 -
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 -
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!
-
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
-
Add Ability to import Tributes to RENXT
We would like to import Tribute Data through OC, into RENXT.
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 -
Need more flexibility for filtering records in RE NXT List, in order to export
RE Query allows for greater flexibility in the output of fields from RE than the List option does. For a client with an email connector, who may be using cons codes, solicit codes, attributes, etc. to segment their audiences this is not possible with the List endpoint in RE NXT.
3 votes -
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
- Don't see your idea?