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
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.
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.
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 ...
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 "...
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 ...
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 ...
Yes, you are right. To work with MS flow and Power Apps, users need to buy licenses separately as described here for MS flow pricing, PowerApps pricing
For InfoPath alternatives, I would suggest you use PowerApps and Microsoft Flow. Otherwise, you could use some third party tools for form building. Refer to here for more:https://techcommunity.microsoft.com/...
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 ...
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:
I know there is Form Library Settings > Advanced Settings > Open
Documents in the Browser > Open in the browser as the default
behavior. But this does not affect my form
There are 2 places for configuring this. One is that you mentioned and another is in
InfoPath Forms Services setting (using the Farm Administrators Sharepoint Group user):
I got the answer!!
You need to publish your form again and check the check box for editing the column data so you can edit that column in library!!
Once it's editable, just change the decimal points to Auto, 1, 2, 3, etc.
Entire script will be :
Replace the web url and list name
$web = Get-SPWeb http://whateverWeb
$list = $web.Lists[“List Title”]
$list.enablethrottling = $false
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 ...
InfoPath Designer is part of the Office suite. Depending on your Office license it will be included. To install it, just run the Office installer and make sure to select it as a component to be installed on your PC.
If you point your favorite search engine towards terms like "Infopath tutorial", you will find many, many materials on getting started.
You could replicate this functionality using a field within the form:
Some field: SubmitBool.
once the form has reached a state that a submission would be appropriate set the SubmitBool value to true, and have rules change behavior once the value has changed.
You could also do something along the lines of having a form status field,
ie: Status = Open/...
Yes, I faced the same issue, actually my InfoPath form was targeted to publish into Document Library instead if Form Library.
In your case i guess you are also doing the same mistake. You may have your published target wrongly specified.
Try de-activating and reactivating the "SharePoint Server Enterprise" features at both the site collection and the site level.
Try de-activating and re-activating "IPFSSiteFeatures" feature. It is a hidden site collection feature. We can do that with PowerShell.
The "IPFSSiteFeatures" feature id "c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5".
One of the prerequisite for publishing infopath is "enabling Desktop experience feature". As my dev server is a "Single farm server", I enabled "Desktop experience feature" and the publishing issues are resolved.
See the following Microsoft KB: support.office.com/en-us/article/-infopath-cannot-save-the-following-form-error-message-when-you-try-to-publish-...
As mentioned you are using the SharePoint library hosted form and want it to work properly on browser so please check compatibility settings for a form template
Compatibility Settings Article 1
Compatibility Settings Article 2
Compatibility Settings Article 3
browser compatible features has to be activated at the very beginning
Go to Tools > Form ...
If you're wanting to just compare values to make sure there are no duplicates among them, you could create a validation rule on each of the fields that compares the values of each of the affected fields every time the value changes, and throws a validation error if duplicates are found.
my guess is you wont be able to do this across versions ( not 100% sure on that ). you could change your submit type to use the list web service of the 2nd farm, that should work (depending on authentication configuration - read more below).
I think if you looked at Fiddler you will see authentication errors, I didn't think about it initially, When ...
I read somewhere that the problem is related to "Classic Authentication" (exactly i don't know where was it) , Try this one.
My apologies, this should be a comment, but I'm new to StackExchange and can't find the button for comments...
I can confirm that your .udcx file is correct - including the element. My .udcx file is identical, except for the server location - obviously. But RELATIVELY it is the same.
I've used Itay Shakury's method in the past, and just to confirm, I just ...