- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
I found a solution to this. The 'DataDescription' elements in the data XML are the cause of the problem. Apparently Acrobat/Reader is not able to handle the elements from form 'A' when loading that data into form 'B'.
My solution was to modify my process to:
1.) Create an xml variable (call it 'xmlData')
2.) Create an XDP "wrapper" by setting the value of xmlData in a 'Set Value' operation. Since my top-level form element is called 'TopLevelFormElement', my "wrapper" (the value for 'xmlData') was:
deserialize('<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" xmlns:dd="http://ns.adobe.com/data-description/"
xmlns:impl="http://adobe.com/idp/services" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/">
<xfa:datasets>
<xfa:data>
<TopLevelFormElement>
</TopLevelFormElement>
</xfa:data>
</xfa:datasets>
</xdp:xdp>')
3.) Copy the form data from the original (call it 'originalXmlData') to 'xmlData' by setting this mapping in a 'Set Value' operation:
//process_data/xmlData//TopLevelFormElement = /process_data/originalXmlData//TopLevelFormElement
4.) At this point, you have a set of data (xmlData) that contains all of your form data but is free of the 'DataDescription' elements that cause problems. Pass 'xmlData' into form 'B'.
5.) Data should be processed as expected in form 'B', and web service calls should be operational.
Views
Replies
Total Likes