sp2010filteredlookup Issue Tracker Rss Feed

Commented Issue: Required field validation is not working [15943]

saad2912 — Tue, 08 Jan 2013 10:18:49 GMT

When I saved data on filtered lookup field but null or empty value still accepting
Comments: ** Comment from web user: saad2912 **

When I saved data on filtered lookup field but null or empty value still accepting

Created Issue: Required field validation is not working [15943]

saad2912 — Tue, 08 Jan 2013 10:16:11 GMT

When I saved data on filtered lookup field but null or empty value still accepting

Created Issue: Site template containing field taken with data included throws error "Value does not fall in expected range" [15693]

sonalibhlr — Fri, 12 Oct 2012 08:20:45 GMT

when list/library contains values for this field column and site template is taken with data included where this list resides, The wsp site template is created succesfully but while creating new site from this site template, It throws a error "Value does not fall in expected range"

Created Issue: Check if field Required not implemented [15645]

alexeybbb — Mon, 24 Sep 2012 07:11:23 GMT

Hello, thanks for project.

Required field cheking not implemented. We add this code to MultipleFilteredLookupFieldControl.cs:

public override void Validate()
{
if (ControlMode == SPControlMode.Display || !IsValid)
{
return;
}

base.Validate();

if (Field.Required && (Value == null || Value.ToString().Length == 0))
{
this.ErrorMessage = "Required field";
IsValid = false;
return;
}
}

Created Issue: List not showing current item [15529]

VoodooChild_ — Wed, 22 Aug 2012 15:27:55 GMT

Hi,

We have a list with user data (name, email, etc) and we have a list with accounts data (user account and password)

In the user list you can select a user account to match this user using a CAML query filtering which user accounts are selectable/visible (accounts already used are not visible). Everything works as expected when we edit an item in the user list with the lookupfield and the filter is allowing some data to be selectable. However when there are no items available in the accounts list the currently selected item is not shown (it is when there are other accounts).

The CAMLQuery set on the user list, filtering data from the user accounts list:
<Where><Neq><FieldRef Name="AccountUsed" /><Value Type="Boolean">1</Value></Neq></Where>

Our usage:

Closed Issue: Deleted [12653]

johnmcalvert — Thu, 12 Jul 2012 20:34:44 GMT

Deleted.
Comments:

Void

Commented Issue: SP 2010 :: Only Site Collection Admins can Add/Edit [15391]

johnmcalvert — Thu, 12 Jul 2012 20:33:02 GMT

There is an issue that only a site collection admin can utilize the field type. This is problematic for more controlled environments.
Comments: ** Comment from web user: johnmcalvert **

I confirmed this in my dev/test environment.

Steps to reproduce:
- install WSP
- with user account that is less than site collection admin, eg site owner
- on New Site Column page in Site Settings
- under Name and Type click radio button for Filtered Lookup
- Error: Access Denied

Closed Issue: SPMetal Issue [14352]

johnmcalvert — Thu, 12 Jul 2012 19:58:52 GMT

Hi there,

I seem to be having issues with generating classes using SPMetal when there are SharePoint 2010 Filtered Lookup Fields. The classes are generated, but the properties for the filtered lookup fields are not. Has anyone else had this issue or similar?

Thanks in advance,

-Pat Ramadass
Comments:

SPMetal limitation, workaround exists, see comments

Commented Issue: SPMetal Issue [14352]

johnmcalvert — Thu, 12 Jul 2012 19:57:30 GMT

As per MSDN SPMetal docs "Extending the Object-Relational Mapping", http://msdn.microsoft.com/en-us/library/ee538669.aspx:

- SPMetal cannot generate code for fields that use a custom field data type.

That same article explains how to work around this limitation of SPMetal using the ICustomMapping interface.

Closed Issue: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/' [15265]

johnmcalvert — Thu, 12 Jul 2012 19:53:29 GMT

When solution is installed, an error displays:

This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution '5dcda1dd-2183-48f6-b330-978a1c891baa' failed validation, file manifest.xml, line 6, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'.
Comments:

As noted, the filtered lookup solution is NOT a sandbox solution, and never can be as per SharePoint product architecture.

Created Issue: SP 2010 :: Only Site Collection Admins can Add/Edit [15391]

Zeph88 — Mon, 09 Jul 2012 17:24:16 GMT

There is an issue that only a site collection admin can utilize the field type. This is problematic for more controlled environments.

Created Issue: Querying Semi Large Items [15312]

