Form-like interactions in Figma - Cell-by-Cell Formula Trace

Sample Data

This table shows user data with Name, Age, and Country columns.

Cell	Value
A1	Name
B1	Age
C1	Country
A2	Alice
B2	30
C2	USA
A3	Bob
B3	25
C3	Canada
A4	Carol
B4	28
C4	UK

Formula Trace

FILTER(Table1, Table1[Age] > 26)

Step 1: Table1[Age]

Step 2: Table1[Age] > 26

Step 3: FILTER(Table1, [true, false, true])

Cell Reference Map

    A       B       C
1 | Name  | Age   | Country |
2 | Alice | 30    | USA     |
3 | Bob   | 25    | Canada  |
4 | Carol | 28    | UK      |

Arrows: Age column (B2:B4) feeds into FILTER condition

The formula uses the Age column (cells B2 to B4) to filter rows.

Result

    A       B       C
2 | Alice | 30    | USA     |
4 | Carol | 28    | UK      |

The filtered table shows only users older than 26: Alice and Carol.

Sheet Trace Quiz - 3 Questions

Which rows does the FILTER formula keep?

A Rows where Age is less than 26

B All rows

C Rows where Age is greater than 26

D No rows

Key Result

FILTER(table, condition) returns rows where condition is TRUE

Practice

1. What is the main purpose of using form-like interactions in a Figma dashboard prototype?

easy

A. To make the dashboard interactive and user-friendly

B. To write actual database queries

C. To create static images only

D. To export data directly from the prototype

Solution

1. Step 1: Understand the role of form-like interactions

   Form-like interactions simulate user input like typing and selecting, making prototypes interactive.

2. Step 2: Identify the benefit in dashboards

   Interactive dashboards improve user experience by allowing testing of input flows before real implementation.

3. Final Answer:

   To make the dashboard interactive and user-friendly -> Option A

4. Quick Check:

   Form-like interactions = interactive dashboards [OK]

Hint: Think: Why add input fields in a prototype? For interaction! [OK]

Common Mistakes:

• Confusing prototype with actual data processing
• Thinking prototypes export real data
• Assuming static images can simulate input

2. Which Figma feature is essential to simulate typing in a form field during prototyping?

easy

A. Component Variants

B. Auto Layout

C. Prototype Interaction with 'On Click' and 'Change To'

D. Vector Networks

Solution

1. Step 1: Identify how typing is simulated

   Typing simulation requires changing the form field state when clicked or typed into.

2. Step 2: Match with Figma features

   Prototype interactions with triggers like 'On Click' and actions like 'Change To' allow switching component states to simulate typing.

3. Final Answer:

   Prototype Interaction with 'On Click' and 'Change To' -> Option C

4. Quick Check:

   Typing simulation = Prototype Interaction [OK]

Hint: Simulate typing by changing states on click in prototype mode [OK]

Common Mistakes:

• Confusing Auto Layout with interaction triggers
• Using Vector Networks which are for shapes
• Thinking Component Variants alone simulate typing

3. In a Figma prototype, you have a dropdown component with two variants: 'Closed' and 'Open'. You set an 'On Click' trigger on 'Closed' to 'Change To' the 'Open' variant. What happens when you click the dropdown in prototype mode?

medium

A. The dropdown opens showing options

B. Nothing changes because variants can't switch

C. The prototype crashes

D. The dropdown closes immediately

Solution

1. Step 1: Understand variant switching on click

   Clicking the 'Closed' variant triggers a change to the 'Open' variant as set by the interaction.

2. Step 2: Predict prototype behavior

   The dropdown visually changes to 'Open', showing the options as designed.

3. Final Answer:

   The dropdown opens showing options -> Option A

4. Quick Check:

   Click 'Closed' triggers 'Open' variant [OK]

Hint: Click triggers variant switch to show dropdown open [OK]

Common Mistakes:

• Assuming variants can't switch dynamically
• Expecting prototype to crash on interaction
• Thinking dropdown closes on click when set to open

4. You tried to simulate a form submission in Figma by adding a button with an 'On Click' trigger to navigate to a 'Thank You' screen, but clicking the button does nothing. What is the most likely cause?

medium

A. Figma does not support navigation between screens

B. The button is not set as a clickable component or frame

C. The 'Thank You' screen is missing from the file

D. You must use Auto Layout for buttons to work

Solution

1. Step 1: Check button interactivity setup

   For a button to respond to clicks, it must be a component or frame with prototype interactions assigned.

2. Step 2: Identify common mistake

   If the button is just a shape or text without interaction, clicking does nothing.

3. Final Answer:

   The button is not set as a clickable component or frame -> Option B

4. Quick Check:

   Clickable button = interaction works [OK]

Hint: Ensure button is a component/frame with interaction assigned [OK]

Common Mistakes:

• Assuming Figma can't navigate screens
• Forgetting to assign interaction triggers
• Thinking Auto Layout affects button clicks

5. You want to create a Figma prototype of a BI dashboard form where users select a date range, enter a keyword, and submit to see filtered results. Which combination of Figma features best simulates this form-like interaction?

hard

A. Frames for each screen, Raster images for inputs, and Plugins for data filtering

B. Auto Layout for form layout, Vector Networks for input fields, and Pages for each input

C. Text Styles for inputs, Color Styles for buttons, and Comments for user input

D. Component Variants for input states, Prototype triggers for navigation, and Overlay for dropdown calendars

Solution

1. Step 1: Identify features to simulate input states

   Component Variants allow different states like empty, filled, or focused for inputs.

2. Step 2: Use prototype triggers and overlays

   Prototype triggers simulate user actions like clicking submit or opening date pickers; overlays can show dropdown calendars.

3. Step 3: Confirm best combination

   Component Variants for input states, Prototype triggers for navigation, and Overlay for dropdown calendars combines these features correctly to simulate form interactions realistically.

4. Final Answer:

   Component Variants for input states, Prototype triggers for navigation, and Overlay for dropdown calendars -> Option D

5. Quick Check:

   Variants + Triggers + Overlays = realistic form simulation [OK]

Hint: Combine variants, triggers, and overlays for full form simulation [OK]

Common Mistakes:

• Using Vector Networks which are for shapes, not inputs
• Relying on styles or comments for interaction
• Expecting plugins to simulate prototype input directly