While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form. If you then click Save, it again offers to reload the current form. After clicking “Yes” to reload the form, you may notice that Designer hangs.
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes
This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3. If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.
If you are attempting to save an XDP file in LiveCycle Designer ES2, created with an earlier version of Designer (i.e. 7, 7.1 or ES), then it can occur that the Save process never completes, and you must kill the Designer process manually in Task Manager. If you analyse the files on your local disk, you will notice some tmp files with large file sizes.
This issue is related to the Data Binding option Allow binding to data not defined by the default data connection. For some forms that contain data connections, Designer ES2 can get stuck in an endless loop while saving the XDP to an intermediary tmp file. You will see the tmp file will contain a huge number of repeated entries related to the DataDescription similar to the following:
<DATACONNECTION xmlns:dd=”http://ns.adobe.com/data-description/” dd:additions=”$template(DATACONNECTION)”/>
This issue has been fixed in LiveCycle Designer ES3 and later cumulative QuickFixes for Designer ES2. You should ensure you are using the latest QF for Designer ES2, or contact your support representative.
Removing the data connection will allow the file to be saved, and also disabling the option in the form properties Allow binding to data not defined by the default data connection. Also putting the sample XML data/schema file used to create the data connection into the same folder as the XDP, opening the XDP, refreshing the Data connection, will then allow to save properly.