https://www.infopathdev.com:443/forums/131.aspxqRules adds support to your InfoPath forms. With qRules, you can add features to your form that require code, but without having to write it. enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/73734.aspxTue, 10 Jan 2012 16:23:40 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:73734Jimmy0https://www.infopathdev.com:443/forums/thread/73734.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=73734<p>Hello,</p> <p>We do have this on our list of future enhancements, though I&#39;m not sure about the certainty that it will be included in the next version.&nbsp; We will certainly take your request into consideration when triaging this feature.</p> <p>One workaround you can use is create your own 2DS with a field called PerformCommand, give it a rule to set the qRules command field to the value of itself, and send all of your qRules commands there instead.&nbsp; That should essentially give you the behavior you are describing, with&nbsp;a few extra manual steps.</p>https://www.infopathdev.com:443/forums/thread/73725.aspxTue, 10 Jan 2012 15:35:55 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:73725Marzipan0https://www.infopathdev.com:443/forums/thread/73725.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=73725<p>Please consider adding the LastCommand field to the QdabraRules.xml SDS and having the program populate this field as an enhancement for the next version.</p> <p>I find this very useful for troubleshooting, having to manage&nbsp;this ourselves is tedious.</p> <p>Thanks&nbsp;</p> <p>&nbsp;</p>