Start a new topic

Transformations (not having a repository like dictionaries)

If having to update a transformation you have to do it on each formula 


2 people like this idea

Hi Amy - Thanks for your idea.  We know that we currently need the functionality that IOM provides with dictionaries.  We will be evaluating how we might approach this in the near future.  We want to be sure to consider other scenarios and limitations in IOM dictionaries such as relying only on 1 field for a transformation with any solution(s) that we come up with for Omatic Cloud.  We would love to hear how you use IOM dictionaries and for what purpose as well as any other insight into transformations that you might need beyond what IOM dictionaries are capable of.  


Steve Brewer

Product Manager



Hi Steve, 

One thing we also struggle with currently with IOM dictionaries, and hope could be implemented some time in the future is for them to allow conditionals. 

As right now it's very straight forward with one value coming in and being able to replace it with another. 
Not sure if that is being worked out with in transformations, but would also help with our import profiles a lot! 

One additional field that would be helpful adding into the transformation drop down fields to have "Not one of" option. 


1 person likes this

Hey Amy - Per your comment above about conditionals, can you elaborate a bit more?  Are you referring to conditionals in regards to one or more fields, meaning if one field has a specific value then apply some logic based on this other field?  Or is the conditional all within that one field's value?  An example would be helpful to have.  Having this level of detail would allow us to perform a sanity check against what we have been planning for future work.  


Thanks again for your feedback!

I think the conditional function we’re looking for is a One Of type.

For example at the moment the dictionaries create a conditional formula of “If = A, do X; If  = B, do Y”

What we want is “If = A or B, do X; otherwise, do Y”

 

That way we don’t have to list every possible alternative, just the one or two that have different needs.

 

Also, we could do with the option of the instruction being do nothing. For example = if there is a tribute ID, link to the tribute. If there isn’t a tribute ID, don’t link to the tribute. At the moment the import runs on the instruction – link the tribute ID; if there is no tribute ID – produce and exception file. (Same is true with Participant ID link)


1 person likes this

I think the conditional function we’re looking for is a One Of type.

For example at the moment the dictionaries create a conditional formula of “If = A, do X; If  = B, do Y”

What we want is “If = A or B, do X; otherwise, do Y”

 

That way we don’t have to list every possible alternative, just the one or two that have different needs.

 

Also, we could do with the option of the instruction being do nothing. For example = if there is a tribute ID, link to the tribute. If there isn’t a tribute ID, don’t link to the tribute. At the moment the import runs on the instruction – link the tribute ID; if there is no tribute ID – produce and exception file. (Same is true with Participant ID link)

Agree, being able to share transformations between formulas would be such a time saver! We have the same transformation on multiple formulas, both for Mapped fields and for Concatenated. It would be great if both of those instances could pull from a repository eliminating the need to make the same update multiple times. 

Login or Signup to post a comment