I was having a strange issue when adding a DataView / DataForm webpart into a webpart zone whereby it was being rendered correctly on the first page visit but then any page interactions including post-backs would cause all of the properties to be wiped. A symptom of this was the message above (“An error occurred processing the data view. The XslText property is empty.”) which was caused by both the XSL and XslLink properties being cleared, but was obviously not the root cause. The only other clue I was getting was an error about “An error occurred while parsing EntityName. Line X, Position Y”. This led me to believe it was a problem with the DataView transforming the XML via the XSL template.
After much investigation and comparing the erroneous webpart to a working one, I found that the issue is caused when you have a column / field in the DataFields element of the DataView with an ampersand (&) character - even though it is escaped properly e.g.
<property name=”DataFields” type=”string”>@ID,ID;@ContentType,Content Type; … @ThisAndThat, This & That; … </property>
Changing the above line to :
<property name=”DataFields” type=”string”>@ID,ID;@ContentType,Content Type; … @ThisAndThat, This and That; … </property>
cured the problem. If you still want the ampersand displayed in the form, then you need to change it in the xsl directly. Obviously ampersands are not supported in the column display name of the datasources element, which seems amazing that I haven’t encountered this before.