Tx GuysAnother alternative I'm considering is preparing a pre-built fragment using the vanilla AEM table. Obviously it will still be effort to build the initial table, but afterwards, form authors would simply need to create a panel, point it to the fragment, and if they needed to change the rows et...

Hmmm. TxThat's what I was afraid of, and since it needs to be author-able I might be in for a big job.Anyhoo, let me give it a college-try and see how it works

Tx SteveHow would the data binding work in such a custom component though? I might be missing something obvious here, but the value behind the vanilla Table component is the ability for a forms author to specify the data binding for each cell in the table.

I'm currently on a project where we are building a number of predominantly numeric tables in Adaptive forms. Typical example is like a company's balance sheet or income statement. These tables are generally about 10-30 rows with 5 or more columns with numeric cells.Using the Vanilla AEM Table compon...

On one of my ES4 servers (not yet migrated to AEM Forms), I get the following exception in the server log constantly:LCCRXIntegrationService is not ready, unable to push asset to repository. Please use forced sync option to sync up the asset.I am aware that LiveCycle has a built-in CRX repository, b...

Tx NitinJust to wrap up this thread, I'm posting my final solution. Key point is that you use the generatePDFOutput method, but pass in null as the XML data.Here's a snippet:        ... flattenXfaForm(File inXfa, String outputFolder)    {             ....            Document doc=null;            Str...

OK, I've put together a quick sample that seems to work. Key point is that you use the generatePDFOutput method, but pass in null as the XML data. Here's a snippet:        ... flattenXfaForm(File inXfa, String outputFolder)    {             ....            Document doc=null;            String xfaNam...

Just found this statement on the Output Service docs page:The generatePDFOutput operation can also accept an XFA-based PDF form as input and return a non-interactive version of the PDF form as output.So it looks like the method was removed but the functionality is now inside the other method

Hi MahendranAfter checking the docs, it seems that flattening is available in the OSGi Assembler service. Check out https://helpx.adobe.com/aem-forms/6-2/assembler-service.htmlBut there's a caveat: "The Assembler service uses the Output service to flatten dynamic XFA forms. If the Assembler service ...