# Allowing Element within an Autocomplete Address Field to be Made Required

**URL:** <https://community.noloco.io/t/allowing-element-within-an-autocomplete-address-field-to-be-made-required/997>\
**Category:** Feature Requests\
**Created:** [July 17, 2024, 4:55pm UTC](https://community.noloco.io/t/allowing-element-within-an-autocomplete-address-field-to-be-made-required/997 "2024-07-17T16:55:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dominic](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/dominic/32/608_2.png) [@Dominic](https://community.noloco.io/u/Dominic)\
**Post date:** [July 17, 2024, 4:55pm UTC](https://community.noloco.io/t/allowing-element-within-an-autocomplete-address-field-to-be-made-required/997/1 "2024-07-17T16:55:12Z")

</div>

Having just launched a form that included an Autocomplete address field that is validated by Google Maps, we now have about 5% of respondents (nearly 100 records in the first day) that have only partially completed addresses.

This field type would be far more useful (currently, it is not even really usable if you need complete addresses every time) if the individual address components (Street, Postal Code etc), with the exception of line 2 (Suite / Apt / Flat) were all required.

This image shows just a few of the submitted addresses that we now have to try to find a way to resolve.

 ![Screenshot 2024-07-17 at 18.53.31](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/dd50ee536bfe9deded55b3a4cb52e6120e2292b5.png)

---

<div class="post-metadata">

**Author:** ![Dominic](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/dominic/32/608_2.png) [@Dominic](https://community.noloco.io/u/Dominic)\
**Post date:** [April 28, 2025, 10:42am UTC](https://community.noloco.io/t/allowing-element-within-an-autocomplete-address-field-to-be-made-required/997/2 "2025-04-28T10:42:44Z")

</div>

Any chance this issue will be addressed (excuse the pun)?