-
How about using a Multiple Selection List Box with the merge option for the promoted property, or having a non-displayed field that uses the double-eval trick to aggregate the checked values in 12 checkboxes and promoting that?
-
Ideally, what I would like is that all 12 variables be in 1 section and when it is exported to Sharepoint, Sharepoint would list the check variables in 1 column and not 12 different ones.
-
Would 12 separate checkboxes not work for your purposes?
-
In Infopath 2007, I want to create a section that contains 12 variables. Users should be able to select 1 or all 12 if they need to. Not sure how to do this. I experimented w/ radio buttons and could not get passed it letting me selected only 1 button. The form will be uploaded to a Sharepoint 2010 form library.
Thanks
-
I have a saveral infopath forms hosted in sharepoint. They were made for 2007 and later upgraded to 2010, without problems. I made changes to them a month ago without problems.
Now, the changes i make, are not saved in sharepoint. I get no error while publishing. I tried deleting the xsn manually and republishing, booting the server, renaming ...
-
Hello, I am also having this problem. Has anyone found a solution?
-
Hilary,
I have the same problem. I have a drop-down list box inside a repeating group that is being populated by a SharePoint list. When there is only one group it works fine, as soon as you add another group, it no longer works. What can I do or is this not possible in InfoPath?
-
Hello ErnestoM,
Thank you for your reply. This issue somehow resolved itself which is nice but not that reassuring :)
If I run into similar problems further down the road I'll try your method, thank you!
-
For the first question, the simplest option is to just use the auto increment ID used by SharePoint. Once you submit, SharePoint assigns the next available integer. The column is typically hidden in the form library view but you can add it. If that's not acceptable, you would probably have a more complex process - this, for example. This ...
-
Hi Jonas,
The parent item always gets created before the child.
If you'd like, you can use /mappingName= to map to one list (parent) then execute a second command (again using /mappingName) to map to just the child list.
Want to try that out to see if it helps?