As recommended by Microsoft, lock the xsl if you are modifying it manually, ok, this is what we did, we used the support article, and this command
<xsl:apply-templates select="." mode="xd:preserve"/>
And today we found that the check boxes are losing their binding if we use that command
Today I am mad, it is Saturday, and instead taking the day off, I am working to find a workaround for this problem.
At the beginning of this year, I was a fan of Microsoft, I was developing software using SQL, VS and VS.NET for years, yes there are some small bugs there but not a big deal; but since I started using BizTalk 2004, and InfoPath 2003, I am just starting to hate this company.
Congratulation, here is the winner of this year's less tested software, (2004), BizTalk (which I dumped 4 month ago), and InfoPath (which if it was up to me I would have dumped long time ago).
But since I am stuck with this software, please fix it the next release, make it developer friendly
Matthew Blain \(Serriform\) - 30 Oct 2004 22:49 GMT
What do you mean, the checkboxes are losing their binding? They should work fine. The only bug I've run into with xd:preserve is that the designer will sometimes re-write the XML and lose some of your changes, specifically things like comments, and also certain elements (input) sometimes need to be expressed using xsl:element instead of <input>. I've never seen an issue with the runtime.
Perhaps you're running in to the input tag being re-written? Look at the XSL and see if you have xsl:attribute tags in the 'wrong' place, and if so switch the input tag to an xsl:element tag.
--Matthew Blain
http://tips.serriform.com/
http://www.developingsolutionswithinfopath.com
As recommended by Microsoft, lock the xsl if you are modifying it manually, ok, this is what we did, we used the support article, and this command
<xsl:apply-templates select="." mode="xd:preserve"/>
And today we found that the check boxes are losing their binding if we use that command
Today I am mad, it is Saturday, and instead taking the day off, I am working to find a workaround for this problem.
At the beginning of this year, I was a fan of Microsoft, I was developing software using SQL, VS and VS.NET for years, yes there are some small bugs there but not a big deal; but since I started using BizTalk 2004, and InfoPath 2003, I am just starting to hate this company.
Congratulation, here is the winner of this year's less tested software, (2004), BizTalk (which I dumped 4 month ago), and InfoPath (which if it was up to me I would have dumped long time ago).
But since I am stuck with this software, please fix it the next release, make it developer friendly