i new designer , xml. have been given basic interactive form , have persevered couple of (often frustrating) weeks extend functionality link xml schema , provide dynamic record creation. unfortunately still having problems when adding new instances of subforms.<br /><br />i have main form reporting issues. underneath there major components on subform (can multiple major components each issue) , under major components sub-components (can multiple sub-components each major component) on child subform of major. can add , delete instances of subforms both levels of records.<br /><br />i have created xml schema based on form since existed, , form fields have not inherited properties schema. however, have bound fields in form xml fields through data connection. schema looks follows (bot not literally same see tags):<br /><br /><element complextype issue><br /> <element issueid string/><br /> ...<br /> ...<br /> <element complextype majorcomponent unbounded><br /> <element majcomponentname string/><br /> ...<br /> <element complextype subcomponent unbounded><br /> <element subcomponent string/><br /> <element quantity string/><br /> ...<br /> ...<br /> </element><br /> </element><br /></element><br /><br />my problem follows: <br /><br />when add instance of sub-component or major component subform, first new instance appears work correctly. however, every subsequent 1 inherits values of previous record , when changed, changes values of existing fields of same name of different node. when change each element in xml schema "unbounded", forms appear work values not nested correctly in outputted xml data file (many records appear under 1 sub-component, example, when new sub-component should added each).<br /><br />i suspected problem might "unbounded" property in schema of major component , sub-component elements not linked designer form because major component , sub-component subforms not bound xml schema. reason not bound because if bind subform, first element, major/sub component name applicable, loses binding.<br /><br />i sorry if doesn't make sense hoping might recognise problem talking creating bother.<br /><br />thanks.
george_hickey@adobeforums.com wrote:
> reason not bound because if bind subform, first element, major/sub
component name applicable, loses binding.
>
your subforms must bound schema work correctly. when first
element "loses binding", mean this? should see binding change
"full path" "relative path", should not losing binding altogether.
--
justin klei
cardinal solutions group
www.cardinalsolutions.com
> reason not bound because if bind subform, first element, major/sub
component name applicable, loses binding.
>
your subforms must bound schema work correctly. when first
element "loses binding", mean this? should see binding change
"full path" "relative path", should not losing binding altogether.
--
justin klei
cardinal solutions group
www.cardinalsolutions.com
More discussions in LiveCycle pre-ES (6.x and 7.x) discussions
adobe
Comments
Post a Comment