Posted by Ethan Gruber on
URL: https://discuss.orbeon.com/Inexplicable-results-with-repeatable-fr-autocomplete-and-xforms-delete-tp932322p3564149.html

I recall having this problem and had to make the control use an itemset based on its current position.  For each repeatable element to which the fr:autocomplete is assigned, I had to insert a element to hold the response from the dynamic itemset query whose position is identical to that of the fr:autocomplete within its context into an aggregated instance.  For example, the third fr:autocomplete within your repeatable element had to refer to instance('suggestions-aggregate-subject')/response[3].  See http://code.google.com/p/eaditor/source/browse/trunk/inputs/subject-autocomplete.xml?r=110 for more info.  The $uid variable is tied to the position and 'suggestions-aggregate-subject' is the aggregate instance.  If you deleted your third fr:autocomplete control, you also had to remove instance('suggestions-aggregate-subject')/response[3].

This ceased to be an issue when I migrated to XBL as each fr:autocomplete relied upon its own internal model.

Ethan




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws