-
Ah yes, classic problem in InfoPath. My advice: instead of creating an email view, create an email section. So your form ends up having two sections:
1. A section for "filling out" the form
2. A section for emailing
When the user clicks the button, instead of switching to the other view you simply change the value of a boolean field ...
-
Hi-
Once you have your connection to the SharePoint list set up, all the data is stored as a secondary data source in your form. Using rules and filters, the selection in the dropdown can be used to retrieve the matching record from the secondary data source. If you look up cascading dropdowns you might find quite a few tutorials on the process. ...
-
You can have two options: o Show Policy o Hide Policy
When the user checks Show Policy, a hidden section becomes visible. This section contains the policy text.
The user then can check Hide policy to hide the section.
Then the checkbox saying "I accept the policy" , which enables the Submit button.
Good luck!
-
Hi,
The first thing I would check the pingback settings for the controls that rely on qRules. You can right click on a control to view its properties and check that they are set to Always. This is necessary for browser forms.
Can you check? Thanks
-
In InfoPath, one way to do this is to have a checkbox that the users have to check to enable the submit button. The checkbox is connected to your terms/policy, such as "I have read the policy and accept it". The user checks the checkbox and then the submit button becomes enabled, so that the user can submit.
Is this an acceptable ...
-
Yes, a large data set from SQL will not perform well in InfoPath. The solution is to filter the data on the server. To accomplish this, you can use a 3rd party tool like DBXL to filter the data before it reaches your form. DBXL includes a web service called QueryDB which can do this.
The other option is to write your own web service in order to ...
-
If you don't want users to see a specific field, the simplest answer is to remove the field from the view. This does not remove it from the form's data source. In other words, the data is still there, in the data source, but it's not in the view (the designing canvas) so the user's won't see it.
If you wanted a more advanced ...
-
As you found out, the dropdown will get its data from the default view. So the only out-of-the-box solution is to show all items in your default view.
If that's impossible, you might look at writing your down web service to retrieve, which I've never done but I imagine is possible. There are third party packaged available which include ...
-
You could use Qdabra qRules, using a technique similar to the one explained in this article. This would save you from having to write your own custom code. Good luck!
-
I don't believe there's anything in the form options. How was the form deployed to the SharePoint form library? If you use a default File > Publish to a form library the behavior you're describing should not happen. Not sure about admin deploy or content types.