<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SharePoint Integration</title><link>https://www.infopathdev.com:443/forums/46.aspx</link><description> For questions concerning issues in the integration of SharePoint and Microsoft InfoPath.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Form only publishing in filler mode...</title><link>https://www.infopathdev.com:443/forums/thread/105162.aspx</link><pubDate>Fri, 15 Jan 2016 17:51:12 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:105162</guid><dc:creator>Hilary Stoupa</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/105162.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=105162</wfw:commentRss><description>&lt;p&gt;&amp;nbsp;Hi, Catharine, Happy New Year!&lt;/p&gt;&lt;p&gt;When you get this in Design Checker, it usually means &amp;quot;This won&amp;#39;t&amp;nbsp;publish as a browser form&amp;quot;. :)&lt;/p&gt;&lt;p&gt;&amp;nbsp;Here is what I usually do. I make a copy of the form to tear down. I then create a new blank view, and remove all other views one at a time, running design checker after each change. This lets me narrow the issue - if it is something in the view, the design checker will return its usual list of warnings instead of &amp;quot;could not verify&amp;quot;.&lt;/p&gt;&lt;p&gt;If, with all views except a new blank view&amp;nbsp;removed,&amp;nbsp;I still get that message from design checker, I start removing rules, usually in batches, keeping track of what I&amp;#39;ve removed, and running design checker.&amp;nbsp;The last time I did this, the issue was a rule condition where&amp;nbsp;a group had been selected with the condition&amp;nbsp;&amp;quot;is blank&amp;quot; - IPFS did NOT like that.&lt;/p&gt;&lt;p&gt;If the issue is a view, I usually create a new copy of the form&amp;nbsp;and remove&amp;nbsp;parts of the view, running design checker as I&amp;nbsp;go - again to narrow the issue down.&lt;/p&gt;&lt;p&gt;Hope that helps -&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Form only publishing in filler mode...</title><link>https://www.infopathdev.com:443/forums/thread/105161.aspx</link><pubDate>Fri, 15 Jan 2016 17:31:14 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:105161</guid><dc:creator>Catharine</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/105161.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=105161</wfw:commentRss><description>&lt;p&gt;Hi&lt;/p&gt;&lt;p&gt;I am using SharePoint 2010.&amp;nbsp; I have a form which is pointing to an external list in SharePoint.&lt;/p&gt;&lt;p&gt;It has been working fine.&amp;nbsp; &lt;/p&gt;&lt;p&gt;I have now&amp;nbsp;had to change&amp;nbsp;the form -&amp;nbsp;to display&amp;nbsp;one extra field on the&amp;nbsp;form (it was already in the data source so), and to change 3 calculations so they include that field&lt;/p&gt;&lt;p&gt;I have republished and&amp;nbsp;get the warning&lt;/p&gt;&lt;p&gt;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.&amp;nbsp; To fix this problem, close the dialog and review the errors in the Designer Checker task pane.&lt;/p&gt;&lt;p&gt;There are no errors in the design checker - but it does say &amp;quot;Could not verify the form template on the specified server&amp;quot;&lt;/p&gt;&lt;p&gt;I have tried from a machine running office 2013 and a machine running office 2010&amp;nbsp; slightly different errors in each case.&lt;/p&gt;&lt;p&gt;Any ideas ?&amp;nbsp;&lt;/p&gt;&lt;p&gt;Jim did help me with&amp;nbsp;a very similar issue before&amp;nbsp;Christmas - and I thought we had fixed it - but obviously not....&lt;/p&gt;&lt;p&gt;Catharine&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>