marc,
I got it to work - but it didn't have to do with the update. It was how my relationship list was structured. Correct me if I'm misundestanding this.
The method is expecting that (like your Region/States/Cities example) the relationship list is expecting that the parent field is a lookup and the child is a text field (which is then used as lookup in the current form). Also the Parent is acting as the foreign key in the relationship list.
However, I have relationship lists where both parent and child fields are lookup. Unfortunately SP doesn't allow nested lookups - meaning I can't have a lookup field in my current list that points to a lookup field in another list. The only solution seems to be adding a separate text field (in relationship list) for the child field and populate the text field from the child lookup. Then I can reference the child text field as a lookup in my current list.
thanks
I got it to work - but it didn't have to do with the update. It was how my relationship list was structured. Correct me if I'm misundestanding this.
The method is expecting that (like your Region/States/Cities example) the relationship list is expecting that the parent field is a lookup and the child is a text field (which is then used as lookup in the current form). Also the Parent is acting as the foreign key in the relationship list.
However, I have relationship lists where both parent and child fields are lookup. Unfortunately SP doesn't allow nested lookups - meaning I can't have a lookup field in my current list that points to a lookup field in another list. The only solution seems to be adding a separate text field (in relationship list) for the child field and populate the text field from the child lookup. Then I can reference the child text field as a lookup in my current list.
thanks