Collect Number Inputs by Link and Generate Calculated PDFs

A respondent-facing form should ask for the facts the respondent can provide: quantities, hours, rates, counts, mileage, fees, or scores. It should not ask them to type a total that the template can calculate.

DullyPDF keeps that boundary by publishing number inputs as questions while keeping calculated outputs out of the web form. The generated PDF receives computed values after submission.

Many external recipients are on phones, browser previews, or email clients where editable PDF behavior is inconsistent. A hosted web form is easier to complete, and the final PDF can be generated after DullyPDF has the structured answers.

That workflow is especially useful when totals matter. The respondent provides source values in a normal form, and the owner can generate a flat PDF where completed values are already baked into the document.

Calculated Fill By Link workflows work well for quote requests, reimbursement forms, simple order forms, inspection scores, membership dues, and application worksheets where the respondent supplies numeric inputs but the organization owns the final calculation.

They are a poor fit for complex calculators that require date math, variable-length tables, or business rules outside DullyPDF’s safe formula model. Those should be handled in the source system or a dedicated calculator before the PDF is generated.

A useful fill by link calculated pdf test starts with one document your team already recognizes, not a perfect demo PDF. Open the existing file, review detection, rename ambiguous fields, confirm checkbox and radio behavior, and save the template only after the field list matches the way the document is used in practice.

Then fill one representative record end to end. Include long names, blank optional values, dates, yes/no choices, and any calculated or scannable fields the page depends on. That single controlled run exposes most template issues before they become repeated output problems.

Search & Fill is the right first path when an operator should pick a record and inspect the result before export. It works with row data from CSV, XLSX, JSON, or stored respondent records. SQL and TXT files should be treated as schema-only mapping inputs; database-backed production workflows should query the database elsewhere and send JSON through API Fill.

Output mode matters too. Editable PDFs are useful when someone will continue working in live fields. Flat PDFs are safer when the completed record goes to customers, employees, agencies, signers, or archive systems because the visible values are baked into the page instead of depending on the recipient PDF viewer.

The fill by link calculated pdf workflow is ready to reuse when a teammate can clear the document, rerun the same source record, and produce the same visible PDF without remembering hidden cleanup steps. If the result depends on one person knowing which field to fix manually, the template still needs review before it belongs in a repeat workflow.

• The saved template uses stable field names and reviewed field types.
• Source headers or API keys match the template schema without ambiguous duplicates.
• Checkbox, radio, calculated, image, barcode, and signature fields have been tested if the workflow uses them.
• At least one flat output and one editable output have been opened in the PDF viewers recipients are likely to use.