InfoPath Dev

Hi, I'm having an issue with cascading data in a repeating table in an Infopath form. Here's the case : I select data in a 1st row in 2 cascading dropdowns. When I select in a second row the same data in the 1st level of the cascade but I need to select another data in the 2nd level of the cascade, it automatically switches to the same value of the 2nd level in the 1 row. Does someone has solution for this ? Thx in advance ! T.

 Is the issue that the field is getting set w/out you selecting an option? So, perhaps you have a rule or a default value that isn't doing what you want? Or is the issue that the options you expect aren't available?

Neither of both, when I have 2 options in the dropdown of the 2nd level, and I have choosen the 1st option in the 1st ArticleLine and I want to select the 2nd in the 2nd ArticleLine, than I'm even able to select the 2nd option, but when I go to the next field it jump to the option that was selected in the 1st ArticleLine

Hi, Anyone any suggestions for the issue mentioned above ? Thanks in advance for your help ! Kind regards, Tim

Any chance you can attach a copy of your form in a reply under the options tab? I apologize - I'm having a hard time understanding your description. :)

Hi Hilary, I just added the form in attachment. If you select in the repeating table 2 or more times the same package, you will see that the subpackage in row 2 and/or 3 will jump to the same value as the sub-package in row 1. The values of the dropdowns are linked to tables in the SharePoint environment so I'm not sure you will be able to see them. Please let me know if you need any further information. Kind regards, Tim

Ah hah! See the attached screenshot - I think the issue is with the value field you have the subpackage set to! See how "Value" is repeating? Is it really the package ID you want stored as the value for the subpackage? I'd guess you'd either want the ID for list item, or the title....

Yes indeed, the PackageID is a lookup from the Package List, that's why it appeared as a repeating field as multiple values might have been possible theoretically. I just added the values, without looking them up in the package Table. After that I modified the form, but unfortunately still the same issue. If I look in the expression I see "d:jknt = current()/my:Package" which, in my opinion should be the correct filter. I've added the new version of the form. I think it has something to do with the fact there's 2nd level cascade in 1 article line. Have you experienced such an issue before ? Kind regards, Tim

No, I don't think it has to do with the controls being in the same row. Is the Package ID really what you want to be storing for the value of the subpackage dropdown? I understand your filter and it looked right - but I don't see why you would want to have the package id (jknt) as the value for the control bound to the subpackage dropdown.

The Values of the Package is also the ID, I always use the ID as value and the other field as view. It's practical when exporting the repeating table to a list. Do you think this could be the cause ? If so I could change it and see what the result is . What do you think ?

I'm attaching a copy of the form with the subpackage dropdown set the way I think it should be, with the ID for that list as the value.

Hi Hilary, Thx, I cannot open the form anymore. I receive the following Error message : Forms that require the domain permission level contain features that access information on a network, such as data connections, linked images, and code. Can you perhaps send me a printscreen from how you setup the subpackage ? Sorry for all the trouble :-s

Save the linked form locally by right clicking the link in the post, then you can right click the downloaded file and select Design to open in design mode - forms don't like being moved. :)

Well thanks a thousand times, what you did seems so simple and it works !!!!! Thx a lot Hilary :-)

Great, so hopefully what I was trying to explain made sense - I think you just had the subpackage dropdown configured wrong for the value field. :)