Forum Discussion
rsderby
Mar 03, 2023Copper Contributor
Using Power Automate and Syntex to create document with multiple tables HELP?
I work for a performing arts organization, and we manually create documents ("one sheets") related to performance information in tables like casts, crews, chorus details, etc. See the example picture below. I would like to start keeping this table data in Microsoft Lists for all the performances and use the new Power Automate Syntex function to generate these tables into the Word documents automatically.
I am confused on how to go about using the Syntex function to create tables. All of the examples and docs are showing simple examples that look like mail merges. Does anyone have advice how to handle the tables?
Note that the function will have to filter the lists to only pull in the information for that performance (which is in the list as a column), and the next document would have a different performance and so on.
Help?
- Wayne_AddisonCopper Contributor
rsderby Sorry to say I don't have a solution for this. I'm having the same problem and been hunting for a solution for many months now. I want to create an invoice that has a table with each billable item as a row in the table but I can't find any examples how to populate the table. If I use the list columns from a 'get items' it goes into a 'Apply to Each' loop so tried the 'Select' Data Operation and 'Create HTML table' and various array variables and JSON formats but it always fails.
It works if I manually create the doc via the library but not via power automate.
Has anyone succeeded in using tables?
- spucelik
Microsoft
Wayne_Addison you can use a Data Operation -> Compose method to bind the items to a table in content assembly.
- Wayne_AddisonCopper Contributor
Hi spucelik and all on this thread, I've been meaning to try your solution but have been getting a brand new problem when creating the template. Whenever I define the table field I get this error:
It started happening around the time MS switched new Syntex licencing from per-user to PAYG. I thought I'd be ok as my per-user was valid until Apr-2024 then I just saw this...
So MS could be switching off content assembly (or at least any new features) unless you are on PAYG even if you have a legacy per-user licence. Are you guys per-user or PAYG?