You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When getting field values from a submission using the getFieldValues() function the agree field returns true or false rather than the values assigned in the checked / unchecked options.
Yeah, the Agree field is a tricky one in this situation. For integrations, it's almost always the case that it needs to be a boolean value. Both for the opt-in fields that are typically mapped to it, and to be compatible with provider fields like checkboxes.
We'll need to look at refactoring this for a few different areas to ensure we don't introduce a breaking change.
Would it be possible to introduce a way of flagging that it should be called with checked unchecked values potentially, that way it's not breaking, maybe as a parameter or something?
For sure, just working through updating a few things. Just wanted to mention there's a few moving parts to factor in so bare with me on this one, as it might not be an immediate fix.
Describe the bug
When getting field values from a submission using the getFieldValues() function the agree field returns true or false rather than the values assigned in the checked / unchecked options.
Here is the field config:

And the data returned from the function call:
Steps to reproduce
yes
and unchecked ofno
Form settings
Craft CMS version
5.5.9
Plugin version
3.0.16
Multi-site?
No
Additional context
No response
The text was updated successfully, but these errors were encountered: