BUG: Action Flow Editor forced to list variable ("users Documents") when selecting "Marker Document" (Type Mismatch)

[javiredmar]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When configuring a Bottom Sheet action triggered by On Marker Tap in a Google Maps widget, the Action Flow Editor incorrectly forces a list variable instead of a single document.

Specifically, when trying to pass a parameter (Type: String or Doc Reference) to the Bottom Sheet component, I click UNSET and select Marker Document from the source list. Instead of showing the marker's properties (like Reference or Document ID), the editor instantly forces the variable to become the entire collection list (users Documents) marked in red.

This triggers a "return type mismatch" error. The editor only displays list-oriented options (e.g., Current Index, Item at Index), completely hiding the single document options.

Troubleshooting attempted (without success):

Clicking "Remove" to clear the variable.

Hard refreshing the browser (clearing cache).

Deleting the Bottom Sheet action entirely and recreating it from scratch. The UI still gets hijacked by the list variable the moment I click Marker Document.

(Please see attached screenshots showing the "No Available Options" UI glitch and the Type Mismatch error).

4. Expected Behavior *
   Esto es lo que debería pasar si funcionara bien:

When selecting Marker Document as the source for a parameter, the editor should recognize it as a single document and display its specific properties (such as Reference or Document ID) in the "Available Options" column. It should allow me to pass that specific marker's data to the Bottom Sheet component without throwing a type mismatch error.

Expected Behavior

When selecting Marker Document as the source for a parameter, the editor should recognize it as a single document and display its specific properties (such as Reference or Document ID) in the "Available Options" column. It should allow me to pass that specific marker's data to the Bottom Sheet component without throwing a type mismatch error.

Steps to Reproduce

1. Add Google Map widget.

2. Set Action on On Marker Tap -> Bottom Sheet.

3. Try to pass a Parameter from the Marker Document.

4. Notice the variable gets stuck on users Documents list.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4Kz8r13It2seJE1rrUY8dB/TwWQkgna7g4luxHaxQ2C7GrG7YMR8+kP0xuTdOcd2NML2eZrH0KzPSKkdnIA+UrOTGafqZi1bpiUznKYEOuaZDWCqiSTnx7J9xJJVy117avvBV4KtdvWEZh2zmUDeyATjHYHabwOEcnDvqYWdrXp1WrQ0SLb3kNh1JWeC/v

Visual documentation

Environment

FlutterFlow version: Web (Latest)

Platform: Web

Browser name and version: Chrome (Latest)

Operating system and version affected: Windows 11

Additional Information

I am trying to build a very standard map feature: tapping a Google Map marker to open a Bottom Sheet and passing the specific marker's Document Reference to the sheet's component.

This bug completely blocks my progress because the UI hijacks the variable selection, forcing a list variable. This triggers a type mismatch error and makes it impossible to select and pass the single document reference. It is a critical workflow blocker.

[itsstevenliu]

@javiredmar this is FlutterFlow 101. You have a type mismatch. Your parameter is asking for type STRING. So you can only pass in a type string, not a different type.

Configure your bottom sheet to have the correct parameter type and it will work. E.g. if you're passing a collection's document, then configure the parameter of the bottom sheet to be that collection's document type.

[javiredmar]

@javiredmar this is FlutterFlow 101. You have a type mismatch. Your parameter is asking for type STRING. So you can only pass in a type string, not a different type.

Configure your bottom sheet to have the correct parameter type and it will work. E.g. if you're passing a collection's document, then configure the parameter of the bottom sheet to be that collection's document type.

Thank you so much, Steven! Changing the parameter type to Document worked perfectly. I really appreciate your help!

[Alezanello]

Thanks a lot, itsstevenliu, for the help! I was just about to message the user to confirm your suggestion when they reported that the issue was fixed. Since the problem is now resolved, I’m going to close this for now.