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 ignore
In this case (RE NXT), the exception that was generated was not as clear as it could have been: 'the gift_splits field is required'. There wasn't any split gift data, so the exception was misleading.
Stu Manewith
shared this idea
With 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 here: http://omatic-cloud.helpdocsonline.com/transformations
-
Cody Murray
commented
When adding custom fields, notes, or solicit codes we would like the option to only add the current date if the field isn't blank.
-
Kendal Ferguson
commented
This logic would be amazing for several use cases even beyond gifts, including use in Salesforce
-
Michael Kracke
commented
Sometimes data from a system could exist in 2 different places. For example Encompass requires a purchase date for memberships. However depending on the membership, this could be the renewal date or the purchase date. This is because a user can pay all upfront, or yearly.
So it would be nice to have the options to say "If field A equals X then use field B", where X could be blank or a specific value. Of course the fields would have to match syntactically for this to work. So Dates could only compare with dates, strings with strings etc.