Re: [OzMOSS] Debugging a Workflow with InfoPath forms

2007-12-19 Thread Jeremy Thake
Thanks Clayton. > "Luckily you can use the same form for your association and > initialisation. Change the workflow.xml Association_FormURN and > Instantiation_FormURN to use the same urn id." If I use the same form, what is the best approach to hide and show the relevant fields? ie. If it's

[OzMOSS] Elevated Permissions from Workflow

2007-12-19 Thread Chris Armstrong
Hi, I'm trying to get a workflow to self approve from within the workflow code using this SPSecurity.RunWithElevatedPriviledges(item.Update). It all works fine when the user is a member of Approvers but we need this user to be a contributor only. I've read that this works only in MOSS & not in

Re: [OzMOSS] You can't have a hidden feature with an activation dependency?

2007-12-19 Thread Bill Williamson
Thanks for the reply! That was the basis of Ishai's reply, which I would like to avoid as this feature otherwise has no code. It seems a bit crap that you'd have to add code for something as simple as a dependancy when dependancies are built into SP to begin with. On 12/20/07, Clayton James <[EM

RE: [OzMOSS] Help - sharepoint 2007 sp1 upgrade problems

2007-12-19 Thread Craig Stevens
The first thing I would try is creating a new site, and attaching one of the databases to it. I would also back up, and the restore a databasse, and sue that for trying to fix the problem ,rather than using a current content database Cheers Craig -Original Message- From: [EMAIL PROTECTED]

RE: [OzMOSS] Help - sharepoint 2007 sp1 upgrade problems

2007-12-19 Thread Peter Milliner
Any one have any ideas. All content seems to be there just not accessible because of versions in database table differ. I know this sounds simplistic but can I just add database version directly to table. Regards Peter M. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTE

RE: [OzMOSS] You can't have a hidden feature with an activation dependency?

2007-12-19 Thread Mark Daunt
Oops, so embarrassing! I didn't mean to send this to all of OzMoss sorry. You must agree though. Thanks a lot Clayton for being active on this list. I'm a bit biased though as we work together J From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Daunt Sent: Thursday, 20 Dec

RE: [OzMOSS] You can't have a hidden feature with an activation dependency?

2007-12-19 Thread Mark Daunt
Hi Clayton, You on fire with the OzMoss stuff. Good work! That's a really good thing to do to get visibility for MVP etc. Do you do anything with the news groups? Mark From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clayton James Sent: Thursday, 20 December 2007 1

RE: [OzMOSS] You can't have a hidden feature with an activation dependency?

2007-12-19 Thread Clayton James
Hi Bill You can create a feature receiver class that contains code when a feature gets: * Installed * Activated * DeActivated * UnInstalled You can do this by writing code in a class that inherits from SPFeatureReceiver base class and override the following methods

RE: [OzMOSS] Debugging a Workflow with InfoPath forms

2007-12-19 Thread Clayton James
Hi J Good to see you in moss land J Could not find schema information for element...sounds like your schemas are different. HYPERLINK "http://msdn2.microsoft.com/en-us/library/bb629921.aspx"http://msdn2.microsoft.com/en-us/library/bb629921.aspx The line below (which was copied from t

RE: [OzMOSS] FW: Sydney SharePoint User Group Xmas Drinks

2007-12-19 Thread Matt Lynch
Count me in for that. Cheers, Matt From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee Marriage Sent: Tuesday, 18 December 2007 11:47 AM To: listserver@ozmoss.com Subject: [OzMOSS] FW: Sydney SharePoint User Group Xmas Drinks I hope OzMoss don't mind me gate crashing

[OzMOSS] Help - sharepoint 2007 sp1 upgrade problems

2007-12-19 Thread Peter Milliner
Hello all, I have attempted to install moss sp1 upgrade but I am unable now to reach my main site, ssp site and mysites. I can access central administration site. This is the entry in the upgrade log file and is the error I recieve when I run the configuration wizard. Microsoft.SharePoint.U