This article includes step-by-step instructions to create multi-page forms using Update Forms. This technique is useful for separating very long forms into manageable steps. The example in this article is a renter’s information form that will be saved to a real estate company’s database.
Planning and Setup
You first create a table that captures renters’ information. This is the Design view of the base table we’re going to use to create our multi-page form. This table has 24 fields.
In order to create a multi-page form, your table must include at least one unique field. Most often this is a record ID field with an Autonumber data type. In this example the unique ID field is called Application_ID.
- Contact information
- Current residence and pets
- Co-applicant information
Steps to create multi-page forms:
Create the first Web Form
- On the DataPages’ listing screen, click New DataPage to open DataPage wizard.
- By default, the cursor selects Submission Form as first DataPage type.
- In Select Fields screen of the DataPage wizard, move the contact information fields from Available Fields panel to Selected Fields panel. Select On exit, pass ID and formula fields as parameters check box so that Autonumber will be passed to the next DataPage.
- Configure your fields as normal. If you are using a random unique ID field (that is not an Autonumber), follow the steps here to pass the value to the next form.
- On Destination and Emails page, click Go to a new page for destination after record submit. Type the URL for the web page that is hosting the following DataPage of your multi-page form. Click Finish.
Create the Update FormsNext, create the remaining update forms.
- Navigate to the DataPages’ listing screen and click New DataPage.
- For DataPage type, select Single Record Update.
- On DataPage DataSource screen, select the same data source. If you receive an error message, it is likely because the table you are using as a data source does not contain a unique field. Go back to the beginning of this article and verify your table design. Then double check to make sure the unique ID is being properly handled in the first form. In this example an AutoNumber field is used as the unique field.
- Next, to configure this form to receive the unique ID from the Web Form, on Record Identification screen, select Find record through unique ID. Choose your unique ID field from the drop-down field. In this example the only unique field is the Application_ID with an Autonumber data type. The parameter name needs to be changed slightly. Add “InsertRecord” after the @ symbol and before the field name. This change in syntax tells the update form that the parameter being received is an Autonumber from a newly created record.
Note: The InsertRecord prefix applies for other ID field types (Random ID, Prefixed Autonumber and GUID).
- Next, select the fields to include in the second section of the multi-page form. In this example, the second section prompts the end-user to provide information about the applicant’s current residence and pets. Move these fields from the Available Fields panel to the Selected Fields panel using the arrow button.
- By default, all Update Form fields are set to Display Only. To allow end-user to input data, change the form elements to an input format such as Text Field.
- On Destination and Emails screen of the DataPage wizard, click Go to a new page for destination after record submit. Enter the URL of the web page where the next DataPage will be hosted. Click Finish.
- Receive the Autonumber
- Select and configure the fields
- Redirect the end-user to the next page after submission
- Add the control field to the last form. Remember to add the Application_Complete control field to the last Update Form. On the Configure Fields screen of the DataPage wizard, select this element and select Hidden from the Form element dropdown. Then, set the default value to “Yes” by selecting the default value checkbox. Now when this final form is submitted the field value will automatically be switched to “Yes”.
Configure the final destination
- The very last page of the multi-page form does not go to another URL. In this example, the standard confirmation message has been customized to include a link back to the homepage. You could also direct the end-user directly to a confirmation webpage on the Destination and Emails screen.
You can now deploy each of the DataPages to their respective web pages.
After the forms have been deployed the end-user will go through the sections in the following order to complete the multi-page form.
Testing and Formatting
Now that the pages are deployed we can go through and test to make sure that the multi-page form is working correctly. Having difficulties connecting the forms? Ask yourself these questions:
- Is the Autonumber parameter spelled correctly?
- Are you using the correct Autonumber parameter format with the InsertRecord prefix? [@InsertRecordxxxx]
- Is the field being passed marked as unique in the table’s Design view?
Once you’re satisfied with the functionality of your multi-page form, you can modify the look and feel so that all of the pages match perfectly with your host website. As you see in this example we used headers to add the company logo and to add section information (in blue) to provide a prompt to the end-user at each step.