InfoPath Dev

This if for InfoPath 2013. Came across a previous thread for writing values from a MLSB to another control which was very helpful for understanding the double eval formula.

I am attempting to do something similar, but append the selection values within the MSLB control. Currently, I have 5 conditional form load rules which trigger and set a corresponding value in the MLSB. Given the logical nature of InfoPath rules, the 5 form load rules overwrite previously triggered values instead of appending them.

My initial thoughts were the double eval trick was the right direction, but instead of concatenating values as text into 1 value, I need them to be set as separate values within the MLSB.

Here's what I have so far in my formula: eval(eval(changeManagementImpacts_mch, 'concat(., ", Translations to be updated or created (French or Spanish)")'), "..")

", Translations to be updated..." is concatenated as text to my control's default value ("None Selected"), where instead I would like them to be set as separately selected values.

Anyone successfully done this before? Any help is greatly appreciated!

Ooooh, I'm confused. Can you attach a copy of your form under the Options tab in a reply? One thing - if you need to work around the five condition limit, change the first dropdown for your condition to "the expression" and you can copy out the actual XPath to the condition and add the "and" or "or" as appropriate in a single large expression. https://www.infopathdev.com/forums/t/14871.aspx

Hello Hillary! I've attached a copy of my form. The control in question (changeMangementImpacts_mch) is at the bottom of view 2.11. The form load rules I have are the very last rules under Form Load. This is for an SPO List, just FYI.

Essentially, these form load rules are checking if columns in a separate list are marked for a specific item. If yes, I want the corresponding value(s) in my MLSB to be pre-selected on form load. The problem I am running into is due to the logical nature my form load rules overwrite the previously triggered values which results in only 1 selected value, instead of keeping the previously triggered values selected.

Ah-hah, now I understand! The issue is actually due to the nature of a multi-select list box, unfortunately. So - you'll see that the Value field is repeating if you look at the schema in advanced view. Unfortunately, when we select and deselect options in a multi-select, behind the scenes, InfoPath is inserting and deleting instances of this repeating node. However - since there is no rule-based way to add or delete repeating node instances, and there is no rule based way to index the target node, you end up in a situation like this. By default, your form will only have one Value node, but even if you re-opened a form where multiples have been selected (so there are multiple instances of the Value node) you still don't have a way in the field picker for the target node to specify which instance you wish to set - InfoPath will always just overwrite the first one.