-
In the InfoPath Designer ....
Double click on the ''from'' listbox. Click Rules. Click Add. Click Add Action. Choose ''Set a Field's Value''. Click the icon next to the Field text box. Select the ''to'' listbox field. Click the fx button next to the Value text box. Click Insert Field or Group. Select the ''from'' field. Click OK 6 times. Preview. ...
-
Hi guys,
Make the form Full Trust. Then it will work.
Patrick Halstead [InfoPath MVP]
InfoPathDev
-
Because you want to learn everything?
Patrick Halstead [InfoPath MVP]
InfoPathDev
-
Hey Matt,
I think I will choose #4! Oh wait, I don't have one! Dang! :)
Patrick Halstead [InfoPath MVP]
InfoPathDev
-
Hi Matt,
OK, that works! Glad you found a workaround but it will require multiple XSNs. The main benefit of the XSL import approach is to be able to just use one XSN. What happens down the road if you have to change the XSN? Maybe you don't want to change it for past forms... come to think of it that's exactly your scenario... ok, sorry!
Carry ...
-
I agree with VT, use a secondary data source for presentation stuff. Otherwise the data sanctity of the XML form is compromised.
Patrick Halstead [InfoPath MVP]
InfoPathDev
-
It's feasible but it will require a Full Trust form to provision the library and upload the file.
Patrick Halstead [InfoPath MVP]
InfoPathDev
-
Use a secondary data source for the lookup and copy to the main data source then you can set the main data source field by default and only copy from the dropdown when there is an OnChange. You can use a rule to set the field in the main data source when the field in the view bound to the secondary data source changes.
Patrick Halstead [InfoPath ...
-
Hi Herve and welcome to our forum!
You should still be able to get the ID for the item since that's part of the default SharePoint properties and it is independent of a modified default list. However, the 50 elements is more of an issue. This is something that you cannot workaround. Indeed, you have discovered the main limitation of the ...
-
Very Tender Asparagus,
Great to have you on board!
Patrick Halstead [InfoPath MVP]
InfoPathDev