-
For existing forms, you'd need to set the content type as the default for the library, then navigate to the Relink view in the library, and relink your existing XML. Relinking updates the href in the InfoPath processing instructions in the XML (download an XML file, take a look in the text editor of your choice and you'll see the href). ...
-
Not that I know of - there may possible be a way to manually modify the view file to do this, but if this is a browser form, there is a good chance a manually modified view won't work correctly in the browser.
-
Did you see the sample form I attached in a reply to your other post? http://www.infopathdev.com/forums/p/38487/116672.aspx#116672
-
No real easy way here. I'd just add a Sort Order column to my list and set it manually, then sort by that column in the data connection.
-
Oh that is weird. I would probably compare the manifest files - you can save the form as source files, or rename from XSN to CAB to access source files, and compare the manifest.xsf in the form where the fields are properly selected and the one where they are not. Data connections aren't being updated on publish are they? Since you are ...
-
This is a SharePoint 2013 site, right? Is your server up-to-date on it's patches? I've got 2013 ShP sites with 2013 InfoPath browser forms that have no issues w/ the user profile service (once loopback check is disabled) but I'm not really sure what to suggest you try next... can you admin deploy a form and see if you get a different ...
-
I've attached a simple sample - right click the link to the file, save it locally, right click the saved file and select design to open in design mode. You may need additional logic if the first date could be greater than the second date, or if you want the button disabled if the fields are blank, but hopefully this gets you pointed in the ...
-
Can you attach the XSN to a reply? I see an XML file above (and just FYI, your screenshot doesn't show for me - you can upload a picture under the Options tab tho!)
-
Well - that's because you are using secure store in your UDCX. :) However, this should work w/out that. Create a simple test form. Add a data connection to the user profile service (set it to NOT run on load) and drag all the query and data fields onto your form so you can see the values. Add a button that runs the query. Add a calculated ...
-
Got it - so if they only ever submit when the form is first created, you don't need to add conditions in this specific case, because they would never apply. :) But yeah, you have found the right way to do this - there isn't really a more graceful way about it. Have a great weekend!