Type “PDF” as a Parameter name and select the PDF/Template column as the custom value.
Step 2: Create The “Generate PDF” Button
Head to the layout screen.
Create a button, select “Open Link” as the action, then add the “PDF/Link” as the URL.
Click the button… And magic happens!
This method is totally free, and while it doesn’t automatically upload the PDF to your Glide app. it allows you or your clients to create as many PDF’s as you want! The template is 100% customisable, and you can even use Tailwind CSS to style the template if it tickles your fancy.
If anyone ever needs a hand with getting this up & running, or anything else Glide related, don’t hesitate to reach out or join my free Glide community.
It’s called Screen Studio. Slower than other tools (like Loom) in many ways, but if you can deal with slow export times and don’t mind uploading to Youtube/Loom before sharing it’s pretty neat!
That’s the basic premise! It takes the HTML you use in your PDF template, renders it as a webpage, then triggers the Print/Save As PDF functionality of your browser. Quite versatile and lightweight
I like it…might use it for personal projects. I’m just afraid that this will break /go unmaintained at some point, so I probably won’t use it for client work unless I’m mistaken. Really need a way to get permalinks for PDFs this easily.
May you show me a short/simple HTML code to use it as template to test your nice tool? I have some problems to replicate your steps and can’t get it to work well (not your fault… I’m sure it’s me )
In the end, I’d like to replicate this HTML page and get a PDF file later (it’s just an example) but I can’t find the flaw in my setup.
I also imagine that if you want dynamic line items, tables, sections, etc. you’d have to craft all of that in some sort of template/join list column combination?
Totally get where you’re coming from! I built this for a client so I have no plans of ever taking the app down, but if you want I can send over the source code so you can create your own free instance of the app? That way you can safely deploy it for any of your client work
As for the dynamic line items, you’re spot on. Two separate Tables as follows:
Line Items:
Each individual Line Item has a Template Column (e.g. “HTML”) where the info is dynamic.
// For example:
<li>ITEM - PRICE</li>
Invoice
Then the Invoice table has a Relation Column (Pulling in all the related Line Items), a Joined List Column (joining all of Line Item’s “HTML” columns, separated by new line or nothing (no commas), and a Template Column that pulls info from current invoice as well as the joined HTML from related Line Items.
// For example, the Template Column would look something like:
<h1>NAME</h1>
<ul>LINEITEMS</ul>
// The final HTML (used to create the PDF) will look something like:
<h1>🎓 Loqode Students</h1>
<ul>
<li>Item 1 - $100.00</li>
<li>Item 2 - $200.00</li>
<li>Item 3 - $300.00</li>
</ul>
And the beauty is that since it’s all HTML based you can make the PDF as complex or as simple as you want, and it stays dynamic as the related Line Items or Invoice is updated/edited.
I’m filming a follow-up video explaining all of this and will post shortly
I’m not quite sure what you’re asking/what the use case is… But if all you want to do is display the HTML you can view it natively using a rich-text component.