<?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: 64-bit Infopath 2010 not triggering workflows in Sharepoint (WSS 3.0)</title><link>https://www.infopathdev.com:443/forums/thread/88340.aspx</link><pubDate>Sun, 24 Mar 2013 19:44:39 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:88340</guid><dc:creator>Patrick Halstead</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/88340.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=88340</wfw:commentRss><description>&lt;p&gt;Hi TiltnSpill,&lt;/p&gt;&lt;p&gt;The only way that this could be related to 64-bit InfoPath client would be if the output XML were different. Take a look at the XML forms generated in Notepad and see if you can figure out what the diference is. My hunch is that the 64-bit change is a red herring. Why? Well, there&amp;#39;s no connection from the client to the workflow. It&amp;#39;s just the XML data that the workflow is using. The workflow runs independently of the clients.&lt;/p&gt;&lt;p&gt;Hopefully, looking at the XML will explain why it&amp;#39;s happening. Certainly, I can&amp;#39;t imagine why 64-bit client would generate different XML. It should not. But, maybe there&amp;#39;s some related issue with logic in the form. &lt;/p&gt;&lt;p&gt;Good luck!&lt;/p&gt;</description></item><item><title>64-bit Infopath 2010 not triggering workflows in Sharepoint (WSS 3.0)</title><link>https://www.infopathdev.com:443/forums/thread/88258.aspx</link><pubDate>Thu, 21 Mar 2013 13:48:02 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:88258</guid><dc:creator>TiltnSpill</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/88258.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=88258</wfw:commentRss><description>&lt;p&gt;Good morning,&lt;/p&gt;
&lt;p&gt;We recently upgraded some users to Microsoft office 2010 (64-bit edition).&amp;nbsp; However, it appears that Infopath 2010 is not playing nice with Sharepoint. :(&lt;br /&gt;&lt;br /&gt;Example - I have an am &amp;nbsp;Infopath&amp;nbsp;form (2007 template) that is submitted to a Sharepoint form library.&amp;nbsp; I have a simple, out of the box workflow that&amp;nbsp;starts when a new item is added to the library.&amp;nbsp; There is only one condition on this workflow.&amp;nbsp; (If name of document&amp;nbsp;contains &amp;quot;Voucher&amp;quot;, email X department).&amp;nbsp;&amp;nbsp;&amp;nbsp; This form/workflow was built 3 years ago, and I haven&amp;#39;t had any problems with it until now.&amp;nbsp; After some initial troubleshooting, I found out forms sent from 64-bit Infopath 2010 weren&amp;#39;t triggering workflows properly!!&amp;nbsp; If simply skips the condition(s) set in the workflow and&amp;nbsp; the workflow shows as &amp;quot;completed&amp;quot; in Sharepoint.&amp;nbsp; These aren&amp;#39;t complex workflows at all, the condition is simply looking for a word in the title of the document.&amp;nbsp; If a user submits the same expense report from 32-bit Infopath 2010 or 2007, the condition of the workflow is met, and the email is sent to the department.&amp;nbsp; To make things more confusing, SOMETIMES it will work and follow the conditions.&amp;nbsp; I had a user test and submit 6 identical forms from 64-bit Infopath 2010.&amp;nbsp; THe workflow was triggered all 6 times, but only 3 times did it follow the conditions set by the workflow.&amp;nbsp; The other 3 times, it skipped the condition. I had the user repeat the same&amp;nbsp;test on a workstation that had 32-bit Infopath 2010, and all&amp;nbsp;6 times if followed the conditions set by the workflow.&lt;/p&gt;
&lt;p&gt;To summarize - Forms submitted from 64-bit Infopath 2010 will trigger workflows, but it doesn&amp;#39;t adhere to the&amp;nbsp;logic set in the workflow.&amp;nbsp; 50% of the time, It skips to the end of the workflow, and the workflow shows as completed.&lt;br /&gt;&lt;br /&gt;Any help in figuring out what&amp;#39;s going on would be greatly appreciated!&amp;nbsp; &lt;/p&gt;</description></item></channel></rss>