Vladi Gubler
Vladi Gubler
November 12, 2026
Stay in the know
Get helpful videos

The shortest path from a SharePoint form to a finished document is a button on the form itself. The user fills in the item, clicks Print, and the PDF downloads. No print preview to open, no template to choose, no separate step to remember.

The Print component of Ultimate Forms powers the button, and the setup is two pieces: a print template that defines the document, and a button on the form that generates it. This guide builds both, then covers the options that make the button production-ready. For the full output system around it, see the complete document generation guide.

Why the button belongs on the form

Document generation usually lives a step away from the data. The user saves the form, finds the item in the view, opens the print preview, picks a template, picks a format, and finally gets the file. Every step is small. Together they are the reason people screenshot forms instead.

The form button collapses all of it into one click, at the one moment the user is already looking at the record. The quote is generated while the conversation is still happening. The completed inspection leaves as a PDF before the inspector moves on. The document becomes part of filling in the form, not a chore after it.

One option makes this genuinely safe rather than merely fast: the button can save the form first, so the document always reflects what is on screen, not what was last saved. More on that below, because it is the detail that separates this button from a shortcut.

Step 1: the print template

The button needs a template to render. If the list already has one, skip ahead; otherwise:

  1. Go to the list and click Design on the toolbar.
  2. Inside Ultimate Forms, click Print and export.
  3. Name the template and choose the columns it should include.
  4. Make sure the Type is Item. The button prints the single item open in the form, so a List-type template will not appear for selection.
  5. Save.

Print template

For a fully designed document, upload a Word file as the template instead: an ordinary document with column names in double square brackets, like [[Title]], which each item fills with its own values. The Word generation guide covers that path end to end, and the designed-reports guide covers making it polished.

Step 2: the button on the form

Now the form side, in Form Designer:

  1. On the main page of Ultimate Forms, click Form designer. If the list has no modern form yet, generate one or start from a blank canvas.
  2. Drag a new button from the control gallery onto the canvas.
  3. Click the button to open its properties.

Button properties

  1. Change the button's Type to Print and export.
  2. Select the print template. At least one Item-type template must exist before Form Designer opens for it to appear here.
  3. Select the output format: HTML, PDF, Word, or Excel.
  4. Publish the form.

That is a working document button. The options you skipped are what turn it into a finished one.

The options that matter

Commit unsaved changes. Toggle this on, and the form saves itself just before generating. On the Edit form, pending changes are written first. On the New form, the item is created and the form switches to Edit, then the document generates. Without this option, a user who types a correction and clicks Print gets a document of the record as it was. With it, what you see is what you print. For most buttons, this should simply be on.

Confirmation prompts. The button can ask before it acts, with your own prompt text, localized into the languages your users work in. Useful when generation has side effects the user should notice, such as the save itself.

Permission rules. The button can appear only when it should: when Status equals Approved, or only for certain roles. The rules pillar covers the conditions, and a quote button that appears only on approved quotes is worth the two minutes it takes.

One Print button, not two. The command bar carries its own Print button, and a form with both can confuse users into the longer path. The Command bar settings let you hide the built-in one, so the form's button is the only door.

Where the button earns its keep

Sales quotes. The rep fills in the quote form and clicks Print while the customer is still on the call. The Word output even lets them personalize the cover note before sending. No quote waits for a formatting pass.

Field inspections. The inspector completes the form on site and generates the PDF on the spot. With Commit unsaved changes on, the report always matches the final entries, including the correction made ten seconds before the click.

HR letters and confirmations. The employment confirmation, the training certificate, the equipment receipt: each is one record and one template, produced by whoever opens the form, with permission rules keeping the button to HR's side of the process.

Approved requests. A button that appears only when Status equals Approved turns the approval itself into the document moment. The requester sees the button appear, clicks it, and holds the formal record of the decision.

The pattern across all four: the person who owns the moment produces the document in it.

Testing it out

