-
Hi!
I've read through this thread, and I'm pretty confused. I'd like to help you though, so I need to ask some questions first so that I can understand what you are trying to do.
First, so you know, the InfoPath To SharePoint List tool has 2 distinct and separate purposes. One is to take existing XML files (the saved files after a ...
-
Hi -- I was able to publish this as an admin approved template without any issue. When are you getting this error? When you upload the template from the published location in _admin/UploadFormTemplate.aspx?
-
Your "group2" field in your formula -- You've selected that using the "Insert Field or Group" button, right? So that it is underlined?
-
Can you attach your template? Under the Options tab, you can attach a file. As I said earlier, we use this method in browser forms with no issue, so it must be something in your form or in IPFS. I can take a look, see what happens when I try to publish it.
-
You need to use a relative XPath:
eval(eval(group2, 'concat(my:Prompt_Other, ", ")'), "..")
-
Are you submitting via rules? Or just a standard submit? Submitting to SharePoint? Email? Submitting via code?
What is the validation in place?
Generally, an InfoPath form WON'T submit with validation errors, so you are right that this should be straightforward, which is why a bit more detail might help....
-
One issue with generating an ID when the form opens -- most methods suggest getting the max ID currently in use and incrementing... but what happens if I open a form, and the ID I get is 2, and you open a form before I submit mine? You also get an ID of 2. You really need to consider using a SQL table where you can "reserve" an ID for ...
-
Actually.... there is.
You'll need a field in your repeating data source that has something you can filter on -- like maybe the category name? Then, in the properties for the repeating control, you can set a specific default value for that field when the user inserts a new row / section. Then add conditional formatting to each of your tables. ...
-
Did you try right clicking the root node in your Main Data Source and seeing if you could add a group there?
Because it doesn't look like a straight XML connection will work-- just like with your Web Service, you can't make a section optional from a secondary data source.... It may be possible if you modify the InfoPath generated schema ...
-
Hi -- you can check out your form using the SharePoint Lists web service -- no code needed. You have to add a query data connection to the web service, (_vti_bin/Lists.asmx) and select the CheckOut message. Also add a data connection to the library where the XML is submitted -- for that connection, you can select the checkbox for getting info ...