Skip to content

How can we improve Omatic Cloud?

← Omatic Cloud

Enhanced Mappable fields to Transformations

This was a previous uservoice story but there are still gaps with usability with the if/then ability in transformations. Specifically with if/then/else, the cascading transformations are challenging to build out for most users outside of onboarding.

The ability to include mapable fields directly to a transformation, outside of concatenated replace logic, would be very helpful and would allow for a more intuitive user experience. This is current functionality in P2GL and it would be helpful to have in Omatic Cloud as well.

3 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Christina Hoffecker shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • AdminKendal Ferguson (Admin, Omatic) commented  ·   ·  Report

    Another example, keep in mind that Gift Date and Deposit Date come from the same source field and are treated differently based on source field containing _A_, _B_, or _C_, Chapter ID and Payment Method are also present for all source data:

    IF source field contains _A_, _B_, or _C_ - then destination field needs: [Defined Value]-[Gift Date]-[Payment Method]
    IF source field does not contain _A_, _B_, or _C_ - then destination field needs: [Deposit Date]-[Chapter ID]-[Defined Value]

  • Christina Hoffecker commented  ·   ·  Report

    Example between 3 fields:

    IF Field A > 0, Payment amount = Field B
    IF Field A = 0, Payment amount = Field C

Omatic Cloud

Categories