As your screenshot suggest, the valuelist attachecde to the Item field of the portal is dependent on the Category field. So the relationship of the Item valuelist must be Invoice_Category_Item TO a 3rd level relationship which is derived from the Invoice_Category TO.
So the issue what i think is that, the related valuelist based on Invoice_Category_Item TO, which is attached to Item field is not depending upon Invoice_Category TO. So if you will modify the Item valuelist "Include only related values starting from" option to Invoice_Category TO instead of Invoice TO, it will work fine i guess.
Thanks to you both.
S Chamblee - I downloaded the sample and that's exactly what I'm looking for. I'm off to decontruct it.
Dillip - I so nearly understand what you're saying. It will be great to compare your notes to the sample.
Well, I'm very close.
The Item field is picking up the correct values, but only for the first item on my Category list.
- When I select Bar Soap, I get the right list.
- If I select Cream, I don't get any values returned.
I've reviewed the sample file and confirmed that I have the same relationships:
- Invoice Data to Products where Item = Item
- Invoice Data to Products2 where Category = Category
The fields on the layout are displaying:
- Category = custom value list (Bar Soap, Cream, etc.)
- Item field = Products2::Item
I just can't see what last little bit I'm missing. Thanks for your help.
The Invoice Item (Invoice Data::Item) field should be a drop down list. Value list use items from Products2::Item.
Item field = Invoice Data::Item value list = Products2::Item