Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

Curious problem with drop-downs and flowed layout

Avatar

Level 3

Hi - I have a form (hopefully to become a series of forms) that has a flowed layout which works fine. I introduced a drop-down list which is populated from an XML data file. The user selects the item from the dropdown, and the result forces the name into another text field, and the address into a different text field. In order to get the XML embedded, I have gone into Acrobat and imported the data file into the form - this enables me to Reader enable (using LiveCycle Reader extensions) and all works fine, except for on curious behaviour: The drop-down populates the text fileds as expected, but as soon as I go into the first flowable text box therafter, add in some text and expand the box, the data-populated text fileds become blank. The user would then be in a situation where they would have to complete all flowable areas before they choose from the drop-down. I want the drop-down populated text fields to stay populated.

I tried giving the fields this script on Exit:

setItemState(i

,true)

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

What is the binding that is set for the fields that disappear? Look at the Binding tab in the Object palette.

Paul

View solution in original post

4 Replies

Avatar

Correct answer by
Former Community Member

What is the binding that is set for the fields that disappear? Look at the Binding tab in the Object palette.

Paul

Avatar

Level 3

I hang my head in shame - indeed, the binding was set to none - changed it to normal and it now works just fine. Thanks as always for the help.

Avatar

Level 3

I have an further question that comes from a user, and I think this might

become quite common. My drop-down has 380 entries, which means that some beginning

letters might be 30 or so entries, such as towns beginning with

B. The user has asked if there is any way to type in the first two or three letters

in the drop-down to get closer to the town of their choice, rather than

the single charater selection.

Avatar

Level 2

Hmm, you could certainly allow the users to enter text in the drop-down field and then compare the first 3 (or all) characters against your data by looping over it. I doubt though that that'd work in real time, e.g. provide a user experience as in a Flash/Flex application where the number of options actually decreases visually.

Cheers

Kai

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