RE: Multiline field - parse error with hidden paragraph character
OK. I have resolved this problem by replacing NewLine with br/ elements before updating the Note field. I have also had to reverse this when retrieving the Note field's contents and rendering them in the TextBox because the br/s are being literally returned. So much for Plain Text. :) Could I avoid all this by using a SharePoint NoteField in my custom control instead of a standard asp textbox? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Wednesday, 18 January 2012 2:40 PM To: ozMOSS (ozmoss@ozmoss.com) Subject: Multiline field - parse error with hidden paragraph character Hi all, I'm trying to update a multiline (plain) text field from a custom control that uses an ASP TextBox. Everything works fin until the user includes a carriage return in the entry. From experience, SQL usually handles this automatically but it seems SharePoint wants to convert these special characters first. Is this expected behaviour, or does anyone know a standard method to cleanse the text first? e.g. Replace(MyColumn,char(13),'\r\n') Kind regards, Paul Noone --- Online Developer/SharePoint Administrator Infrastructure Team, ICT Catholic Education Office, Sydney p: (02) 9568 8461 f: (02) 9568 8483 e: paul.no...@ceosyd.catholic.edu.aumailto:paul.no...@ceosyd.catholic.edu.au w: http://www.ceosyd.catholic.edu.au/ ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Doing a SharePoint caveats talk soon - send me your good'uns
Hi all Michal Pisarek and I are doing a talk in March about various SharePoint caveats. The audience is not really tech, but the purpose of the talk is to save people the pain of proceeding on an untested assumption and then finding out far too late that the logical edifice they have built has come crashing down. But it seems that there are around 2-3 common gotchas with most SharePoint components - and the newer the component the more the gotchas. Some of the big ones people know about are things like managed metadata support for InfoPath/SharePoint workspace. So if you have any caveats that has nailed you, would you mind sharing them with this list or mailing them to me? I'm sure each of us has a couple of good ones :) What's the biggest issue/caveat that's nailed you? Regards Paul ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Doing a SharePoint caveats talk soon - send me your good'uns
Undocking the ribbon? :) From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Thursday, 19 January 2012 12:33 PM To: ozMOSS Subject: Doing a SharePoint caveats talk soon - send me your good'uns Hi all Michal Pisarek and I are doing a talk in March about various SharePoint caveats. The audience is not really tech, but the purpose of the talk is to save people the pain of proceeding on an untested assumption and then finding out far too late that the logical edifice they have built has come crashing down. But it seems that there are around 2-3 common gotchas with most SharePoint components - and the newer the component the more the gotchas. Some of the big ones people know about are things like managed metadata support for InfoPath/SharePoint workspace. So if you have any caveats that has nailed you, would you mind sharing them with this list or mailing them to me? I'm sure each of us has a couple of good ones :) What's the biggest issue/caveat that's nailed you? Regards Paul ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Doing a SharePoint caveats talk soon - send me your good'uns
Thanks guys Remember I have to frame this to a business audience. What was the context around the ribbon issue? Was it simply to address branding requirement? Regards Paul From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Hertz Sent: Thursday, 19 January 2012 9:52 AM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Oh hell yes. +1 to the ribbon. I'd say the biggest issue I had was when doing a database attach upgrade from 2007 to 2010, and having the installation somehow maintaining references to the page layouts on the old server. It happened 4 out of 5 times. I had to go in, export the file default.aspx file, modify it, and re-import it for it to work correctly. From: ozmoss-boun...@ozmoss.commailto:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com]mailto:[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Thursday, 19 January 2012 12:43 PM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Undocking the ribbon? :) From: ozmoss-boun...@ozmoss.commailto:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com]mailto:[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Thursday, 19 January 2012 12:33 PM To: ozMOSS Subject: Doing a SharePoint caveats talk soon - send me your good'uns Hi all Michal Pisarek and I are doing a talk in March about various SharePoint caveats. The audience is not really tech, but the purpose of the talk is to save people the pain of proceeding on an untested assumption and then finding out far too late that the logical edifice they have built has come crashing down. But it seems that there are around 2-3 common gotchas with most SharePoint components - and the newer the component the more the gotchas. Some of the big ones people know about are things like managed metadata support for InfoPath/SharePoint workspace. So if you have any caveats that has nailed you, would you mind sharing them with this list or mailing them to me? I'm sure each of us has a couple of good ones :) What's the biggest issue/caveat that's nailed you? Regards Paul Stockland Notice: If this communication has been sent to you by mistake, please delete and notify us. If it has been sent to you by mistake, legal privilege is not waived or lost and you are not entitled to use it in any way. Stockland and its subsidiaries reserve the right to monitor e-mail communication through its networks. ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Doing a SharePoint caveats talk soon - send me your good'uns
User Profile - issues around who can update data in there (just user, user and admin, etc), chance of losing that data if need to rebuild (backup those databases!!) - its better then in 2007, but still a little flaky (imho) Content Type hub - understanding what gets published with the content type (in terms of receivers, workflow association not workflow itself, etc.), that CTs are readonly in subscribing site colls. The problems associated with changeing content types after they are in use (esp removing columns) MMS is good - everyone seems a little suprised to find it is not well supported in infopath. Not able to break the inheritance of content types information policies - i.e. all children ct's must inherit the imp from parent, and this cant be broken. From: nigel.he...@stockland.com.au To: ozmoss@ozmoss.com Date: Thu, 19 Jan 2012 12:51:37 +1100 Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Oh hell yes. +1 to the ribbon. I’d say the biggest issue I had was when doing a database attach upgrade from 2007 to 2010, and having the installation somehow maintaining references to the page layouts on the old server. It happened 4 out of 5 times. I had to go in, export the file default.aspx file, modify it, and re-import it for it to work correctly. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Thursday, 19 January 2012 12:43 PM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Undocking the ribbon? J From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Thursday, 19 January 2012 12:33 PM To: ozMOSS Subject: Doing a SharePoint caveats talk soon - send me your good'uns Hi all Michal Pisarek and I are doing a talk in March about various SharePoint caveats. The audience is not really tech, but the purpose of the talk is to save people the pain of proceeding on an untested assumption and then finding out far too late that the logical edifice they have built has come crashing down. But it seems that there are around 2-3 common gotchas with most SharePoint components – and the newer the component the more the gotchas. Some of the big ones people know about are things like managed metadata support for InfoPath/SharePoint workspace. So if you have any caveats that has nailed you, would you mind sharing them with this list or mailing them to me? I’m sure each of us has a couple of good ones J What’s the biggest issue/caveat that’s nailed you? Regards Paul Stockland Notice: If this communication has been sent to you by mistake, please delete and notify us. If it has been sent to you by mistake, legal privilege is not waived or lost and you are not entitled to use it in any way. Stockland and its subsidiaries reserve the right to monitor e-mail communication through its networks. ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Doing a SharePoint caveats talk soon - send me your good'uns
that should have read more than a little suprised From: nigel_wither...@hotmail.com To: ozmoss@ozmoss.com Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Date: Thu, 19 Jan 2012 02:21:21 + User Profile - issues around who can update data in there (just user, user and admin, etc), chance of losing that data if need to rebuild (backup those databases!!) - its better then in 2007, but still a little flaky (imho) Content Type hub - understanding what gets published with the content type (in terms of receivers, workflow association not workflow itself, etc.), that CTs are readonly in subscribing site colls. The problems associated with changeing content types after they are in use (esp removing columns) MMS is good - everyone seems a little suprised to find it is not well supported in infopath. Not able to break the inheritance of content types information policies - i.e. all children ct's must inherit the imp from parent, and this cant be broken. From: nigel.he...@stockland.com.au To: ozmoss@ozmoss.com Date: Thu, 19 Jan 2012 12:51:37 +1100 Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Oh hell yes. +1 to the ribbon. I’d say the biggest issue I had was when doing a database attach upgrade from 2007 to 2010, and having the installation somehow maintaining references to the page layouts on the old server. It happened 4 out of 5 times. I had to go in, export the file default.aspx file, modify it, and re-import it for it to work correctly. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Thursday, 19 January 2012 12:43 PM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Undocking the ribbon? J From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Thursday, 19 January 2012 12:33 PM To: ozMOSS Subject: Doing a SharePoint caveats talk soon - send me your good'uns Hi all Michal Pisarek and I are doing a talk in March about various SharePoint caveats. The audience is not really tech, but the purpose of the talk is to save people the pain of proceeding on an untested assumption and then finding out far too late that the logical edifice they have built has come crashing down. But it seems that there are around 2-3 common gotchas with most SharePoint components – and the newer the component the more the gotchas. Some of the big ones people know about are things like managed metadata support for InfoPath/SharePoint workspace. So if you have any caveats that has nailed you, would you mind sharing them with this list or mailing them to me? I’m sure each of us has a couple of good ones J What’s the biggest issue/caveat that’s nailed you? Regards Paul Stockland Notice: If this communication has been sent to you by mistake, please delete and notify us. If it has been sent to you by mistake, legal privilege is not waived or lost and you are not entitled to use it in any way. Stockland and its subsidiaries reserve the right to monitor e-mail communication through its networks. ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Doing a SharePoint caveats talk soon - send me your good'uns
Branding and usability. We finally accepted defeat. The sheer amount of JavaScript required (and the associated side-effects) simply made it untenable. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Thursday, 19 January 2012 1:03 PM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Thanks guys Remember I have to frame this to a business audience. What was the context around the ribbon issue? Was it simply to address branding requirement? Regards Paul From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Hertz Sent: Thursday, 19 January 2012 9:52 AM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Oh hell yes. +1 to the ribbon. I'd say the biggest issue I had was when doing a database attach upgrade from 2007 to 2010, and having the installation somehow maintaining references to the page layouts on the old server. It happened 4 out of 5 times. I had to go in, export the file default.aspx file, modify it, and re-import it for it to work correctly. From: ozmoss-boun...@ozmoss.commailto:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com]mailto:[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Thursday, 19 January 2012 12:43 PM To: ozMOSS Subject: RE: Doing a SharePoint caveats talk soon - send me your good'uns Undocking the ribbon? :) From: ozmoss-boun...@ozmoss.commailto:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com]mailto:[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Thursday, 19 January 2012 12:33 PM To: ozMOSS Subject: Doing a SharePoint caveats talk soon - send me your good'uns Hi all Michal Pisarek and I are doing a talk in March about various SharePoint caveats. The audience is not really tech, but the purpose of the talk is to save people the pain of proceeding on an untested assumption and then finding out far too late that the logical edifice they have built has come crashing down. But it seems that there are around 2-3 common gotchas with most SharePoint components - and the newer the component the more the gotchas. Some of the big ones people know about are things like managed metadata support for InfoPath/SharePoint workspace. So if you have any caveats that has nailed you, would you mind sharing them with this list or mailing them to me? I'm sure each of us has a couple of good ones :) What's the biggest issue/caveat that's nailed you? Regards Paul Stockland Notice: If this communication has been sent to you by mistake, please delete and notify us. If it has been sent to you by mistake, legal privilege is not waived or lost and you are not entitled to use it in any way. Stockland and its subsidiaries reserve the right to monitor e-mail communication through its networks. ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
content approval
Hi guys, I have a library with content approval turned on, and a approval workflow that runs when a major version is published. I upload a document, version 0.1, I check it out, and then check it in, selecting version 1.0. SharePoint saves it has 0.2 instead of 1.0, which I understand is normal until its approved, but the workflow doesn't fire. If I check the document in, using the browser I get the workflow start form, and it starts properly. Although ideally I don't want them to have to click Start, or be able to edit those options either. Chris Grist MCITP, MCPD, MCTS, VCP, CCA Senior Technical Consultant Description: Description: Description: email-logo Ground Floor 175 Fullarton Rd Dulwich SA 5065 Tel (08) 8304 Fax (08) 8364 2910 Description: Description: Description: partnerbar-email NOTE: This email and any files transmitted with it are confidential and may contain information intended only for the addressee(s). If you have received this communication in error, you must not copy or distribute any part of it or otherwise disclose its contents to anyone - please notify Loftus IT immediately. Loftus IT does not accept liability for any errors or omissions in the information provided herein. No representation is made that email and any files transmitted with it are virus-free - virus scanning is the responsibility of the recipient and is recommended. image001.pngimage003.gifimage004.gif___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
