Hi @guptast, as mentioned earlier, it is worth looking at html2pdf.fr
This example PDF is auto generated using a mobile phone, it uses png, jpg and svg graphics.
1 Like
Thanks for your response.
I had a look at this PDF generator. My understanding is that this software needs to run PDF generation process on the server. I don’t have a programming background, so, I wanted to work with options that provided me client-side functionality 
Just bumping this popular feature request as it’s been some time now. If it won’t receive much attention, any recommendations on the best or simplest library to integrate with (rather than api)?
Great library Max!
Thanks Dave. It would be nice to have a server side module, similar to the options available for files. It’s a shame as this request is over 2 years old now and still no news on it potentially becoming a feature
2 Likes
Hi @George, @Teodor & @patrick,
Is there a chance that this feature request will be realized? If yes, I would be happy if you could give a timeframe.
I’m looking for a server action for NodeJS with the possibility to use repeats on the server side. I have automatically generated reports with a cronjob which are generated with mPDF on an “old” PHP site which was not yet brought to Wappler. I want to recreate it in Wappler with the NodeJS server model and need this last piece of my puzzle 
.
Marcel
1 Like
@MH2ag,
Have you tried the extension we released? Link just above your post.
If you have, could you share what is missing so we can try to improve it.
I tried it, but like I wrote I need the possibility to use repeats on the server side. I didn’t yet see how this would work. Did I overlook something?
From our understanding, the concept of repeats is not something that is related to HTML to PDF generation.
More powerful report generators have a complex UI of their own to set repeatable data bindings and other complex designs for the report. Something like Crystal Reports come to mind.
The logic here is to generate your HTML and supply that to the extension.
You can use repeat in server action and set value to first generate your table HTML. Then just pass that to the extension.
Something like this:
Repeat in eMail body
You are correct, that this is not related to HTML to PDF generation. I know that this is a problem of using repeats on the server side. This of course also applies to the eMail body.
I know that there are workarounds for this (like in your link), but I would prefer a Wappler solution before I start. I was hoping that if Wappler would create a server side action for generating PDF’s they would also integrate a solution for server side use of repeats.
As the Wappler team didn’t post anything to this thread for a long time I wanted to make sure if it is on their timeline or not. If it’s not I would look into the workarounds.
1 Like
So you are looking for a DB to HTML kind of solution? And that output you wish to use in email or PDF generation?
Any chance we can see PDF Generator in Wappler 4.x?
any news on this feature request?
1 Like
Is this feature request on your roadmap or will you suggest using external extensions instead?
There are a lot of feature requests and it would be great to know if you consider them to integrate them in Wappler in the near future or suggest using external extensions. I understand that it is difficult to give a roadmap, but it would also be helpful to know what the next Top 5 features you are working on.
I’m planning to extend the features of our customer portal and I would like to know if it is worth waiting or not.
2 Likes
I really don’t understand why users continue asking for more features in Wappler when:
i) the features already exist in well-established 3rd party tools and do a great job for free (e.g. PDFMonkey offer 300 free documents per month)
ii) It’s clear the Wappler team is ridiculously overstretched
It would make far more sense commercially to ensure they are spending their time hardening their existing software, removing all the annoying little bugs, improving the quality of their weekly releases and reducing all the weekly regression issues we see.
Once that’s finally under control, recruit a documentation specialist to reduce churn rates - by ensuring more new customers onboard and stay rather than sign-up briefly, get frustrated with bugs and lack of guidance and leaving.
Following that, hire some specialist support staff and stop burning developer time doing support.
More customers -> more revenue -> more professionals -> a better quality solution.
In my opinion, the best thing Wappler could do is to feature freeze for the rest of 2022. Start using Wappler to develop something to help find and fix all the little issues and then document everything that is there today.
Basic software business 101.
2 Likes
I think you didn‘t understand my comment. I was just asking if it is worth waiting. It would be probably a good idea to close a feature request if it is not on the timeline. This way everyone knows to look after a third party integration. I don‘t have any problems with that. I know that the team is doing a great job.
My comment was far more general and not aimed at your request. You are entitled to ask for whatever you want. I’m just frustrated at how the business is failing to capitalise on the great work they’re doing. As a user, it’s very clear what needs to change to make Wappler the success it deserves to be but it’s obviously not clear to the team themselves.
I fully understand that in a business like DMXZone, new features are everything. but in a professional IDE, less is so often more - particularly if it’s robust and well planned out.
One simple example, why do we support so many databases ???
Just imagine how robust and feature-rich the DB manager would actually be if the team were allowed to focus on just one (e.g PostGresQL or mySQLor MariaDB) and utilise its full capabilites and APIs
Imagine how integrated and seamless it could be if we targeted the DigitslOcean platform only? One click set-up, effortless load-balancing and Traefik config - by focusing it’s all achitevable. And less frustration and bug reports
By doing less, focusing on particular platforms, this could be amazing, far more productive far less frustrating and a much bigger success.
4 Likes
I agree with your first reply about holding off on new features and fixing the little bugs, but I strongly disagree with focussing on only 1 database etc etc. I really appreciate that Wappler is flexible
2 Likes