I'll remove the setting of that parameter and see if that fixes the form. Setting the CheckoutToLocal to "true()" throw an error, but setting it to "true" seemed to be OK.
That makes sense. Your instructions didn't have that being set, but another post from Yash Goel (https://blogs.technet.microsoft.com/yashgoel-msft/2015/01/12/automatic-checkout-check-in-in-infopath-2013-with-sharepoint-2013/) indicated it did need set, although he set it to blank. Also, setting the CheckOutToLocal to "true()" throws an error as your post instruction has, but setting it to just "true" is OK.
I had another post (http://www.infopathdev.com/forums/p/31152/106165.aspx#106165 ) from a while back that Patrick Halstead replied to asking why I just didn't create a form field with rule logic instead. I really don't require checking the form out, we just have to know who has it open.... and adding a couple extra rules when the form loans allows it to open to a 'view only' so that other users cannot edit it. Not sure if you remember, the BIG 12+views, so large I have to deploy it from the server because of all of the rules that also has qRules 7.2 injectected for file attachments, form we have (Change Management)…. it is that beast. We are finally going to production with it after 2 years. But, this little hurtle of knowing who has the form open.. it's a show stopper on browser enabled forms. Since this form already has the data connections into userprofileservice for signatures, I opt'd to go the route of a couple extra onload rules to render the form 'view only' if someone else has the form open - we really don't need to have it checked out/in automatically. Having said that, I want to get this to working in our environment.... I have other situations, on smaller forms were this will be needed.
I'll review the parameters again on this smaller form... and try it... and let you know what the result is and send the form.
Laurie Wheeler