-
You can have both on the same control but play around with the order. If the conditions are both met, then the control could be hidden instead of disabled!
-
Which mappings form are you referring to?
-
I would suggest creating a test form with some very simple code, and publishing that. It may be a SharePoint issue where no code is being allows at the moment (due to a config issue).
Such a test would at least tell us if it's a server issue or an issue specific to a form with qRules.
I'm attaching a test form with some simple code for ...
-
This might be possible to achieve with xslt tranform. qRules includes a command to achieve this, or it can be done using custom code.
If you export the data to Excel and massage it there, you can then import it into InfoPath using the Excel to XML tool.
Bottom line is: there's no easy answer here. It's going to take a bit of work to ...
-
What do you mean when you say that "lookup fields are not available"? Are they not showing in the data connection wizard? Are those fields in the secondary data source, just not returning any data?
-
Hi-
You cannot add code to a SharePoint list form.
You can add code to a regular InfoPath form (published to a form library) so that it submits to a SharePoint list (in addition to the out of the box data connection to submit to the form library).
Here's one method: ...
-
Hi BJ,
Before the form is submitted as an attachment, you'll want to make sure that the loop up fields have been copied into the main data source. Since the secondary data sources won't be available, having the data in the main data source is the solution.
Hope this helps!
-
I'm a little confused by your scenario...
A SharePoint list stores flat data. A list item will have a set number of columns with data and you can load each of those items via a secondary data connection, into an InfoPath form. Once in the InfoPath form, you'll have a repeating structure in your secondary data source (containing all ...
-
Typically one needs to open an xml form to have the data updated (via rules or via user input) then resubmit to overwrite the existing xml form.
A similar question was asked yesterday but I don't think that a solution has been found for that question either:
http://www.infopathdev.com/forums/t/25632.aspx
-
I imagine that your condition might be my:field1 <= my:field2.
Instead try this:
current()/my:field1 <= current()/my:field2
I'm attaching a sample XSN that you can download, open in design mode, and see how I've implemented this.
Good luck!