PL-200 · Question #335
Case Study 4 - Contoso Suites Background Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs…
The correct answer is Edit the resident form.; Add a form component.; Select the lookup. The correct sequence of actions configures the Resident form to display related food details by adding a Quick View Form component linked to the food lookup.
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Edit the resident form.
- Add a form component.
- Select the lookup.
Explanation
The correct sequence of actions configures the Resident form to display related food details by adding a Quick View Form component linked to the food lookup.
Approach. The case study describes a 'Resident table' that tracks dog stays and has a lookup for 'food'. It also states that 'food type and amount are logged on each resident record', implying these details should be accessible or displayed on the Resident form. The most appropriate way to display related record information (like food type and amount from the linked Food record) on a form in Power Apps model-driven apps is by using a Quick View Form component. The steps to achieve this are:
-
Drag 'Edit the resident form.' to position 1: To make any modifications to the Resident form, you must first open it in the form editor within the Power Apps maker portal. This is the essential starting point for form customization related to the 'Resident' table.
-
Drag 'Add a form component.' to position 2: After opening the form, if the goal is to display details from a related record (the food record via its lookup), you would add a Quick View Form component. A Quick View Form component is a type of 'form component' designed specifically for this purpose. It acts as a container to show fields from a record related via a lookup.
-
Drag 'Select the lookup.' to position 3: Once the Quick View Form component has been added to the Resident form, you then need to configure it. A crucial configuration step for a Quick View Form component is to associate it with an existing lookup field on the current form. By 'selecting the lookup' (specifically the 'food' lookup in this context), you tell the Quick View Form component which related record's data it should retrieve and display (using a pre-defined Quick View Form from the looked-up Food table). This completes the setup for displaying related food details on the Resident form.
Common mistakes.
- common_mistake. - Incorrect starting form: Dragging 'Edit the dog form.' to position 1 would be incorrect because the scenario explicitly mentions the 'Resident table' for dog residency and the requirement to log food type and amount 'on each resident record'. The context for configuration is clearly the
Residentform. - Irrelevant actions: 'Add a code component.' is used for custom client-side JavaScript or TypeScript controls/logic, not for displaying related data through standard form elements like lookups or Quick View Forms. This action is not relevant to the described scenario.
- Incorrect order: Swapping 'Add a form component.' and 'Select the lookup.' would be illogical. You first add the structural element (the form component, e.g., Quick View Form), and then you configure that component, which includes specifying the lookup field it should utilize. You cannot 'select a lookup' in this context as an independent first step of configuration for a complex component; rather, it's a step within the component's properties.
Concept tested. Form customization in Power Apps model-driven apps, specifically the use of Quick View Forms to display related record information via lookup fields, and the sequential steps involved in editing a form.
Topics
Community Discussion
No community discussion yet for this question.
