Thoughts on migrating older word merge technology to Power Automate and Word Developer Tab

[lucky_phil_78]

I've spent considerable time developing word templates over the past decade which are populated from a Microsoft Access database and built a decision support system within that Microsoft Access Database to quickly populate complex reports including conditional formatting, linking images etc. The current database is part populated from Microsoft Outlook using power automate using regex functions.

My templates are all built using word .doc file format. Trying to consider if it's working now why change or if using the newer framework will be more stable and quicker.

At present I have some logic built into the merge templates but most of it in the access database and the images are linked using includepicture functions from a local PC directory. I'm looking to move the directories onto a business OneDrive account with IncludePicture unable to work over the cloud using the older merge functions.

I'm interested in the opinion of others as to whether it is worthwhile trying to convert this functionality to more modern framework of Microsoft Power Automate and using its functionality to populate word with the developer tab functions.

[SudeepGhatakNZ · Accepted solution]

@lucky_phil_78 

That is indeed the current approach to create documents.

There are a couple of approaches, some require premium connector other are free (but require additional config).

I have covered some in my blogs, in case you find it useful.

Creating word/pdf document using HTML template - Powering your Apps (sudeepghatak.com)

Create automated Attendee certificates using Power Automate - Powering your Apps (sudeepghatak.com)

[lucky_phil_78]

Thank you for your comments Sudeep. I think the technique I'm currently using is still the best. With longer, more complex mail merges creating HTML will introduce other issues.