Enable Short vs Long Formatting for Address Lines
Currently, the replace function will impact the entire string. Example: When formatting an address, 111 West 3rd Street, I want to replace West with W & Street with St. In this scenario, the current functionality will give me an output of “W”. I would like to request the functionality to replace individual elements of a string. Example: When formatting an address, 111 West 3rd Street, I’d like to replace both West with W and Street with St, giving me an output of 111 W 3rd St. Without this additional functionality it is impossible to keep aligned with our database standards using OC.
Ryan Powell
shared this idea
With the recent update to add the custom code script transformation, users are now able to write a custom code script to transform an incoming address to achieve their desired results for long vs short address lines. In our KB that has details about the custom code script transformation, we have examples, including these address long to short and address short to long scripts that you can copy and paste into the custom code transformation to get your address data in the format you desire. This behavior mimics the dictionaries that were made available for address updates in ImportOmatic. The KB article with the details and examples for the custom code script transformation can be found at: https://support.omaticsoftware.com/s/article/Custom-Code-Script-Transformations.
In addition, look out for an upcoming release later this year where we bring address verification and standardization into the Omatic Cloud where a user can configure a Smarty account to perform a lookup into Smarty to not only standardize an address but get back address verification information.
-
Thank you for your interest and feedback in product enhancements! We're excited to share that we're working towards additional address standardization formats and verification features, planned for H1 2026. While timelines may adjust, we aim to deliver these enhancements soon. Stay tuned for updates!
-
Jessica Daggett
commented
Do you think you could give us a timeline update? This issue was first flagged almost 3 years ago.
-
Jessica Daggett
commented
Any updates to this feature since May/June?
-
Jessica Daggett
commented
Fantastic, this will allow me to use Omatic Cloud for flat file imports once this is released! I don't know if it's possible to also have it add "Unit" or "#" or something in front of a lone number or letter at the end? For example people will type in "1451 24th Street 528" and would be great to end up with "1451 24th St #528". Not sure if that's possible. It would also be amazing for the transformation to work well with concatenate for a second line. For example, if people enter "4300 Cherry Creek Drive South" on one field and "Apartment B" on a second field, for the transformation/concat to allow us to import "4300 Cherry Creek Dr S Apt B" all into Address Line 1. Thank you for your consideration!
-
John Rivett
commented
We have many addresses that come in with directions, e.g., NW, NE, SE, etc.; after the case transformation they come in as Nw, Ne, Se, etc.Then there are case were PO and US that need to be all caps but come out as Po or Us.As it is, we will have to cleanup the file since this cannot be done within Omatic, but it would be a great feature to have.
-
Amy Wong
commented
Address clean up transformations like St. to Street, etc
