-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Description
When GravityMCP (using Claude) creates entries that include checkbox fields, the values are stored and displayed as a JSON array string in the Gravity Forms entry (e.g., ["integrations", "performance", "data_management"]).
Expected behavior
Checkbox selections should be stored in the same way as when submitted through a normal Gravity Form — i.e., each choice is recorded in its respective checkbox input and displayed as the selected labels/values in the entry details.
Actual behavior
Instead of storing the values across the child inputs, the entire JSON array is saved as a single string. This results in the backend showing raw JSON, which is inconsistent with normal Gravity Forms behavior and may cause issues for downstream logic or integrations that rely on standard checkbox formatting.
Steps to reproduce
- Create a form with a checkbox field.
- Use GravityMCP (with Claude) to generate an entry that includes multiple checkbox values.
- View the entry in the Gravity Forms backend.
Observed result
The checkbox field displays the JSON array string.
Expected result
The field should display the selected choices properly, as if submitted by a normal form submission.
Impact
- Entry data is harder to read for administrators.
- Downstream add-ons and integrations relying on standard Gravity Forms checkbox data may not behave as expected.