@PaulD1
Yes, the Plumsail connector is very flexible and can accept records and tables worth of items.
We use the connector for Word and Excel creation and it works well. The Template is defined differently than a standard Word template, but it's much more flexible.
In reference to my posting - we started with solution #2 and it was painful. Templates needed to be maintained at the Document Library level and if more than one was needed, then at the Content Type level. In order to get the template to fill-in, it took a lot of work in Flow to assign the proper column values.
With Plumsail, we simply had a Template library, PowerApps "picked" the proper Template name and that, along with a payload of JSON to Flow and we had our document created. Tweaks to the template were easy to do since it was just a regular document in a document library. Overall...Highly recommend it!
Plumsail Documents will work with DOCX, XLSX and HTML Templates.
It will generate any of the above plus PDF and can also be used to manipulate PDF files (merge, split, convert, etc.).
I also found their documentation and demos to be very well done and spot-on.
Some specifics to check out:
Defining templates with Plumsail.
Specifically - tables with Plumsail.
Also in the subscription are several Actions that can be taken besides just creating docs from templates.
They have pretty decent licensing prices and, when we put it side-by-side to the amount of work needed for the other options, it was well worth it.
I haven't looked at the Word (Business) Connector yet, but it seems pretty pale in comparison. And, it requires all users of it to be P1 or above. Plumsail charges by the document created and it is not a per user license.
They also have other subscriptions for things like super-pumped Flow actions and a slew of other products that are not necessarily Flow or PowerApps specific.