Web Services

Re: Check out/in of InfoPath forms on SharePoint 2013 with claims

Laurie Wheeler — Thu, 26 Jul 2018 17:32:21 GMT

This project was put on hold for a couple years, but now being re-visited since they want to go to production with the form now. I agree that it would be a hassle to enforce check out/in - I've not gotten it to work, and we really don't need it. We really only need to know who has a form open. Since this is a browser form... nobody knows until they try to save and maybe find out their changes didn't save because somebody else's (last person to open the form) changes got saved instead. I implemented two new rules to my form load and added another 'set a fields value' in key places through out the form to address the "If Open" status. Your suggestion works like a charm - Thank you. I even added logic that allows a form admin the ability to reset this field and save the form back to SharePoint. This might come up if the original person who had the form open forgot to hit the "save" button which resets the field to blank, and posts the form back to SharePoint - if the user isn't available to re-open the form, a form admin and overrule the process and release the form for others to use.

Re: Check out/in of InfoPath forms on SharePoint 2013 with claims

Patrick Halstead — Mon, 18 Apr 2016 13:01:43 GMT

Hi Laurie,

This may seem like a strange suggestion, but why not just create your own field-promotedProperty-column for monitoring checkin/checkout status?

Just add a rule that on form load that checks the field. If it's blank, set it to the current person, submit the form, and leave it open. If it's not blank, check to see if it's the same as the current user (you could use username() for this) and if not, switch to a read only view and display some message that so-and-so has it checked out. Then, you can also provide an admin override. :)

Simply solution and you don't have to hassle with the checkin/checkout stuff in SharePoint.

Check out/in of InfoPath forms on SharePoint 2013 with claims

Laurie Wheeler — Thu, 14 Apr 2016 11:54:50 GMT

I've used Hilary's blog (http://www.infopathdev.com/blogs/hilary/archive/2010/11/10/check-that-form-out-or-in-automatically.aspx) with a tweak to accommodate SP2013 that uses Claims Authentication - namely the UDCX file must refer to a secure store app.

The issue is when using the auto checkout/in via UDCx files and web services with SP2013 claims authentication, you will get the 5566 error unless using a secure store app to pass through credentials. as such the credentials used to checkout the form, and check in the form automatically are using those credentials stored in secure store, NOT the user who opened the form and since the form at this point is read only to that user they cannot make changes or save the form.

Other than creating a new Web App using classic authentication (not something we want to do). Any ideas on how to get around this issue?