Challenge:
Create a form in InfoPath 2007 and implement a SharePoint Workflow to it for approval processes. In each step, a Status field in the InfoPat form should be updated automatically according to the change of workflow task status. So a different view in the InfoPath can be opened based on the Status field in the form.
But after the InfoPath was published to the SharePoint (MOSS 2007 with InfoPath Form Services turned on) as Document Library and Content type, the Status field could not be displayed when “Set Field value in Current item” action was selected in the workflow design. Even it was promoted to be available in the SharePoint document library.
Continue reading ‘How to pass InfoPath form fields to SharePoint workflow but hide from Document Library item properties’
Related posts
This post is an updated to the previous post of mine about the Task List item manipulations. Apparently the method I described in the previous post works only for different task lists, not for the sub-folders which belong to the same task list moved from.
When I tried to move the list items into a sub-folder inside the same task list on Manage Content and Structure page, and got the error below
“An error was encountered performing this operation.
Attempt to move url(s): http://site/Lists/Tasks/1_.000; failed. Please try again
Continue reading ‘[Updated] How to move task list item into sub-folders on sharepoint’
Related posts
Yesterday one user reported that when he tried to edit a Microsoft Project document that is stored in a document library of a Microsoft Windows SharePoint Services Web site, he received the following error messages with Office (Project) 2003 installed on his computer.
‘Edit Document’ requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater.
I found a Microsoft Knowledge base article and did what it told me to do by updating the SharePoint support, but could not be successful. Then I tried the method 3 to register the Owssupp.dll but get the following error.
DllUnregisterServer in Owssupp.dll failed….return Error code 0×80070716.
Continue reading ‘How to resolve “‘Edit Document’ requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater” error’
Related posts
Challenge:
When I was approached by a co-worker to come up a quick solution to design a training registration application. The requirement is to display all upcoming training events in calendar view and allow users to register to each training. And upon the registration is submitted, the training department and the user’s supervisor should receive notifications immediately (although not required now, but might need the approval from the supervisor in later development). The deadline is very…, how to say it, … how about this afternoon. Well, while the co-worker asked how to design the database tables and asp.net coding, I suggested why not giving the SharePoint a shot. Since I am the one proposed, then I had to create it for her.
Well, that was what I came up so far. In our Microsoft Office SharePoint Server System (MOSS) 2007 with Windows SharePoint Services 3.0 (WSS), I created a calendar list to display training events; in the calendar item there was a link to another new created survey list acting as a registration form. Then I added a workflow to the survey so that emails will be sent out whenever a new response is added into the survey (or register list).
Everything is working fine, but however, the workflow does not start. Instead, the status of the workflow appears as Failed to Start.
Trouble-Shootings:
I searched this issue on Google, and I found out a lot of people had the similar errors before. Someone pointed out the cause was the user of application pool who should be Network Services instead of a user with administrative right; Someone suggested to re-active the workflow feature in SharePoint Application server; Someone asked whether it was done in SharePoint Designer 2007.
Continue reading ‘Can not start a workflow from a survey response in Windows SharePoint Services 3.0 (MOSS 2007) with "Failed to Start" error’
Related posts
Blog Comments