Our org likes to keep track of where people came from i.e. Source code and subsource code. Some of our formulas have to be manually run by people since the type is file upload. The work around I found for adding fields only for new people is to have two formulas but some of our files are big enough it takes us double the processing time to run two formulas. While two formulas work in the short term it also means if I have to fix or add something I have to fix it in both which then tends to get lost. Adding in a "for only new" field would change my processes and save time in the long run.

It is unacceptable that Omatic cloud is unable to differentiate between a new and existing records in RE, resulting in a default constituency code being added to ALL records, not just new ones.

We were so excited to switch from importomatic to omatic cloud, but the fact that it adds a constituent record to ALL records, instead of just new records, is such a critical issue for us that it makes the product unusable. It's a huge disappointment to be lacking in such basic functionality that we've been used to with importomatic, and will have to continue using that for the foreseeable future until this gets fixed.

This one is very important for my org because we have a lot of VIPs who may have very specific ways of wanting to be addressed, or we want their name in our database in a very particular way. I was frustrated to realize today while creating a new formula that there is no way to selectively add this information, and therefore it will write over the data we already have. This could cause some major problems for us down the line when sending acknowledgment letters or other mailings.

I would love for OIC to only add the default Individual constituency code to new records, not add it to existing records. Our corporate, organization, and foundation records keep having an Individual constituency code added to them.