Expand my Community achievements bar.

SOLVED

returned (mailed) form expands fields again?

Avatar

Former Community Member

Hi

Sorry for the very basic question but I have an irritating problem

I created some LC forms which have the functionality that if you select a certain country some fields appear/dissapear depending of the choice of the country.

I also attached a 'send form' button so that the filled form is mailed back in PDF to a central point. This all seems to work perfectly.

The problem now is that the returned pdf always shows all fields regardless of the choice of the country made. Where I hoped it would send back the PDF as saved and thus only showing the fields that are needed for that specific country.

Is there a way to change this so that it matches my expectations?

Thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The issue is that you are changing the state of the form by hiding and showing content based on selections. This information is not being saved by the form when you send it. In Designer, if you go to File/Form Properties/Defaults and under the Scripting area make sure the Preserve Scripting Changes to Form is set to Automatically and not Manually and try it again.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

The issue is that you are changing the state of the form by hiding and showing content based on selections. This information is not being saved by the form when you send it. In Designer, if you go to File/Form Properties/Defaults and under the Scripting area make sure the Preserve Scripting Changes to Form is set to Automatically and not Manually and try it again.

Paul

Avatar

Former Community Member

Thanks Paul for the swift answer

it did the trick!

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