rinjutsu — Tue, 19 Jun 2012 13:17:37 GMT

Hi. This filtered lookup field has issue on querying semi large items. I got a list of only 4800 and its giving me a timeout error as indicated in the logs. I managed to resolve my issue today by filtering some items from my 4800-item list. However, in the long run, i'll be removing this field and replace it with an ordinary lookup field and control my filtering via InfoPath.

Commented Issue: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/' [15265]

johnmcalvert — Fri, 08 Jun 2012 01:52:08 GMT

As PeppeDotNet says in the discussion thread on this same topic:

The filtered lookup solution is NOT a sandbox solution.You must install it using Powershell cmdlet Add-SPSolution and you have to deploy the solution using the Central Administration.

So we should close this issue.

Created Issue: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/' [15265]

chelleatl — Wed, 06 Jun 2012 22:17:41 GMT

Commented Issue: AllowMultipleValues will not be inherited into lists [14022]

johnmcalvert — Tue, 28 Feb 2012 02:22:43 GMT

When creating a field in the rootweb (on sitecollection level) the property "AllowMultipleValues" will not be passed to the lists, where the field will be added.
I've created the field with "AllowMultipleValues=true" (through the UI). After adding the field to some lists, the value inside the lists is false.
For SPSiteDataQueries this value is essential. A lookup-field without allowing multiple values must be added with "Nullable='false'" to the viewfields, else (if nullable is set to true) SharePoint will not find any item where the field is defined. But if multiple values are allowed, the fieldreference must be set to "Nullable='true'".
Comments: ** Comment from web user: johnmcalvert **

As a work around, after you add the field to a list modify the properties of the list field to change AllowMultipleValues to True.

I found the same problem with the property Apply List View Filter. When set at the site column level it does not propagate to a list field but can be set manually at the list field level.

Commented Issue: Filtered Lookup Field "List" attribute and custom content type using vs2010 [14524]

thcase — Mon, 16 Jan 2012 17:55:14 GMT

I have added "Filteredlookup" column by using the below field defination. If I assign the GUID to "List" attribute in field defintion; it works but if I change it with value "Lists/ProductDetails"; It does not assosiacate the Lookup list with field.
How I can get rid of GUID ? However it works perfect for field of type "Lookup". Following is the field dfintion;

<Field Type="FilteredLookupField" Name="lookupTemp123" StaticName ="lookupTemp123" ID="{E7EE707C-FF3A-4B24-9C62-2BD7CE1E9CAC}"
List="Lists/ProductDetails" ShowField="SettingValue" DisplayName="lookupTemp123" Required="TRUE" Group="Custom Site Columns" >

<Customization>
<ArrayOfProperty>
<Property>
<Name>QueryFilterAsString</Name>
<Value xmlns:q1="http://www.w3.org/2001/XMLSchema" p4:type="q1:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">&lt;Where&gt;&lt;Eq&gt;&lt;FieldRef Name=&quot;LookupKey&quot; /&gt;&lt;Value Type=&quot;Choice&quot;&gt;ContentKey&lt;/Value&gt;&lt;/Eq&gt;&lt;/Where&gt;</Value>
</Property>
<Property>
<Name>ListViewFilter</Name>
<Value xmlns:q2="http://www.w3.org/2001/XMLSchema" p4:type="q2:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance" />
</Property>
<Property>
<Name>SupportsMultipleValues</Name>
<Value xmlns:q3="http://www.w3.org/2001/XMLSchema" p4:type="q3:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">False</Value>
</Property>
<Property>
<Name>IsFilterRecursive</Name>
<Value xmlns:q4="http://www.w3.org/2001/XMLSchema" p4:type="q4:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">False</Value>
</Property>
</ArrayOfProperty>
</Customization>

</Field>
Comments: ** Comment from web user: thcase **

In looking at the source code, I wonder if the issue is the fact that the constructor for the FilteredLookupField just passes the fields from the XML. Since the spLookupField doesn't have a List property, it doesn't get set. It is looking for a LookupList property, which is the GUID of the lookup list the field is to be set to. The issue may be needing to lookup the passed list attribute and setting the LookupList field property in the FieldCollection passed to the parent constructor.

Commented Issue: Filtered Lookup Field "List" attribute and custom content type using vs2010 [14524]

thcase — Mon, 16 Jan 2012 17:29:14 GMT

