DataTypes not working on Cloud Functions

[geret1]

Can we access your project?

• [X] 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

I've tried to use a DataType as a parameter into a cloud function with a validation error on runtime.

Expected Behavior

Accept DataTypes (proper mapping validation) or remove it from accepted parameters.

Steps to Reproduce

1. Create a DataType.
2. Create a CloudFunction.
3. Pasa the DataType as CloudFunction.
4. Run

Reproducible from Blank

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

Bug Report Code (Required)

IT4kz/Ll8ZNIvulA187pbfowtDg7Q1g/TL03pu0bFEggGLbrBIYMaePedk1CTbSgTVFbKEWLsGMd08Lsjvz1EfFdBxGbGqZR+LVcVTyXJVO/aoTSCKmwXURCTJtMGBWD5LaNoCJ5JbdhSloB2DmICty8aDLvJo/7Zwh9f6PHaOI=

Visual documentation

Environment

- FlutterFlow version: FF latest
- Platform:Web, MacOs Desktop
- Browser name and version: Chrome (latest)
- Operating system and version affected: OS X Sonoma 14.5 (23F79)

Additional Information

No response

[geret1]

Switching from DataTypes to JSON solve the issue because at cloud function level FF is considering DataTypes as dynamic and that's the main error. That's the main purpose of DataTypes avoid dynamic.

[Alezanello]

Hello!

You’re absolutely correct; this is the expected behavior when using Cloud Functions with the DataType setting. To send a JSON, please refer to our documentation for more examples and guidance: Cloud Functions Documentation.

Thank you!

[geret1]

Maybe this is the most stupid question ever but how is DataType reachable and selectable while defining arguments in cloud functions?

Please review it because this is the bug. Users can expect that FF map datatypes as serializable map.

[github-actions[bot]]

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

[geret1]

Close ticket due to lack of support.