The Dictionary function is imperative. One of the dictionaries we use in IOM classic transforms EA source codes to fund codes. There are hundreds of entries in that dictionary and it is constantly being updated as new source codes are being added/created. This dictionary is used in several IOM classic profiles. We tried to move one of the profiles to Omatic Cloud. I have to put the use of this profile in the Cloud on hold until we have access to dictionaries because right now I already have to clean up 44 records that imported the source codes without transforming them to fund codes. The point of using Omatic is not to have to clean up records afterwards.

having to rebuild the same transformations over and over and over and over again is not only frustrating, but introduces a huge risk. If I forget to update one transformation, my formula is now wrong. Whereas with a saved transformation, I only have to update on transformation, and all the formulas using it are updated.

The reason this is so critical for us is the address and RegEx transformation dictionary that we have in IOM. It has hundreds of entries to help format addresses properly (abbreviations, no punctuation, etc). I now have to try to build those in the Cloud and not only that, I have to build them over and over for all our Formulas!! So maybe converting existing dictionaries isn't possible, but finding a way to create this one in the Cloud is what we need. It would be ideal if you had a built-in transformation to do this to addresses as I'm pretty sure most clients want to adhere to USPS standards.

More generally, the Dictionary function does not exist at all in OC. That has to be added as a component as it is built into everything we do in the databse.