sharepoint 2010 cumulative updates April vs February
Has anyone experience any issu with the April CU updates for sharepoint 2010 or would you recomment to stick with Februaryupdates. We normaly try to go for N-1 but by the time this will be in production the new updates will most likiely be released thanks for your response in advance -- ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Filter view on current year
Hi all, I have the following two fields which both return a singe line of text. *Name Type Value * Year Single line of text 2013 CurrYear Calculated (Text) TEXT(Today,) As u can see in the list view both display the same value. [image: Inline images 1] Yet when I try to filter the view using *Year = CurrYear* I get no results. Any ideas?? Regards, Paul image.png___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: sharepoint 2010 cumulative updates April vs February
There is a HUGE issue with any CU which includes KB2687418. March and April CU have it. It completely breaks managed metadata on any published item, including the OOTB enterprise wiki. It also gives all published pages an invalid security validation. We have a sev 1 PSS call open about it. On 10/05/2013 7:40 AM, Marc Sally Seydel ms.sey...@gmail.com wrote: Has anyone experience any issu with the April CU updates for sharepoint 2010 or would you recomment to stick with Februaryupdates. We normaly try to go for N-1 but by the time this will be in production the new updates will most likiely be released thanks for your response in advance -- ___ 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
Word Custom Properties Character Limitation
Hi All, We are using SharePoint 2010, and have a Document Set which has a large number of shared fields, some of which are multiple lines of text. Some of the allowed content types for the document set use Word document templates, which then use quick parts to display the metadata properties pushed down from the document set in the content of the document. We have experienced a problem lately where Word hangs attempting open documents on the splash screen showing Processing... A lot of digging around has shown (I think) that Word custom properties have a character limit of 255 char (similar complaints are here: http://social.msdn.microsoft.com/Forums/en-US/worddev/thread/fb885674-dc8c-4c0a-9202-374adbf11612/ and here: https://forum.solidworks.com/message/282519#282519). Testing of the documents that hang in our environment has proven this out - the problem docs all have fields with content 255 chars, shrinking it down makes them open correctly. The users are going to pitch a blue fit if we try and limit them to 255 chars for these fields! Just wondering if anyone else has experienced this, and has any possible resolution/work around. My possible solutions are:- Whinge at MS (can't see any joy coming from this approach)- Use multiple fields limited to 255 chars (this would involve a lot of work re-doing the SharePoint forms, document templates, plus a nasty script to split the existing 255char content into the new fields)- Switch from using Word documents to web pages, display the field content much like a publishing page (I like this approach, but as it is going to require a bit of dev time to might be a hard sell) Any ideas? Cheers, Nigel ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: Word Custom Properties Character Limitation
Hi Nigel, We had the same issue with an Annual Report project and wound up using InfoPath and Reporting Services to produce the final PDF. I feel your pain. Regards, Paul Noone SharePoint Farm Admin/Developer Infrastructure Team CEO Sydney p: (02) 9568 8461 f: (02) 9568 8483 e: paul.no...@syd.catholic.edu.au w: http://www.ceosyd.catholic.edu.au/ On 10 May 2013 10:35, Nigel Witherdin nigel_wither...@hotmail.com wrote: Hi All, We are using SharePoint 2010, and have a Document Set which has a large number of shared fields, some of which are multiple lines of text. Some of the allowed content types for the document set use Word document templates, which then use quick parts to display the metadata properties pushed down from the document set in the content of the document. We have experienced a problem lately where Word hangs attempting open documents on the splash screen showing Processing... A lot of digging around has shown (I think) that Word custom properties have a character limit of 255 char (similar complaints are here: http://social.msdn.microsoft.com/Forums/en-US/worddev/thread/fb885674-dc8c-4c0a-9202-374adbf11612/ and here: https://forum.solidworks.com/message/282519#282519). Testing of the documents that hang in our environment has proven this out - the problem docs all have fields with content 255 chars, shrinking it down makes them open correctly. The users are going to pitch a blue fit if we try and limit them to 255 chars for these fields! Just wondering if anyone else has experienced this, and has any possible resolution/work around. My possible solutions are: - Whinge at MS (can't see any joy coming from this approach) - Use multiple fields limited to 255 chars (this would involve a lot of work re-doing the SharePoint forms, document templates, plus a nasty script to split the existing 255char content into the new fields) - Switch from using Word documents to web pages, display the field content much like a publishing page (I like this approach, but as it is going to require a bit of dev time to might be a hard sell) Any ideas? Cheers, Nigel ___ 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: Word Custom Properties Character Limitation
Can you use the column setting Allow unlimited length in document libraries? This is available on the Multiple Lines of Text column type under the Additional Column Settings section. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Witherdin Sent: Friday, 10 May 2013 10:35 AM To: OzMoss Subject: Word Custom Properties Character Limitation Hi All, We are using SharePoint 2010, and have a Document Set which has a large number of shared fields, some of which are multiple lines of text. Some of the allowed content types for the document set use Word document templates, which then use quick parts to display the metadata properties pushed down from the document set in the content of the document. We have experienced a problem lately where Word hangs attempting open documents on the splash screen showing Processing... A lot of digging around has shown (I think) that Word custom properties have a character limit of 255 char (similar complaints are here: http://social.msdn.microsoft.com/Forums/en-US/worddev/thread/fb885674-dc8c-4c0a-9202-374adbf11612/ and here: https://forum.solidworks.com/message/282519#282519). Testing of the documents that hang in our environment has proven this out - the problem docs all have fields with content 255 chars, shrinking it down makes them open correctly. The users are going to pitch a blue fit if we try and limit them to 255 chars for these fields! Just wondering if anyone else has experienced this, and has any possible resolution/work around. My possible solutions are: - Whinge at MS (can't see any joy coming from this approach) - Use multiple fields limited to 255 chars (this would involve a lot of work re-doing the SharePoint forms, document templates, plus a nasty script to split the existing 255char content into the new fields) - Switch from using Word documents to web pages, display the field content much like a publishing page (I like this approach, but as it is going to require a bit of dev time to might be a hard sell) Any ideas? Cheers, Nigel ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: Word Custom Properties Character Limitation
It's a Quick Parts limitation in Word, not a SharePoint field issue. Regards, Paul Noone SharePoint Farm Admin/Developer Infrastructure Team CEO Sydney p: (02) 9568 8461 f: (02) 9568 8483 e: paul.no...@syd.catholic.edu.au w: http://www.ceosyd.catholic.edu.au/ On 10 May 2013 12:29, Ivan Wilson iv...@sharepointgurus.net wrote: Can you use the column setting “Allow unlimited length in document libraries”? This is available on the “Multiple Lines of Text” column type under the “Additional Column Settings” section. ** ** *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On Behalf Of *Nigel Witherdin *Sent:* Friday, 10 May 2013 10:35 AM *To:* OzMoss *Subject:* Word Custom Properties Character Limitation ** ** Hi All, ** ** We are using SharePoint 2010, and have a Document Set which has a large number of shared fields, some of which are multiple lines of text. ** ** Some of the allowed content types for the document set use Word document templates, which then use quick parts to display the metadata properties pushed down from the document set in the content of the document. ** ** We have experienced a problem lately where Word hangs attempting open documents on the splash screen showing Processing... ** ** A lot of digging around has shown (I think) that Word custom properties have a character limit of 255 char (similar complaints are here: http://social.msdn.microsoft.com/Forums/en-US/worddev/thread/fb885674-dc8c-4c0a-9202-374adbf11612/ and here: https://forum.solidworks.com/message/282519#282519). ** ** Testing of the documents that hang in our environment has proven this out - the problem docs all have fields with content 255 chars, shrinking it down makes them open correctly. ** ** The users are going to pitch a blue fit if we try and limit them to 255 chars for these fields! ** ** Just wondering if anyone else has experienced this, and has any possible resolution/work around. My possible solutions are: - Whinge at MS (can't see any joy coming from this approach) - Use multiple fields limited to 255 chars (this would involve a lot of work re-doing the SharePoint forms, document templates, plus a nasty script to split the existing 255char content into the new fields) - Switch from using Word documents to web pages, display the field content much like a publishing page (I like this approach, but as it is going to require a bit of dev time to might be a hard sell) ** ** Any ideas? ** ** Cheers, ** ** Nigel ** ** ___ 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
