Clear Childs when changing value Parent


Hi Leonid,
I posted some comments on your msdn blog in 2007 on this beautiful piece of work.
I'v anxiosly been waiting for your release here on codeplex, hoping you had done some last finetung to the connected lookup field.
Installed the solution today.
Everything worked like a charm, except for the same problem i've had from the start.
I've created everything exactly as described in your documentation. All is working exactly as you decribe. At the end of your documentation a new list item is created with three working connected lookup field.
Here's where the problem begins. Let's say whe want to edit the list item we just created. 
Looking at your example, i want to change the value of the country from 'Australia' to 'Canada'.
Once i've opened the item and select edit item, all is looking well. But When i change 'Australia' to 'Canada' i get 'an unexpected error has occured'.
The only way i can workaround this is is to first set the 'Lastname' (which is the last child lookup field) to '(none)' and save the item, then edit the item again en set the 'State' (which is the 2nd last child lookup field) to 'none' and save the item, then edit the item again and change the Country from 'Australia' to 'Canada'. I can now the choose the State and Lastname without any errors.
I'm no programmer but it looks like all child fields must be flushed/cleared when a value of a connected lookup field acting as a parent is changed.
Please, please, please help me out. I've been struggling with this problem for a year.


llyublin wrote Dec 6, 2008 at 2:18 PM

I will look into this issue as soon as...

klaiddias wrote Dec 20, 2008 at 9:40 PM

I'm have a same problem, please, please, please help me too;

panoone wrote Jan 14, 2009 at 3:38 AM

IS there any resolution to this problem yet?

jamesd999 wrote Jan 15, 2009 at 3:41 PM

same issue the sepecific error is 'Lookup' has a SelectedValue which is invalid because it does not exist in the list of items. this would be perfect if this were fixed

llyublin wrote Jan 15, 2009 at 10:06 PM

2.0.011509.0 addresses the issue

wrote Jan 15, 2009 at 10:07 PM

wrote Feb 14, 2013 at 1:51 AM

wrote May 16, 2013 at 7:44 AM

wrote May 16, 2013 at 7:44 AM

wrote Jun 14, 2013 at 7:46 AM