# Progressive form issues - fields disappear

**URL:** <https://community.hubspot.com/t/progressive-form-issues-fields-disappear/93406>\
**Category:** CMS Development\
**Tags:** forms\
**Created:** [November 6, 2023, 10:01pm UTC](https://community.hubspot.com/t/progressive-form-issues-fields-disappear/93406 "2023-11-06T22:01:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![EmilyVaulted](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/emilyvaulted/32/44222_2.png) [@EmilyVaulted](https://community.hubspot.com/u/EmilyVaulted)\
**Post date:** [November 6, 2023, 10:01pm UTC](https://community.hubspot.com/t/progressive-form-issues-fields-disappear/93406/1 "2023-11-06T22:01:28Z")

</div>

I am working on a client’s site and would like to create a progressive form that shows a couple fields and then a submit button. I’ve added the following fields to test, I’ve included the labels with the input type and property description.

**First Name** \* _text/contact property_

**Company Emai** l\* _email/contact property_

When I preview the page, the form doesn’t show up, I’m presuming because my contact properties exist and are filled out in the form, skipping straight to the submit button? When I open an incognito browser, I can test but I’d rather not create a bunch of fake emails in my clients system to test each time.

There will be workflows attached to the final form. Is there any way to get around this and test so I can show the client a proof of concept that shows the form is working and contacts are enrolled in a workflow?

---

<div class="post-metadata">

**Author:** ![SteveHTM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevehtm/32/22074_2.png) [@SteveHTM](https://community.hubspot.com/u/SteveHTM)\
**Post date:** [November 6, 2023, 10:22pm UTC](https://community.hubspot.com/t/progressive-form-issues-fields-disappear/93406/2 "2023-11-06T22:22:36Z")

</div>

A quick answer on this is to do your early testing with the form option “don’t autofill” switched on.

Hope that helps!

---

<div class="post-metadata">

**Author:** ![EmilyVaulted](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/emilyvaulted/32/44222_2.png) [@EmilyVaulted](https://community.hubspot.com/u/EmilyVaulted)\
**Post date:** [November 8, 2023, 6:01pm UTC](https://community.hubspot.com/t/progressive-form-issues-fields-disappear/93406/3 "2023-11-08T18:01:22Z")

</div>

Thank you! Works and I totally missed that in setup since it’s on the Options page.

---

<div class="post-metadata">

**Author:** ![Raffy](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/raffy/32/31408_2.png) [@Raffy](https://community.hubspot.com/u/Raffy)\
**Post date:** [November 7, 2023, 5:56am UTC](https://community.hubspot.com/t/progressive-form-issues-fields-disappear/93406/4 "2023-11-07T05:56:51Z")

</div>

Hi Emily,  
To show the client a proof of concept, have you considered creating app developer account?  
An [**app developer account**](https://developers.hubspot.com/get-started) is a free account for you to test creating and managing apps, integrations, and managing developer test accounts. It is not connected to a standard HubSpot account and cannot sync data or assets with it.  
A **developer test account** is a free HubSpot account with access to a 90-day trial of many enterprise features. It is created within an app developer account and is used to test apps and integrations without affecting real HubSpot data. It has some limitations on marketing, CMS, and email features. It can be identified by a banner that shows the expiration date.  
Some content lifted from [HubSpot Account Types](https://developers.hubspot.com/docs/api/account-types)