-
Rob_VealForm ID: 232024192342041
Issue Summary
When submitting to our form via the JotForm REST API (POST /form/{id}/submissions), data written to the My Products field (control_stripe, question ID q21) is stored in the database and appears correctly in CSV exports, but does not display in the JotForm submission dashboard. The column appears blank for all API-submitted entries.
Expected Behavior
The My Products field should display submitted data in the dashboard the same way it does for native form submissions.
Actual Behavior
- Dashboard: My Products column is blank
- CSV export: My Products column contains the correct data exactly as submitted
Reproduction Steps
- Submit to the form via REST API: POST https://api.jotform.com/form/232024192342041/submissions?apiKey=...
- Include submission[21] with a plain-text value matching the native dashboard format (product name, amount, quantity, subtotal, tax, total, transaction ID)
- Open the JotForm Submissions dashboard — My Products column shows blank
- Export submissions as CSV — My Products column shows the submitted data correctly
Additional Context
We process Stripe payments independently (not through JotForm's Stripe integration) and submit order data to JotForm via API after payment is captured. The My Products field is critical to our day-to-day operations dashboard and business reporting. We cannot add additional fields to the form as it would break existing downstream parsers and dashboards.
We also attempted updating the field after submission creation via POST /submission/{id} — same result: data in CSV, blank in dashboard.
Question
Is there an API-compatible submission format for control_stripe fields that will render correctly in the dashboard? If so, what is the required field structure?
-
Podo: Support SpecialistHi Rob,
Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.
Regarding your issue with the My Products field (control_stripe, question ID q21) not displaying in the Jotform submission dashboard when submitted via the REST API, but showing correctly in CSV exports, there is no specific documented API-compatible submission format for the control_stripe field that guarantees rendering in the dashboard differently from what you are currently doing.
The data you submit via the API is stored correctly in the database and appears in CSV exports, which means the submission is successful. However, the dashboard display for the Stripe payment field (control_stripe) may require native Stripe integration or a specific internal format that is not publicly documented for API submissions.
Since you process Stripe payments independently and submit order data post-payment, the dashboard may not render the control_stripe field content as it does for native Stripe integrations. This is a known limitation when bypassing Jotform's Stripe integration.
Unfortunately, there is no publicly available alternative field structure or API submission format for the control_stripe field that will make it render correctly in the dashboard like native submissions.
If maintaining dashboard visibility of the My Products field is critical, you might consider using additional custom fields or alternate display methods, but as you mentioned, adding fields could break your existing downstream parsers and dashboards.
For now, the best approach is to rely on CSV exports for accurate data representation of the My Products field submitted via API.
Let us know if you have any other questions.
Your Reply
Something Went Wrong
An error occurred while generating the AI response. Please try again!