New problems entering address?
This is in the NEW FORMS: When entering an address using the Full Address search it keeps putting the number AFTER the street: After choosing the top address in the list, it puts this into...
Forum Discussion
Jeff,
I actually think a dropdown for US states is an improvement. It prevents errors by all those users who don't know whether MI is Missouri, Mississippi, Minnesota, or Michigan. But I agree that the dropdown should not be the last work. My suggestion is twofold:
(a) In the dropdown for US State, show both the postal code and the full state name, so that the user can query based on either of those.
(b) Revise the Region/Postal code values for the US to be a combination of the two-letter state postal code plus the zip code. So the value of the field would be, for example, NY 10017.
Alex Wilkinson
The problem is occurring when I have it set to US format and an automation tries to create a new record using the state name instead of the abbreviation:
"You must provide a valid choice for the field named "Full Address: State/Region" with field id 22." - It will not accept 'OR' and is expecting 'Oregon'
Edit: I realize I can add another step to format the state name, but it's ridiculous that I should have to do that at all. I would be using the international format since we use addresses in Canada and Mexico, but because of the problem in the first post of this thread, I cannot.
------------------------------
Jeff Peterson
------------------------------
- One solution would go like this:1) In your app, create a new table with two fields, the two letter code is one, the state name is the other. Both are required & unique. Call this table "State Lookup" or something similar.2) In your pipeline, insert a new Query step which finds the record in the new table that has the two letter code, and returns that plus the state name.3) In the existing step of your pipeline that creates a new address, use the state name that the new step found.Alex