ARGH!! Actually, it is still chopping it off at 255 characters - just not giving me an error any more!! Bit more googling, and it seems like I will have to cut my code up so that I implement the treeview control (inheriting from from BaseFieldControl) in one class, and then write a seperate class to implement the actual field. This class will inherit from SPFieldMultiLineText (which will then get around the 255 character limit, and in it I will have to override the FieldRenderingControl property so that it uses my treeview control. Will get on to it shortly - right now I need to go lie in cool, dark place for a little while.... Nigel Witherdin Senior Support Analyst Eversheds Direct Dial: +44 (0) 84 549 754 17 Mobile: +44 (0) 7738 553256 www.eversheds.com <http://www.eversheds.com/>
________________________________ From: Witherdin, Nigel Sent: 08 May 2008 09:58 Subject: RE: [OzMOSS] Custom Field Type - 255 char limit Actually - figured this out (with the help of Google -- which I probably should have done before emailing the list :) In the custom FieldType xml (FLDTYPES_<name>.XML), you should set the ParentType to be "Note" - i.e. <Field Name="ParentType">Note</Field> Cheers All - Nigel Witherdin Senior Support Analyst Eversheds Direct Dial: +44 (0) 84 549 754 17 Mobile: +44 (0) 7738 553256 www.eversheds.com <http://www.eversheds.com/> ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Witherdin, Nigel Sent: 07 May 2008 10:40 To: [email protected] Subject: [OzMOSS] Custom Field Type - 255 char limit Hi All, Have written a TreeView control as a custom field type (extends the "BaseFieldType" class), that then stores the node path for selected items as a ; seperated string in the list item (e.g. "NodeName\SubNode\LeafNode; AnotherNodeName\AnotherSubNode\AnotherLeafNode"). My problem is that the value that can be stored for the control seems to have a 255 character limit - which can be hit quite quickly if you have a tree that has a few levels. I guess I could change the control so that it stores node IDs rather then the node path, but I quite like the flexibility inherit in storing the node path. A far better solution would be to be able to extend the amount of characters I can store - but I have no idea how I would go about doing this. Any ideas?? Cheers, Nigel Witherdin Senior Support Analyst Eversheds Direct Dial: +44 (0) 84 549 754 17 Mobile: +44 (0) 7738 553256 www.eversheds.com <http://www.eversheds.com/> ********* This email is sent for and on behalf of Eversheds LLP ********* >From 12 May 2008, our new London headquarters will be One Wood Street, London EC2V 7WS. For more information please visit our website (www.eversheds.com/onewoodstreet). This email is sent for and on behalf of Eversheds LLP which is a limited liability partnership, registered in England and Wales, registered number OC304065, registered office Senator House, 85 Queen Victoria Street, London EC4V 4JL. Registered VAT number GB820704559. A list of the members' names and their professional qualifications is available for inspection at the above office. Regulated by the Solicitors Regulation Authority (see www.sra.org.uk <http://www.sra.org.uk/> ). Confidentiality: This email and its attachments are intended for the above named only and may be confidential. If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this email and highlight the error. ************* [ www.eversheds.com ] ************* ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
