Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Resetting Hidden Fields

Avatar

Former Community Member

My form starts with a header  sub form with check boxes. The user checks whatever box they need and its cooresponding subform appears. Works great, right? The problem comes when it comes to resetting the fields. I hit the reset button and all of the data is cleared, HOWEVER the hidden fields are still visible? How do I reset it it ALL to look exactly like it is when you first open it? Thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You will need to explicitly reset the values of hidden fields. Go to the click event of the reset button and set the hidden fields to null. For example,

// form1.page1.ResetButton1::click - (JavaScript, client)

xfa.host.resetData();

TextField1.rawValue = null;

Steve

View solution in original post

3 Replies

Avatar

Correct answer by
Former Community Member

You will need to explicitly reset the values of hidden fields. Go to the click event of the reset button and set the hidden fields to null. For example,

// form1.page1.ResetButton1::click - (JavaScript, client)

xfa.host.resetData();

TextField1.rawValue = null;

Steve

Avatar

Former Community Member

Try setting the visible property to the fields you don't want to invisible:

fieldToHide.presence = "Invisible"

Avatar

Former Community Member

Awesome! They both worked for different fields!!!!! Thanks so much!

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