A non-required field becomes required after publishing - InfoPath Dev
in

InfoPath Dev

A non-required field becomes required after publishing

Last post 06-16-2016 04:47 PM by theInnovator. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 06-16-2016 07:26 AM

    A non-required field becomes required after publishing

    There is a strange behavior that users are experiencing with InfoPath.
    Just recently, I added a new option to multi-selection field that's not required, but after I publish it to SharePoint and a day goes by, the field becomes required. I can’t figure out why that happens.
    Does anyone you know why this happens?
  • 06-16-2016 10:36 AM In reply to

    Re: A non-required field becomes required after publishing

    That's odd. Can I see your form? You can attach it under the options tab... is the field now required in new & existing forms?
    Hilary Stoupa

  • 06-16-2016 04:47 PM In reply to

    Re: A non-required field becomes required after publishing

    Sorry for the late response. We may have found the issue. We think the SharePoint list is not syncing up somehow. So, we are going to try making changes in the list first and then open it in infoPath and then publish it. Before I would open the list in InfoPath first, make my changes and then publish. The change is really minor. All I do is add or remove a value from a multi-select control. If that does not work, I will see if I can post the form here so you can take a look. Thanks!
Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.