Currently, the address capturing in POS is straight-forward, but also not very flexible. Hence it would be great, if this form could also meet additional needs like:

1. Define whether or not a field should be displayed as a drop-down or not

Bug Counties is a free text field but ignores the address setup parameter validations and validates regardless. Therefore as a free text field this is impossible for uses to correctly guess the county ID.

e.g. cannot be displayed as a drop-down field, although it throws an error when a county is entered that does not exist in HQ. Hence it would be good to have the opportunity to eliminate this issue through parametrization.

2. filter address fields based on the address setup, and not rely on zip- code population

-> If you enter a zip-code, city and county can be pre-populated with the data from HQ, but if you can select the either state or county , we should be able to filter the other fields and visa-versa

3. Use the address format defined for the country in HQ to display the fields in POS

-> This way, cashiers can enter an address using the field sorting they are used to

Issue search bugs

Details for issue 606477 (dynamics.com)

Details for issue 822249 (dynamics.com)