-
Oh how funny, I was just typing the same suggestion up! Glad things are working now.
-
Hi - sorry no one has replied, it could be that your situation is uncommon. Have you tried publishing a new, simple form to a new library, just to verify that you can publish to the new site?
-
Here's a sample that may help you - save the file locally, right click and select Design, then preview to see the functionality.
-
Is your SharePoint instance on premises? Or Office 365? If on prem, you should be able to still publish a form with code. I usually create a dummy connection to the SQL DB and then modify the command in code so that I don't have to have a full trust form.
-
I'd check the submit options on the template - are they set correctly? Or are you submitting via rules?
-
The current function is contextual - I think you need something like this on your submit button: starts-with(xdXDocument:GetDOM("ClassInfoForEnrollementForm")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Class[../d:ID = current()/dfs:dataFields/my:SharePointListItem_RW/my:Class], "Reporting 100")
-
You won't be able to insert the XML declaration, I'm afraid - but I don't anticipate this causing you issues down the road, either. I usually only insert the mso-infoPathSolution processing instruction.
-
I can't reproduce this - I set up a similar scenario on my SharePoint 2013 site, with a choice column that I made required if the lookup's ID = an ID where the title started with a certain string, so much like yours for the Reporting Security Access - and my validation works as anticipated. Perhaps since you have a submit request button on ...
-
Hey, Lou, I'm sorry, but I didn't get a chance to try this today. I will in the morning. :)
-
I'm going to run a test on a list form later today & see if this reproduces for me at all. Just in case the issue is with the custom validation - I'll let you know what I learn