Schalk's evolutionary ramblings - All Comments

re: "Document checked out" workflow issue in SharePoint document library

schalkvanwyk — Tue, 08 Dec 2009 03:08:15 GMT

@steve

Sorry I can't help you, I've not work with that issue for a while. Maybe have a look at a ex-colleague of mine's blog: http://dotnet.org.za/zlatan

He's a MVP and might be able to suggest something.

re: "Document checked out" workflow issue in SharePoint document library

AKSteve — Tue, 08 Dec 2009 01:39:36 GMT

Hey, I hope someone is still monitoring this page. I have this issue and have switched from SharePoint Designer to VS2008. I have coded a simple workflow on a document library with the same goals 1-4 listed by the author, also set to start when the item is created. I do not want the users to have to kick off the workflow manually.

After the VS 2008 built workflow, I having the same issue as before with SP Designer. I got Microsoft Gold support ($260 hour) and the SP dev team involved. They could not figure it out either (and did not charge us $). I am going to continue to code my way out of it with delays and check-out checks etc. If anyone else has any time dedicate to this issue post it here or contact me at steve.fink@avtec.edu

re: SharePoint VSeWSS and feature dependency rules

SharePointVictim — Tue, 29 Sep 2009 16:53:46 GMT

I just tried to post a comment agreeing whole-heartedly, but was greeted with

"Oops something went wrong!

Either the site is offline or an unhandled error occurred. We apologize and have logged the error. Please try your request again or if you know who your site administrator is let them know too."

I guess that's what happens when you try to add comments to a blog based on Microsoft technology...

re: "Document checked out" workflow issue in SharePoint document library

Ruth Jennaway (UK) — Fri, 11 Sep 2009 15:22:40 GMT

I was having similar problems in a Sharepoint Designer workflow...

If the document is checked out and the workflow tries to update the fields then the workflow will get a status of stopped.

Adding a Wait for “Checked out to” field to be empty should work, however, it does not always seem to work. (Possibly due to this field being cleared whilst the checked out comments are still being written back? Not sure!).

Combining Wait for field change with Pause for 1 minute Action seems to be much more robust. (Although wait for 1 minute is actually wait for between 1 and 5 minutes).

works on my test system. Off to try it on live now.

re: "Document checked out" workflow issue in SharePoint document library

Bhavana — Fri, 10 Jul 2009 07:01:26 GMT

I was trying to fire an event handler on a doc library and it was giving me the same error when I saved a new document..

I used item.SystemUpdate() instead of item.Update() and it worked fine.............

re: "Document checked out" workflow issue in SharePoint document library

Denson Hamilton — Mon, 08 Jun 2009 14:34:19 GMT

I had issues with a custom workflow and the upload event in a document library.

I fixed this problem in a custom workflow.

I check the base type of the list.

If it is a document library I set the OnItemCreated to false. When the metadata is changed the changed event fires and normal processing of metadata begins. If your workflow works off of a column you need t make it required.

If you do multiple upload then you have to enter the metadata for each item then do a check in.

SPBaseType theBaseType = this._sharePointListAttachedTo.BaseType;

if (theBaseType == SPBaseType.DocumentLibrary)

{

this._paramAutoStartWF_OnItemCreate = false;

}

The upload starts the workflow before the metadata retrieval this is to allow for multiple document uploads as per Microsoft support.

re: SharePoint VSeWSS and feature dependency rules

Bill — Tue, 26 May 2009 21:03:05 GMT

"I've found most of my time spent on SharePoint development is not spent and designing the solution, but with the inconsistent xml definitions used in the features definitions"

Yes.

re: "Document checked out" workflow issue in SharePoint document library

schalkvanwyk — Tue, 07 Apr 2009 00:56:21 GMT

Sorry ozbromy, I found no solution and moved on, since the requirement has changed and there is no need to worry about the problem for now.

I am sure I will come across the issue again and will post a solution if I find it.

re: "Document checked out" workflow issue in SharePoint document library

ozbroomy@hotmail.com — Fri, 03 Apr 2009 05:39:01 GMT

I've got the same exect issue and it's drivingme nuts! Let me know if you find a solution - ozbromy@hotmail.com

re: Source Control with SubVersion (SVN)

schalkvanwyk — Wed, 18 Mar 2009 06:37:38 GMT

Yip, Charl

I find the user interface so much easier, more natural. And if you are having trouble in Visual Studio using Ankh, just switch to explorer and sort out the issue using Tortoise.

I think the best thing about SVN (compared to stupid Source Safe) is that you can easily get all the code related to a certain version, without going on a extensive hunt for it.

Branching and merging projects is also very easy, I found it to be a simple task after reading the documentation and trying it out.

re: Source Control with SubVersion (SVN)

charlv — Mon, 16 Mar 2009 10:36:55 GMT

I agree 100%, Subversion rocks! I have been using it for a while now and it beats SoureSafe hands down. I feel it is a very matured platform and widely used among open source developers.

The shell integration of TortoiseSVN is the best thing since sliced cheese :). It helps a lot when you have non source related content to keep under source control, i.e. documentation, scripts, etc.

re: A good starting point for SharePoint

schalkvanwyk — Wed, 25 Feb 2009 04:17:10 GMT

I also found the following video: OS304 - SharePoint Technology Tools, Techniques, References, and Resources for Visual Studio Developers (OS304_Isenhour.wmv) - download.microsoft.com/.../OS304_Isenhour.wmv

It's old but gives some basic background to developing with SharePoint.

re: A good starting point for SharePoint

schalkvanwyk — Wed, 25 Feb 2009 00:05:08 GMT

Zlatan, if I can learn from a expert like you, I would be over the moon (no sarcasm).

And I am NOT against SharePoint, to the contrary I think it will be great development platform. I just wish there was a easier way to get to know where and how one should use it and witch "features"/parts are for historic purposes and should be avoided.

I'm discovering loads about the platform on a daily basis (especially after reading Jeremy Thake blog), but that does not directly help me produce a solution to the current environment. I also want to make sure that what I develop is testable, as well as maintainable with as little user input as possible.

Sorry I never got a chance to see you (or any other buddies back there), time just was not on my side.

Unfortunately (or is that fortunately) I am not planning to go back to SA, unless something major happens that forces me that direction.

re: A good starting point for SharePoint

Zlatan — Tue, 24 Feb 2009 07:26:46 GMT

Umm Schalk you have got to see me next time you come back from Oz so we can sort most of your concerns. However some limitations exist, but I can show you how to live with them (I don't know how that sounds but I call it positive).

re: A good starting point for SharePoint

schalkvanwyk — Tue, 24 Feb 2009 05:43:16 GMT

I've downloaded and installed the newest VSeWSS package (VSeWSS v1.3 - Feb 2009 CTP) I could find on the Microsoft download site: www.microsoft.com/.../details.aspx

I see a couple of items has been added to the context menu for a SharePoint project (not workflow), as well as a couple of other UI features and VS templates.

One can read some more here: wss.made4the.net/.../the-ultimate-sharepoint-development-tool-and-the-new-release-of-vsewss-1-3-ctp-and-stsdev-2008-v2-0.aspx