-
I've attached a simple sample with custom validation - for the first drop down, you'll see the second is not required if you select "Bagels". Save the linked file locally, right click, select design and from there you can preview.
-
Check the ULS logs on SharePoint - that should tell you more.
-
Sorry, I guess I didn't understand this whole "secondary set of fields" business. You want to submit the XML to a second library that has different fields promoted than the first library? I would think you would just need to promote all the fields and modify your library views to hide the ones you don't want displayed.
-
Hi, instead of setting the field as cannot be blank, use custom validation. Then you can add a validation rule like "if field 1 is not blank and if there are items in my secondary data connection that populates the dropdown for field 2 that match the selection in field 1, field 2 can't be blank" - sorry, that sounds clunky. I'll ...
-
Multiple users can open the same template. They fill it out and submit individual forms (XML files - some of this depends on your form logic). Since InfoPath doesn't have out of the box connection to work with Excel, I'm assuming your form has code?
-
Responded to your new post here: http://www.infopathdev.com/forums/p/30827/105122.aspx#105122
-
Well, without workflow, you will have to open the form for the email to be sent, so I'm guessing that sort of defeats the purpose here. Rules only run when a field changes - so you'd need to open the form, and set the maintenance renewal reminder field to today, then the rule on the field will run....
-
Whoops, also this: /child=my:BalanceScoreCardTable/my:BalanceScoreCardItem should be: /child=my:BalanceScoreCardItem
-
Hi - it is probably your schema design. We need the repeating group to be the last group in the parent group, which means in the BalanceScoreCardTable you need to move MYID2 up so the repeating group is last. Can you try that?
-
As outlined, this would require a great deal of code - but for tracking purposes, can't you just submit your form to a SharePoint Library? Promote all the fields that you need to see data from and then you can use views to find the open requests, who they are from, etc? That would be the simplest out of the box approach.