-
You can't bind a node to two different nodes. However, you can bind the control to your main data source node, then set a rule on that node to also copy it's value to the secondary datasource node. It achieves the nearly same result.
-
What is not possible is displaying the joined value as the display value in the dropdown. but if you just want to write the joined value to the other node then yes, you can use concat() as part of a rule which will fire every time the dropdown value is changed.
-
Another option for putting everything on the same view is to use the Master/Detail control which is designed for this.
-
Fantastic mbenbow. This information will be very useful! Thanks for contributing.
-
What this is about is when you deploy InfoPath in an organization you can actually turn off the designer for a user completely. THis is not a per form setting though. This will apply to that user entirely so they can never design any form. You will find the option in the Custom Installation Wizard.
-
Hello and welcome to our forum!
This is possible with SharePoint 2007 which allows for setting permissions at the document level. Unfortunately with SharePoint 2003 this is not possible.
-
Ah this is a very common scenario. To fix this you just need to add a rule on the top dropdown to set the value of the bottom dropdown's node to blank. Then every time the top dropdown changes the bottom one will be cleared out. Even in the repeating section using rules should properly maintain context and only clear the dropdown in that item.
-
Glad our forum could help. This is also a good opportunity to point out that the samples that ship in InfoPath 2003 were built before the calculations functionality was added for SP1. Therefore there is a ton of extra code in there that we wouldn't do today. We just didn't have the option back then when we built them and could not take on the ...
-
Ah ok. Glad you found the permissions issue on the server. Sorry I couldn't help more. :)
-
Baffling. Sorry I couldn't help.