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

Binding a sequence XSD Schema to repeating subform elements

Avatar

Former Community Member

Hi, I am creating a form with repeated table rows using an Add button to add rows dynamically. I am binding the row with the xsd schema with [*] at the end in the data binding option with checked repeat row for each data item. While submitting the form as XML data to the java controller I am getting only one table row and not other rows added dynamically by add button functionality.

Untitled.jpgUntitled1.jpg

    

Untitled2.png

I want to know that how to generate the xml of dynamically added rows bonded with XSD schema.

I have also explore the below link but doesn't resolve the issues:

http://www.adobe.com/devnet/livecycle/articles/binding-xsd.html

Thanks in advance

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I have resolved the issues by adding maxOccurs="unbounded" in xsd schema with the binded element name.

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

I have resolved the issues by adding maxOccurs="unbounded" in xsd schema with the binded element name.

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