I've had a similar problem; SharePoint/InfoPath doesn’t seem to deal with multiple-selection list boxes very well (unless I'm also missing something). The workaround I used w/o code was to create a new hidden field with the default value set to:
eval(eval(MultiSelectField[. != ""], 'concat(., ", ")'), "..")
where MultiSelectField is your field
You need to tell InfoPath that changes to the field should result in a server round trip.
Select the source control.
In the ribbon tab Control Tools Properties click Control properties
On the Browser Form tab select Always below Postback settings
If you know which site collection the form has been published to, you can download the form from the site collection. Go to the site collection "All Site Content > Form Templates" or http://YourSite/YourPath/YourSiteCollection/FormServerTemplates/Forms/All%20Forms.aspxto see all administrator-approved form templates published to the site collection.
Right, you cannot share an InfoPath or PowerApp form with external users.
As an alternative, I could suggest you taking a look at our Plumsail Forms. This solution is designed for creating responsive forms and publishing them to modern SharePoint pages. But also, it allows you to create a form and publish it anywhere, at any website publicly available.
Firstly, we need to know whats happening behind the scenes with Admin approved forms while uploading and activating within the Central Admin.
Behind the simple click of the Upload button, InfoPath Forms Services creates a feature to deliver the form template (.xsn file). The feature is then wrapped in a Windows SharePoint Services solutions package which ...
Old thread but someone might find this helpful.
When we had this problem, we found that the hidden workflows library had the wrong permissions.
In SharePoint Designer go to All Files then right-click on Workflows and select Properties. Under Customization click on Permissions for this list.
Check that the user with the problem has permissions in the ...
You would add a calculated value to accomplish this.
Do not add your Created By field to the form template.
Add a Calculated Value from the Controls.
Go into the control
Select Insert field or Group
You wont see Created By at first, select show advanced view
Expand Created By
That should do it ...
well, state service just use SQL DB to store user session data so Guids are most probably refers to current User session. Lock on a SQL table can appeared after too many requests at the same time. Probably your State Service is a performance bottleneck for a bigger farm? Could you please enable SQL profiling on State DB and check its performance and locks?
I had a similar issue with "You are not authorized to perform the current operation" when publishing to a HTTPS destination. The form template was set to Full Trust (Central Admin Administrator Approved). However InfoPath wants to "see" that URL and confirm it's a valid destination.
I opened the HTTPS website in IE. By clicking "View Certificate" then "...
User form templates that contain code can be published by site collection administrations to form libraries as sandboxed solutions. For more information about sandboxed solutions, see Sandboxed solutions overview (SharePoint Server 2010). Form templates that require full trust or use a data connection that is managed by an administrator must be deployed by ...
At first, you need to install Office Pro Plus 2013 which includes InfoPath Designer 2013 (and InfoPath Filler 2013). For system requirements you'll need at least a 1 GHz processor and 1 GB RAM (32 bit) or 2 GB RAM (64 bit). And of course 3 GB HDD available space.
To start develop, there are numerous of guides available, but a good place to start is at ...
To change the default view for Infopath form do the following:
Open your list.
Click on your Item name field to edit your item.
The InfoPath Edit form should be shown > now go to Edit Page.
Edit the InfoPath form Web Part as shown below.
At view section, select your default view.
Note: whatever which way you are using to edit your item you should be ...
Here are answers:
Yes. Take a look at InfoPath 2010 Introduction Part 3: SharePoint Form Web Part
No. It is not logical. Maybe you can just hide your list from users (navigation) as simplest woraround.
Yes. Take a look at InfoPath 2010 – turn off Ribbon and then you need to add Submit connection and button for submit action.
You can create simple workflow using SharePoint Designer.
Your InfoPath form should contain field Manager and you should propagate it to SP when you commit your form. Your workflow can then read this value and use it to sen email to manager. You can use OOTB Modified by (Editor) column to determine person who submitted the form.
Your workflow can be ...
When you customize forms for a list or library, those forms simply replace or customize the current forms, the permissions are not affected. However, creating your own custom form that has nothing to do with a list that is already deployed can be affected in many ways. If the forms is deployed as a content type, then it can be used in any library that ...
There is no single answer here. Getting form design correct is really going to depend on the requirements. In some cases, designing a single list and customizing the form will be the answer for a small process. For larger processes, designing a form that is deployed as a content type in a site collection will work, for other cases, you will need to deploy ...
Open the InfoPath Form in Design view.
1) Go to Tools -> Form Options.
2) Select Category 'Open and Save'.
3) There is a section called 'Open behavior', where you can set Rules. These Rules are fired when the Form is opened. This is similar to Rules specified in "Form Load" option in InfoPath 2010.
I ran into something similar. The problem is that the InfoPath Form Template is under the element's sub-folder. You need to put the .xsn file in the same folder as Feature.xml. I could not find a way to do this using the SharePoint Project template in Visual Studio 2010. So I used a WSPBuilder project instead.
After spending much of today on the phone with Microsoft developer support, it turns out that this is a legitimate bug. It was fixed by the August 2011 cumulative update for SharePoint Server. Once I installed that successfully, the above error no longer occurred.
We had the same problem with InfoPath.
After analysis of servers,it turns out that the anonymous user authentication has been enabled on the web application server via IIS and not via SharePoint (unsupported configuration), causing side-effects on some queries which calls to forms.
We disabled anonymous access.This deactivation causes the functioning of ...
It seems Microsoft is not accepting feedback for SharePoint Server 2010. But, if you have MSDN subscription you can open the Support Case and report bugs to Microsoft. Depending on type of subscription, you get number of support cases you can open.
Each InfoPath form type has a different purpose and different restrictions related to that purpose.
There are (in general) three types of forms
First I will talk about what the restrictions are for each, and then how to use them
List Form: A list form is a SharePoint specific form meant exclusively for use to replace the ...
A bit late, but since the other answer was not terribly helpful, you can reference other classes and code in a separate strong-named assembly and include a reference to it in your project. The form's assembly may be fairly rigid, but you can always design around it. Build your other functions/classes in a separate VS project, deploy it as a SP solution, and ...
It is impossible to publish "Sharepoint List Form" compatibility/type Infopath template to more than one list
You can "centralize" and automatize (make a script at Windows level to a manual procedure I gave below) to restricting changes just to one template (in Infopath Designer 2010), and after making changes in one, to "replicate" the template's ...
While deploying your feature you need to change the scope of your feature(feature.xml) as web. So when you activate the feature it will be activated for that subsite only.
more can be found here: