Search - InfoPath Dev Sign in | Join | Help InfoPath Dev InfoPath Dev is dedicated to bringing you the information and tools you need to be successful in your Microsoft Office InfoPath development projects. Home Blogs Forums Photos Downloads Search More Search Options Page 7 of 14 (131 items) « First ... < Previous 5 6 7 8 9 Next > ... Last » Initial submit to DBXL linked to SharePoint doc library Is there a setting I'm missing that submits a form linked to a SharePoint 2010 document library as the current user? With my current solution, it's submitting as System Account instead of the current user. This is causing all kinds of problems with workflow. Please advise and thanks. Posted to Qdabra Database Accelerator (Forum) by TomRenfro on 08-14-2013 Re: Workflow stuck in Starting state Ok, here's what I'm observing. The content type form is published to DBXL and is mapped to SharePoint, using different expressions on what library to post the form. The initial submit goes to a library called AdditionApprovals. When the first form is filled out, the Modified by column on the library shows "System ... Posted to Workflow (Forum) by TomRenfro on 08-14-2013 Re: Workflow stuck in Starting state No I created it under my credentials. And it's working as is on other libraries as intended. I'm currently testing deleting the library, creating again with the same name, and adding the same workflow. I'll let you know what happens. Posted to Workflow (Forum) by TomRenfro on 08-14-2013 Re: Workflow stuck in Starting state Ok, an update. I found a blog post regarding stuck workflows in SharePoint, which were related to a hotfix applied a few months back. Basically, items created with system accounts won't start automatically without changing a workflow property on the server. A stsadm command needs to be executed on the server as such: stsadm ... Posted to Workflow (Forum) by TomRenfro on 08-14-2013 Workflow stuck in Starting state Hi, I've developed a reusable workflow in SharePoint Designer 2010 with the intent of using it with a specific InfoPath 2010 form content type. When I bind the workflow to different libraries for new items or changed items, it starts successfully except one library. Every new iteration of a form for this solution submits to an ... Posted to Workflow (Forum) by TomRenfro on 08-13-2013 Re: Sharepoint workflow question But does the modification of that column via another workflow trigger the desired workflow? Posted to SharePoint Integration (Forum) by TomRenfro on 07-31-2013 Sharepoint workflow question Hopefully I can get a quick answer on this. If I have a SharePoint Designer workflow that changes a value in the current item, for this purpose the current form that the workflow is running against, does that modification mark the xml in the form library as changed? What I'm trying to determine is if I have a workflow that pauses on a ... Posted to SharePoint Integration (Forum) by TomRenfro on 07-31-2013 re: qRules SubmitToSharePointList - Walkthrough for v4.2 Hi Hilary, I followed the blog completely, and I get "Failed to generate new Batch from mapping". I'm using version 4.3 of qRules. Any ideas? Posted to Hilary Stoupa (Weblog) by TomRenfro on 07-10-2013 Re: Promoted columns not showing data when changing form to content type Anybody have any wisdom on this subject? There seems to be a myriad of opinions on the net and I'm really stuck and need to get this solved. Posted to SharePoint Integration (Forum) by TomRenfro on 06-26-2013 Promoted columns not showing data when changing form to content type Hi, I'm hoping there's a quick answer to this. I've recently changed a form library from using directly published forms to content types, primarily so I don't clobber existing forms and its data in the library already. I've noticed that none of the data shows in the library for the newly published content type ... Posted to SharePoint Integration (Forum) by TomRenfro on 06-25-2013 Page 7 of 14 (131 items) « First ... < Previous 5 6 7 8 9 Next > ... Last » Copyright © 2003-2019 Qdabra Software. All rights reserved.View our Terms of Use.