Contents
- 1 Can you call SharePoint REST services from InfoPath?
- 2 Why is my InfoPath form not showing in my browser?
- 3 Can you add a file to an InfoPath form?
- 4 Is the InfoPath form template unsupported in SharePoint?
- 5 Is the sandbox code service in InfoPath unsupported?
- 6 Why is InfoPath Forms Services a farm level feature?
Any call to a service that’s hosted on a SharePoint server will fail, except for the 10 web service calls that are listed in KB 2674193. SharePoint REST services can’t be called from the InfoPath client because the authentication is incompatible. Calling the built-in SharePoint REST endpoints is unsupported in the DvNext/MT environment.
Why is my InfoPath form not showing in my browser?
When you run an InfoPath form in the browser, you may receive the following error message: The form could not be displayed because default values or rules are taking too long to evaluate. To correct this, simplify the expressions or reduce the size of the data sets that they depend on.
What’s the difference between SharePoint and InfoPath forms?
The recommended resolution is to use the SharePoint List data connections. These let you apply a filter when you query SharePoint. When you add an attachment to a browser instance of an InfoPath form template that was published to a forms library, the attachment is embedded in the InfoPath XML file.
Can you add a file to an InfoPath form?
Therefore, adding a file that exceeds 5 MB as an attachment can adversely affect the performance of the form. This limitation does not apply to SharePoint lists that are customized to use an InfoPath form.
Calling the built-in SharePoint REST endpoints is unsupported in the DvNext/MT environment. Running managed code from an InfoPath form template is unsupported in the DvNext/MT environment. This isn’t specific to InfoPath.
Why is my InfoPath form not working in Office 365?
When you use an InfoPath form in the browser through Office 365, UDCX connections that contain explicit credentials or Secure Store Application details fail. This is because of the following InfoPath Forms Services options that aren’t enabled in the cloud:
Is the sandbox code service in InfoPath unsupported?
Calling the built-in SharePoint REST endpoints is unsupported in the DvNext/MT environment. Running managed code from an InfoPath form template is unsupported in the DvNext/MT environment. This isn’t specific to InfoPath. Support for the Sandbox Code Service is removed from the DvNext/MT environment.
Why is InfoPath Forms Services a farm level feature?
InfoPath Forms Services is a farm-level feature. The displayed options in On-Premises Central Administration can’t be changed in the DvNext/MT environment on a per-tenant basis. This is because modifications to these settings could affect other tenants in the farm.