This gives us the flexibility to do the data shaping in javascript and leave it to the Word connector to create the final document. Therefore we are going to fetch all data upfront in the client and pass a tailored dataset for easy consumption to Power Automate. This makes it not feasible if the document has to span arbitrary tables. The main concern one has with the OOB Word Templates in Power Apps is the fact that it is always scoped to a single entity along with its related entities. ![]() With Power Automate's connector for Word Online we can easily author the template in Word and fill placeholders including repeating content controls like tables or bulleted lists to make sophisticated documents without additional costs for a specific document generation engine. ![]() While the first one has several limitations regarding data retrieval - the latter is frankly just cumbersome to work with although it has received some updates to the report authoring extensions lately. Generating a document in Power Platform with OOB features usually involves Document Templates or SSRS reports based on FetchXML queries. This allows the creation of sophisticated documents without the limitations (single table+referencing tables, poor formatting) of OOB document templates. The data is queried and transformed in a web resource and the document - based on a word template - is created with Power Automate's Connector for Word Online to render the final document as PDF. ![]() Today's post shows a way to create a document with data from arbitrary tables in Dataverse.
0 Comments
Leave a Reply. |