> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/inspection-reports/show-or-hide-asset-questions-from-report-information.md). # Show or hide asset questions from Report Information A Yes/No question in **Report Information** can control whether a question appears for every asset in a later step. For example, **Show MFG Date?** can show **Date Manufactured** for every Fire Extinguisher when answered **Yes**, and hide it when answered **No**. The question can also remember the asset group's setting. Link it to a Yes/No attribute on a configuration asset type that has exactly one asset per group, such as **Report Config → Show MFG Date?**. ## Set up the question Ask the Essential Assistant to update the report form. Name the controlling question, its saved attribute, and the question it should show or hide. For example: > Add a required Yes/No question called Show MFG Date? in Report Information, linked to Report Config → Show MFG Date? for this asset group. Yes should show Date Manufactured for every Fire Extinguisher in the later asset step; No should hide it. Apply the same condition to the PDF. Review the proposed form and PDF changes, then publish the updated report definition. Use the existing Report Config entry as the source. Avoid adding an asset list for that same source in this report, so the same attribute is not edited twice. If you later remove or change the binding to a different source, add an asset list for the former source before publishing. This keeps the existing entry represented in the report instead of treating it as removed. The source must remain a Yes/No attribute on a type with exactly one asset per group while a draft, current published definition, or existing report uses it. Its attribute and type cannot be deleted or retyped during that time. Older reports keep their source protected even after a newer definition removes the binding. Reports using other forms for the same asset group preserve sources used by published templates or saved reports. An unpublished template draft does not change those forms’ asset deletion behavior. Publishing, including imported publications, validates the source against the current configuration. Missing or duplicate source values are checked for the selected group when creating or saving its report; they do not prevent publishing a template for other groups. ## Fill in the report * New and duplicated reports prefill the question from the group's saved setting, including **No**. A delayed or offline creation refreshes its cached prefill when it reaches the server; later saved edits sync normally. A required question must have either Yes or No selected; it has no N/A option. * Changing the answer updates visibility immediately throughout the form. Hidden questions do not count as unanswered required questions. * Saving the report saves a changed answer back to the group's setting. Offline changes reach the group when the report syncs. New or duplicated reports on the same device use queued setting changes while offline. The asset group must already have its Report Config entry. Create the group and that entry before starting a bound report; the mobile New Asset Group flow cannot start one. * Choosing **No** does not erase manufacture dates already stored on the extinguishers. Hidden answers are omitted from the saved report. * Saving an unchanged answer on an older report does not replace a newer group setting. Existing reports retain their own recorded answers. See [Save a draft and publish an inspection report](/field-operations/inspection-reports/save-a-draft-and-publish-an-inspection-report.md). --- # 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://learn.withessential.com/field-operations/inspection-reports/show-or-hide-asset-questions-from-report-information.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.