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/89566.aspxTue, 07 May 2013 19:31:06 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:89566Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/89566.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=89566<p>&nbsp;Well, attach it to a reply&nbsp;(under the Options tab)&nbsp;if you want me to take a look - or email the form to Support AT Qdabra&nbsp;DOT com and reference this thread.&nbsp;The mapping itself shouldn&#39;t be preventing it from publishing as a browser form. If you have access to the SharePoint Logs, you can look at those for around the time you tried to publish and see if they reveal anything.</p>https://www.infopathdev.com:443/forums/thread/89565.aspxTue, 07 May 2013 19:23:54 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:89565chrisgee0https://www.infopathdev.com:443/forums/thread/89565.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=89565I think both are 4.3. The form is for SP2010. I was getting errors at first, concerning some filters I had set up. I removed the filters and the Design Checker lists no errors. However, when I try to publish I still get the message that the form has elements that can&#39;t be displayed in a browser. I run the Design Checker again and it still reports no errors. Honestly I may have messed around with things and thrown something off-kilter. It may be worth it to remap everything to see if that helps.https://www.infopathdev.com:443/forums/thread/89530.aspxMon, 06 May 2013 19:59:40 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:89530Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/89530.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=89530<p>&nbsp;You should not have to recreate the form, the mapping, or anything, you should be able to just re-inject. What version was the trial you were using? What version is the full version you are using? What version of SharePoint are you publishing to - 2010? Office 365? Are you publishing the same form to the same site? Thanks - sorry about all the questions!</p>https://www.infopathdev.com:443/forums/thread/89529.aspxMon, 06 May 2013 19:55:40 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:89529chrisgee0https://www.infopathdev.com:443/forums/thread/89529.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=131&PostID=89529I finally got the paid version of qRules but I&#39;m getting some weird errors in trying to deploy a form. I reinjected the form with the paid version of qRules, but I&#39;m now wondering, do I need to go through the &quot;Qdabra InfoPath to SharePoint List Tool&quot; and re-map everything using the new version? The error I&#39;m receiving happens when I try to publish as a web browser form, error reads: &quot;The form template has been published to the server but it can only be opened in the InfoPath Filler because it contains features that are not compatible with Web browsers. To fix this problem, close this dialog and review the errors in the Design Checker task pane.&quot; But when I run Design Checker it doesn&#39;t find any errors. Does anyone know why this would happen? I&#39;m planning to re-create the form completely using the paid software, but before I jump into that I wanted to see if there was a simple solution!