-
-
Hi Philippe,
Sorry for the outage. I was on vacation and apparently no one else saw this post. My apologies!
Have you tried creating a section that wraps the section that has the signature and hiding the outer section?
-
Hi Abhishek,
I should have checked forms built from ''New from Dataconnection''. I also should have realized that InfoPath automatically adds this for those schemas. Sorry for the bad advice.
At any rate, don't use ''New from Dataconnection'' to create forms. If you do, you can still fix this to not switch to the default view by adding a custom ...
-
-
Hi Afzal,
Have you installed the SharePoint SDK? It should have samples of how to create an event handler. Good luck!
-
Hi Hilary,
Good question. What you want to do is to use a pattern. In the designer, double click on the text field. Click Data Validation. Select field1 and for "matches pattern" in the middle dropdown. For the third dropdown in the Data Validation dialog, choose "Select A Pattern". The Data Entry Pattern dialog appears. ...
-
Hi Deb and welcome to our forum,
You can use your own rules, buttons, and query adapters to customise the experience. I'm not sure why your forum is switching to the other view, but it may have something to do with the rules around the existing Search button. Go to Designer, double click on Search. Click on Rules to see if there are any rules. If ...
-
Hi Bernie,
Interesting problem! My suggestion would be to put a wrapper section around the entire section that you want to sign and hide that. In other words, don't hide the inner. My guess is that InfoPath isn't smart about hiding the signature control when the section is hidden, but not sure.
-
Hi Eric,
I would look at signing individual sections as opposed to the entire forum. Then you can have some sections that show data which is editable where other sections (in your Finalized View) are locked down. Keep in mind that the fields are locked down when the form is signed. If the data field is in a section that has a signature, you can't ...
-
Hi DTobias and terribly sorry for the delay in responding. I am responsible for the errant reference on page 52. We had originally planned to add a section on custom merge and then cut it. Nobody caught this mistake during review. I'm sorry about this and thank you for pointing it out. It is a very good find.
You are going to need to do a custom ...