Open an item in its Display form and click the button: the document downloads. Edit the item, change a value, and click again: the form saves first, then generates, and the document carries the change. Then try the New form: click Print before saving, and watch the item be created, the form switch to Edit, and the document arrive.

Form with Print button

Those three tests cover the three states a user can click from, and they take two minutes together.

Beyond the button

Everything the Print component does is available to the button's template. Attachments can embed inside the generated PDF, so the request prints with its supporting documents inside it. Additional attachments defined at the template level ride along with every generated document, terms and conditions with every quote, without being attached to any item.

And when the document should exist without anyone clicking at all, the same template serves an action: generated, saved, or emailed in the background when the status changes to Approved, or on a schedule. The button and the action are not competitors. The button serves the person looking at the record; the action serves the process. Most lists that have one eventually grow the other, with the automation engine carrying the background half.

The sum is a form where the document is simply part of the workflow. The user who can fill in the form can produce the document, correctly formatted, from current data, in one click, and the training for it is the sentence "click Print."

Frequently asked questions

Q: How do I generate a document directly from a SharePoint form?
A: Add a button in Form Designer with its type set to Print and export, pick an Item-type print template and an output format, and publish. Clicking the button generates and downloads the document for the open item.
Q: Which output formats are available?
A: HTML, PDF, Word, and Excel, chosen in the button's properties. PDF is the usual choice for final documents; Word suits documents the recipient will edit.
Q: What happens if the form has unsaved changes?
A: With Commit unsaved changes enabled, the form saves first, so the document always matches what is on screen. On a New form, the item is created and the form switches to Edit before generating.
Q: Can I control who sees the Print button?
A: Yes. Permission rules show or hide the button by user, group, or conditions, such as only when Status equals Approved. The built-in command-bar Print button can be hidden separately to avoid confusion.
Q: Does the template need anything special?
A: Only that its type is Item, since the button prints the single open item. The template itself can be column-based or a designed Word document with [[Column]] tokens.
Q: Can the same document be generated automatically instead?
A: Yes. An action can render the same template in the background, on events or schedules, and email or file the result. The button covers on-demand generation; actions cover the automated cases.
Loading...

Add your comment

Comments are not meant for support. If you experiencing an issue, please open a support request.
Products
Vladi Gubler | October 24, 2026
SharePoint items can carry true electronic signatures: tamper-evident, identity-verified, and bound to the data they sign. The Signature component of Ultimate Forms is a column you add to any list or library, attach to the columns whose values it should protect, and sign in one of three ways, real-time username and password validation against your...
Products
InfoPath reached the end of its road on July 14, 2026, and Ultimate Forms is its natural successor for SharePoint forms: browser-based design instead of a client application, data stored as real SharePoint items instead of XML, all column types supported, and permissions, validation, automation, and printing built in. This comparison walks the two...
Products
Vladi Gubler | April 30, 2025
If you’ve ever used Survey lists in SharePoint, you’re likely familiar with a powerful and often underappreciated feature: the Rating Scale column. This special column type presents a matrix of statements or questions alongside a numeric scale, typically used for gathering structured feedback. The idea is simple but incredibly effective - allow...
Build powerful business applications in SharePoint using only your browser.
100% No-Code Solution
It’s never been easier to create, innovate, and share. All you need is your web browser!
Cost-Effective
Address business process pain points immediately. Save time and money.
Fantastic Support Team
In addition to our responsive support team, a wide variety of resources, documentations, tutorials, blogs and webinars is available to you
Popular Solution Templates
Corporate Gift Management System
Streamline and automate corporate gift planning, delivery, and tracking
Purchase Order
Automate and manage the full purchase order process — from request creation and approval to supplier management and delivery tracking
Payment Agreement
Formalize payment terms, schedules, and confirmations in one structured workflow
Microsoft partner logo
© 2005-2026 Infowise Solutions Ltd. All rights reserved.
Trust Center | Cookie Policy | Cloud SLA