> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/example-gallery/how-to-guides/how-to-guide-repeating-inputs.md). # How-To Guide: Repeating Inputs This How-To Guide contains examples of how to collect repeating sets of information, which can give you a shortcut for modeling repeated questions and make editing/updating these questions much faster. Additionally, by collecting the inputs using these repeating constructions, you make your underlying data much more accessible as well as easy to manage, report on, and use in other questions and areas of the application. Examples of the business scenarios these tools cover include collecting similar data sets across multiple office locations, products, service units, people, and events. The three constructions showcased in the example project are: 1. Vertical Repeater 2. Smartgrid 3. Tab Control Use the Vertical Repeater to gather data that is limited in terms of the number of questions and space used but provides customized and variations for each step. To collect the same information across multiple "cycles", you can use the Smartgrid. If you want to provide extensive and rule-based variations in each cycle use Tab Control. ## Attachments * [ASF How-To Guide - Repeating Inputs 74.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/y7kh0r-ASF-How-To-Guide---Repeating-Inputs-74.zip) * [ASF How-To Guide-Repeating Inputs 8.1.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/80b9qh-ASF-How-To-Guide-Repeating-Inputs-8.1.zip) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/example-gallery/how-to-guides/how-to-guide-repeating-inputs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.