Couple of downsides of related field property to keep in mind:
1. In my experience the RelatedField property breaks site templates, as
its not part of the schema.
2. The only way to display the value of the related field in list view is
to use CAML DisplayPatterns that are now deprecated. If you try to use XSL
rendering for the field you cannot get the VALUE of the related field if it is
not already in the view - so no matter how good your XPATH skills are, you
can't make a custom field that renders the contents of a related field if the
related field is not in the view.
Where does this leave you?
* Use standard custom properties on your custom field to store the
name(s) of your related field(s).
* Use the related fields in the list views to enable
sorting/grouping/filtering, while using the custom field in the
new/edit/display forms.
Cheers,
James.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Turner
Sent: Wednesday, 9 March 2011 11:40 AM
To: ozMOSS
Subject: RE: MultiColumn Custom Field Problem
Use related fields (set it's value to what you want to sort on).
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfield.relatedfield.aspx
http://msdn.microsoft.com/en-us/library/ms459059.aspx
Regards,
Paul Turner
MCT, MCPD: Enterprise, MCSD, MCDBA, MCTS, Microsoft vTSP
Consultant
M: 0412 748 168
A: 66 Henley Beach Road, Mile End SA 5031
E: paul.tur...@dws.com.au<mailto:paul.tur...@dws.com.au> W:
www.dws.com.au<http://www.dws.com.au/>
This email and any files transmitted with it are confidential and are only for
the use of the person to whom they are addressed. If you are not the intended
recipient you have received this email in error and are requested to delete it
immediately. Any opinion expressed in this e-mail may not necessarily be that
of DWS Pty Ltd.
Please consider the environment before printing this email.
________________________________
From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] on behalf of James
Boman [james.bo...@i-pmo.com.au]
Sent: Wednesday, 9 March 2011 10:10 AM
To: ozMOSS
Subject: RE: MultiColumn Custom Field Problem
When making custom fields, the underlying data type is very important. The
Multi-Column Value Type is very useful for storing arrays of values, but the
downside is that it can't be sorted, filtered, grouped, indexed or edited using
the normal SharePoint UI.
You might want to consider changing to a different underlying data type to get
more OOB functionality. We have several custom fields that when added to a
list, create other simple columns in the list that don't appear on the
new/edit/display forms to enable indexing, grouping and other OOB features.
Cheers,
J.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul English
Sent: Wednesday, 9 March 2011 10:02 AM
To: 'ozmoss@ozmoss.com'
Subject: MultiColumn Custom Field Problem
I'm having an issue with a custom field that I've created. It is a MultiColumn
field that renders a list of names taken from a BDC. The problem I have is
when I add the column to a Document library I get the following message appear.
"This field type cannot be edited from most client programs and might block the
programs from saving documents to this library."
When I create a new document in the library the Doc panel displays the control
but is greyed out and says "Edit property on server". I've set the
"AllowBaseTypeRendering" property to True and the "ParentType" property is
MultiColumn in my fieldtypes.xml as suggested in several Google posts but this
hasn't made any difference. The field seems to work fine when added to a List.
Has anybody been able to resolve this problem using a DropDown? Could it be
because Word doesn't recognise dropdowns as MultiColumns ?
Thanks
Paul
________________________________
The information transmitted by this e-mail is intended only for the addressee
and may contain confidential and/or privileged material. Any interception,
review, retransmission, dissemination, or other use of, or taking of any action
upon this information by persons or entities other than the intended recipient
is prohibited by law and may subject them to criminal or civil liability.
Unless explicitly attributed, the opinions expressed are personal and not those
of HomeStart or the South Australian Government. If you received this
communication in error, please contact us immediately at
ad...@homestart.com.au<mailto:ad...@homestart.com.au>, and delete the
communication.
_______________________________________________
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
