Hi,
Something to try might be to copy your data to a second data set and have your fields bind to those values, then if someone does import data then they are values the form does not look at.
Normally you dataset will look something like (with formData being the root of your data).
<xfa:datasets>
<xfa:data>
<formData>
<a>value a</a>
<b>value b</b>
<c>value c</c>
</formData>
</xfa:data>
</xfa:datasets>
You could copy this dataset outside of the data node (which is were the importData would go);
<xfa:datasets>
<formData>
<a>value a</a>
<b>value b</b>
<c>value c</c>
</formData>
<xfa:data>
<formData>
<a>value a</a>
<b>value b</b>
<c>value c</c>
</formData>
</xfa:data>
</xfa:datasets>
Your fields would then bind using the expression "!formData.a".
To copy the dataset, maybe in the docReady event, use;
xfa.datasets.loadXML(xfa.datasets.data.formData.saveXML(), false, false);
xfa.form.remerge();
You would have to remerge for the fields to pick up the new dataset.
When it comes time to submit the form you would then have to copy the dataset back.
Maybe to much mucking around? Hopefully there'll be a server rendering setting but I don't know of one. If your users are within your organisation you could do a custom install and remove the import data menu item.
Here's a sample I used to test this idea, https://sites.google.com/site/livecycledesignercookbooks/home/SecondDataSet.pdf?attredirects=0&d=1
The preview data for it looks like;
<formData>
<a>value a</a>
<b>value b</b>
<c>value c</c>
</formData>
Regards
Bruce