I exported a WSP file to look at the Field Definition it produces. The code above looks correct, except missing Overwrite="True" UnlimitedLengthInDocumentLibrary="FALSE" EnforceUniqueValues="TRUE". My issue is similar to yours, but it is that when I specify Type="Lookup" it gets the right list, but when I specify Type='FilteredLookupField" the list selected is incorrect. I haven't looked at source code to determine why this is happening.

Created Issue: Filtered Lookup Field "List" attribute and custom content type using vs2010 [14524]

naveedafzaal — Mon, 05 Dec 2011 15:47:26 GMT

I have added "Filteredlookup" column by using the below field defination. If I assign the GUID to "List" attribute in field defintion; it works but if I change it with value "Lists/Lookups"; It does not assosiacate the Lookup list with field.
How I can get rid of GUID ? However it works perfect for field of type "lookup". Following is the field dfintion;

<Field Type="FilteredLookupField" Name="lookupTemp123" StaticName ="lookupTemp123" ID="{E7EE707C-FF3A-4B24-9C62-2BD7CE1E9CAC}"
List="Lists/Lookups" ShowField="SettingValue" DisplayName="lookupTemp123" Required="TRUE" Group="Custom Site Columns" >

<Customization>
<ArrayOfProperty>
<Property>
<Name>QueryFilterAsString</Name>
<Value xmlns:q1="http://www.w3.org/2001/XMLSchema" p4:type="q1:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">&lt;Where&gt;&lt;Eq&gt;&lt;FieldRef Name=&quot;LookupKey&quot; /&gt;&lt;Value Type=&quot;Choice&quot;&gt;ContentKey&lt;/Value&gt;&lt;/Eq&gt;&lt;/Where&gt;</Value>
</Property>
<Property>
<Name>ListViewFilter</Name>
<Value xmlns:q2="http://www.w3.org/2001/XMLSchema" p4:type="q2:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance" />
</Property>
<Property>
<Name>SupportsMultipleValues</Name>
<Value xmlns:q3="http://www.w3.org/2001/XMLSchema" p4:type="q3:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">False</Value>
</Property>
<Property>
<Name>IsFilterRecursive</Name>
<Value xmlns:q4="http://www.w3.org/2001/XMLSchema" p4:type="q4:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">False</Value>
</Property>
</ArrayOfProperty>
</Customization>

</Field>

Created Issue: Filtered Lookup Field "List" attribute and custom content type using vs2010 [14524]

naveedafzaal — Mon, 05 Dec 2011 15:47:26 GMT

I have added "Filteredlookup" column by using the below field defination. If I assign the GUID to "List" attribute in field defintion; it works but if I change it with value "Lists/Lookups"; It does not assosiacate the Lookup list with field.
How I can get rid of GUID ? However it works perfect for field of type "lookup". Following is the field dfintion;

<Field Type="FilteredLookupField" Name="lookupTemp123" StaticName ="lookupTemp123" ID="{E7EE707C-FF3A-4B24-9C62-2BD7CE1E9CAC}"
List="Lists/Lookups" ShowField="SettingValue" DisplayName="lookupTemp123" Required="TRUE" Group="Custom Site Columns" >

<Customization>
<ArrayOfProperty>
<Property>
<Name>QueryFilterAsString</Name>
<Value xmlns:q1="http://www.w3.org/2001/XMLSchema" p4:type="q1:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">&lt;Where&gt;&lt;Eq&gt;&lt;FieldRef Name=&quot;LookupKey&quot; /&gt;&lt;Value Type=&quot;Choice&quot;&gt;ContentKey&lt;/Value&gt;&lt;/Eq&gt;&lt;/Where&gt;</Value>
</Property>
<Property>
<Name>ListViewFilter</Name>
<Value xmlns:q2="http://www.w3.org/2001/XMLSchema" p4:type="q2:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance" />
</Property>
<Property>
<Name>SupportsMultipleValues</Name>
<Value xmlns:q3="http://www.w3.org/2001/XMLSchema" p4:type="q3:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">False</Value>
</Property>
<Property>
<Name>IsFilterRecursive</Name>
<Value xmlns:q4="http://www.w3.org/2001/XMLSchema" p4:type="q4:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">False</Value>
</Property>
</ArrayOfProperty>
</Customization>

</Field>

Commented Issue: SPMetal Issue [14352]

patramadass — Sat, 15 Oct 2011 16:08:50 GMT

Hi there again,

After further investigation and trial/error it seems that simply adding similar code (either to the generated SPMetal class or preferably to another partial class) to what would be generated by SPMetal for a normal lookup field seems to work.

Thanks,

-Pat Ramadass