Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

Removing subforms

Avatar

Level 1

I have produced a form with the first page showing tick boxes for the different sections of the form.  The user deselects any sections that they do not want by deselecting the tick box.  This removes the associated subforms and works perfectly.

After completing the form the data is submitted to me via email (XML format) and I import the data back into the PDF form.  On import, even though the tick boxes on the first page are deselected it still shows all of the subforms.  The only way I can get rid of the subforms that are not required is to select and deselct each tick box again.  Is there a way around this so that the tick boxes continue to work when the XML data is imported back in?

Many thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You can check the File/Form Properties/Defaults and ensure that the save scripting state changes is checked. If it still does not work then you will have to write an initilization routine to set the state of the form when it loads.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

You can check the File/Form Properties/Defaults and ensure that the save scripting state changes is checked. If it still does not work then you will have to write an initilization routine to set the state of the form when it loads.

Paul

Avatar

Level 1

Thanks Paul!

I realised I didn't have the script under 'Initialize'.  It works now - thank you.

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] ----