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

Cannot save selections in a drop down box

Avatar

Level 2

Hi, I originally posted this in the'Acrobat Windows' section but was told to post here instead.

I created a snazzy form in Adobe Designer 7.0.  This form had drop down boxes with 3 or 4 selections in them.

When I open AA 7 Pro and fill the form out, it won't save the drop down box entries.

For example:

One field is just a text entry, so I'll enter "20,000".  The next field has 3 selections "Diesel, Gasoline, Kerosene"; I will select Diesel.

I will save, close and reopen that file.

The "20,000" will be there, but it won't save the "Diesel".

So what gives?  Is it me?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Have a look at the bindinng tab of the fields that do not show up and make sure that they are NOT set to None. Look at a

field that is being saved. Is it set to Normal? If it is set all the fields that you want saved to Normal.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Have a look at the bindinng tab of the fields that do not show up and make sure that they are NOT set to None. Look at a

field that is being saved. Is it set to Normal? If it is set all the fields that you want saved to Normal.

Paul

Avatar

Level 2

Thanks for the fast response!!

This is indeed the problem and changing the binding to 'Normal' solves my problem completely.

Thanks again!!

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