-
Hi Drummer_Dre,
Here are a couple links to XML Template Parts that we have recently created for worklog history:
http://www.infopathdev.com/ControlPanel/Files/FileEditor.aspx?SectionID=130&PostID=60774
http://www.infopathdev.com/ControlPanel/Files/FileEditor.aspx?SectionID=130&PostID=60775
To automatically add rows or set fields in ...
-
This XML Template Part can easily be added to your form to give it a "history section" or a log of changes to your form. Works with InfoPath 2007.
-
This XML Template Part can be added to your 2010 InfoPath form to allow you to add submit-level change-tracking to your form.
-
You are not crazy and this will work and it's a best practice.
Mel created a detailed blog describing how to set this up over a year ago:
http://www.infopathdev.com/blogs/mel_balsamo/archive/2009/05/18/using-e-mail-forms-to-communicate-with-external-users.aspx
-
Jimmy reminded me that:
Preserve blocks aren’t allowed in Browser-enabled forms. That’s probably what datvt is working with. http://vspug.com/ssa/2008/11/09/preserve-code-blocks-are-not-supported-in-browser-enabled-infopath-forms/
Sorry about the confusion!
-
That's quite an interesting theory. I should contact Microsoft and ask them about it.
-
-
I don't understand. You say "when public the form it is not allow" - what do you mean? That English makes no sense. Do you mean "when publishing the form, xdPreserve is not allowed"? If so, that's not true. xdPreserve is just an element in the xsl and it can be used for all forms. I need more details.
-
If you're hacking the XSL, you should use xdPreserve to allow roundtrips.
-
xdExtension has nothing to do with the XSLT. You add it to the condition of the rule to allow you to call code.