Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Exporting XML and/or .csv from PDF form

Avatar

Former Community Member

Is there a way to place a button or macro in a PDF form that would allow a user to automate the extraction of the full XML out of the completed PDF form without using the email functionality? What I'd like to do is automate the Forms-->Manage Form Data-->Merge Data Files into Spreadsheet process--for XML and .csv--or both.

I'm a newbie to LiveCycle and javascript--so the solution may be beyond my comprehension but thought I'd put the question out there.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

There is no XFA equivalent command for this but you can access the AcroForm command. It will bring up the save dialog and the user has to pick the filename (a default one will be provided) and location to store the file . For security reasons you cannot fully automate the save. I have not tried this myself but the command woudl be:

event.target.exportAsText()

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

There is no XFA equivalent command for this but you can access the AcroForm command. It will bring up the save dialog and the user has to pick the filename (a default one will be provided) and location to store the file . For security reasons you cannot fully automate the save. I have not tried this myself but the command woudl be:

event.target.exportAsText()

Paul

Avatar

Former Community Member

Thanks, Paul. I will experiment with that and see what happens.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----