-
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.
-
quote:Originally posted by Greg Collins
I am unaware of anything in a resource kit to do this. The only setting I know of is in the Tools | Form Options dialog. This prevents users from getting into the designer while editing a form, but does not prevent, as you've said, users from right-clicking the XSN or XSF file and choosing ...
-
I think the problem is a fundamentally misunderstanding of how to use the current() function.
The current() function returns a ''node''. Thus, my:Employee[my:SomeNode] is an invalid statement and will not give you a valid result.
You need to do something with that node that gets returned by the current() function. That is why my:Employee[. = ...
-
I am unaware of anything in a resource kit to do this. The only setting I know of is in the Tools | Form Options dialog. This prevents users from getting into the designer while editing a form, but does not prevent, as you've said, users from right-clicking the XSN or XSF file and choosing Design.
-
I'm trying to keep my users from being able to edit a form by opening the form in 'design mode' - I know about the security feature to keep people from editing it... but it is only a 'warning' ... and does not prevent the user from editing the form. I've read that there is some kind of security template that is supposed to be part of the resource ...
-
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.