Form-like interactions in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ visualization

intermediate

Identify the Best Practice for Form Accessibility

Which option shows the best way to make a form accessible in a BI dashboard?

A Use labels linked to inputs with <code>for</code> attribute and ensure keyboard navigation.

B Use placeholder text only without labels to keep the form clean.

C Use images as buttons without alt text for visual appeal.

D Disable tab navigation to prevent accidental input changes.

💡 Hint

Think about users who rely on screen readers or keyboard only.

Labels linked to inputs and keyboard navigation ensure all users can interact with the form easily.

🎯 Scenario

intermediate

Choosing Input Types for Data Filters

You want users to filter sales data by date range and product category in a BI report. Which form input types should you use?

A File upload for dates and slider for product category.

B Text inputs for dates and checkboxes for product category.

C Single text input for date range and radio buttons for product category.

D Two date pickers for start and end date, and a dropdown for product category.

💡 Hint

Consider input types that reduce user errors and improve clarity.

Date pickers help users select valid dates easily, and dropdowns simplify category selection.

❓ dax_lod_result

advanced

Calculate Total Sales for Selected Region Using DAX

Given a sales table with columns Region and SalesAmount, which DAX measure correctly calculates total sales only for the selected region in a slicer?

A Total Sales = CALCULATE(SUM(Sales[SalesAmount]), ALL(Sales[Region]))

B Total Sales = CALCULATE(SUM(Sales[SalesAmount]), VALUES(Sales[Region]))

C Total Sales = SUM(Sales[SalesAmount])

D Total Sales = CALCULATE(SUM(Sales[SalesAmount]), FILTER(ALL(Sales), Sales[Region] = SELECTEDVALUE(Sales[Region])))

💡 Hint

Think about how to respect the slicer selection context.

Using VALUES(Sales[Region]) keeps the filter context from the slicer, summing only selected regions.

🔧 Formula Fix

advanced

Find the Error in This DAX Measure for Average Sales

What error will this DAX measure cause?
Average Sales = AVERAGE(Sales[SalesAmount

Figma

Average Sales = AVERAGE(Sales[SalesAmount])

A TypeError because AVERAGE expects a table, not a column.

B Returns zero because of empty SalesAmount column.

C SyntaxError due to missing closing bracket.

D No error, measure calculates average correctly.

💡 Hint

Check the brackets and syntax carefully.

The measure is missing a closing bracket for the column reference, causing a syntax error.

🧠 Conceptual

expert

Understanding Level of Detail (LOD) Expressions in BI Tools

Which statement best describes the purpose of Level of Detail (LOD) expressions in BI tools?

A LOD expressions allow calculations at a specified granularity, independent of the current view filters.

B LOD expressions are used to create visual themes and color palettes.

C LOD expressions automatically refresh data sources in real-time dashboards.

D LOD expressions replace all filters applied by users on reports.

💡 Hint

Think about how to calculate values ignoring or including certain filters.

LOD expressions let you fix the calculation level, like total sales per customer regardless of other filters.

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