-
MMLawHello,
I’m currently using Jotform Documents (not Jotform Forms) and trying to set up a bulk send of personalized documents based on a CSV file.
My goal is to upload a document template, and then use a CSV file to auto-populate fields such as:
- Name
- Amount (number field)
- Additional personalized details
I have created fields inside the document editor and assigned them unique names (for example: “number4” for the amount field).
In my CSV file, I have matching headers:
- name
- number4
However, when I upload the CSV and try to generate or bulk send the documents:
- The "number4" field does NOT populate
- Other fields (like name/email) work as expected
I have already tried:
- Ensuring exact matching field names between the document and CSV
- Removing spaces and formatting issues
- Changing the field type (text/number)
- Testing with a clean, minimal CSV file
- Re-uploading and remapping fields
The issue persists specifically with this field not being recognized or populated.
Could you please clarify:
- How exactly Jotform Documents maps CSV headers to document fields?
- Whether there are any limitations or naming conventions for numeric fields?
- If there is a different required process for bulk populating document fields (without using forms)?
I’d appreciate step-by-step guidance specific to Jotform Documents bulk send with CSV.
Thank you in advance.
-
Podo: Support SpecialistHi MMLaw,
Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.
Regarding your issue with Jotform Documents bulk send using a CSV file, here is what I can clarify based on available information:
CSV Header to Document Field Mapping: Jotform Documents maps CSV headers to document fields by matching the exact field names. You have done this correctly by ensuring the CSV headers match the unique field names in your document template.
Limitations or Naming Conventions for Numeric Fields: There is no specific mention of limitations or special naming conventions for numeric fields in Jotform Documents. However, since your numeric field "number4" is not populating while other fields like name and email work fine, it might be related to how the field type is handled internally. You have already tried changing the field type and testing with a clean CSV, which are good troubleshooting steps.
Bulk Populating Document Fields Without Using Forms: The process you are following—uploading a document template, creating fields with unique names, and uploading a CSV with matching headers—is the standard approach for bulk sending personalized documents in Jotform Documents. There is no different required process mentioned.
Since the issue persists specifically with the numeric field not populating, I recommend double-checking the following:
- Ensure the numeric field in the document editor is properly configured to accept the data format coming from the CSV.
- Try renaming the numeric field to a simpler name without numbers or special characters to test if the field name might be causing the issue.
- Verify that the CSV file encoding and format are standard (UTF-8, comma-separated) and that no hidden characters are affecting the field recognition.
If these steps do not resolve the issue, it may be a specific limitation or bug related to numeric fields in Jotform Documents bulk send, which is not explicitly documented.
Give it a try and let us know how it goes.
-
MMLawHello,
Thanks for the response, but the suggestions provided do not resolve the issue.
To clarify, this is specifically about Jotform Documents (not Forms) and the Bulk Send via CSV feature.
Current status:
- CSV headers exactly match the document merge tags
- Name and email fields populate correctly
- Numeric field does NOT populate
- I tested with:
- Plain text merge tags
- Different field names (amount, id, value, etc.)
- Different field types (text and number)
- Clean CSV (UTF-8, no spaces, tested in plain text editor)
- Minimal test file (2 rows only)
Result:
→ Only this specific field consistently fails to populate
→ Other fields work as expected under the exact same conditions
This strongly suggests this is not a configuration issue, but a problem with how Jotform Documents handles certain fields during CSV bulk generation.
Please clarify the following:
- Is there any known limitation with numeric fields in Jotform Documents bulk send?
- Is CSV mapping in Documents officially supported without using Forms as an intermediary?
- Can you confirm whether this is a known bug and escalate to your technical team?
If needed, I can provide a sample CSV and document template for replication.
I’d appreciate escalation to a human support agent or technical team, as this appears to go beyond standard setup troubleshooting.
Thank you.
-
Sheena JotForm SupportHi MMLaw,
For us to troubleshoot, can you provide us with the CSV file so we can check and test them from our end? You can upload the files to Google Drive and send us the link. You can also send a screenshot of your result to help us to understand better what’s going on. Let me show you how to post a screenshot to our Help Center:
1. On the Help Center page, scroll down to the Your Answer section and click on the Image icon.
2. Drag and drop your image into the Upload box, or click on it and select your file.
3. Then, click on the Add button in the bottom-right corner of the window.
4. To resize it, click on your screenshot and then click on one of the boxes in the corners, and drag it inward.
5. Once you're finished, click on the Post Answer button at the bottom right of the Your Answer section.
That's it. Once we hear back from you, we'll be able to help you with this. -
MMLaw -
Kevin JotForm SupportHi MMLaw,
Thanks for sharing the details about what you are experiencing. I have performed a test and I can see what you are referring to, when you import the data to the Bulk Send section, Jotform only supports the name and email fields, at the moment it's not supported to add other fields to this section. This means that even if you add additional fields to your form, other fields will not be listed when you bulk send the document.
Here is also a screenshot of what I could see on my end upon testing:

We can open a feature request for this, it's important to mention that we cannot provide an estimated timeframe for this to be implemented, but we will keep you updated through this support ticket.
Let us know if you need any more help.
Your Reply
Something Went Wrong
An error occurred while generating the AI response. Please try again!
