Troubleshooting Plumsail Forms for SharePoint Online in Microsoft 365
On this page, you will find information about most common errors with forms, and how to fix them. If you have any issues that you are unable to fix with this guide, please, contact us to get help with any question you might have.
Cannot start application
If you get the following error, saying that the application cannot start - you need to delete the ClickOnce file cache.
Trouble with the license
After trial period expires, you need to make sure that a subscription is purchased in our store and tied to the domain, this can be checked in the Plumsail Account:
If you’ve purchased a subscription, but it didn’t activate in the Plumsail Account for any reason, please, contact us with a receipt # at support@plumsail.com
If the subscription is active in Plumsail Account, but you still get the message that trial has expired, clear browser’s cache to update the license in SharePoint.
Trouble connecting to a site
Sometimes, you might get stuck at the login screen and there a few things that you can do:
If you try to connect to a site, but get stuck at a blank login screen, first try to sign out and sign in again:
If you can’t access the sign out button, try to cancel connection:
If it doesn’t help, try to clear browsing data by going to Control Panel > Internet Options > Browsing history > Delete:
Make sure to delete Temporary Internet files and Cookies:
This should refresh the page and you’ll be able to login again:
Note
There are still some authentication options which are not supported at the moment. We’re working on making all authentication options work with Forms.
Trouble signing out
If you can’t sign out of the account in the designer, you need to delete the SPDesigner.exe.WebView2 folder that holds cookies for the designer.
To find the folder, do the following:
start the designer
open the Task Manager CTRL+SHIFT+ESC
find the Plumsail Forms app and expand it:
right click on the Plumsail Forms app → Open file location:
the File Explorer opens; find the SPDesigner.exe.WebView2 folder and delete it:
re-start the desktop designer.
Trouble saving forms
You must always wait for this message to ensure that the forms have saved properly:
If you have troubles saving a form, there are a few possible reasons for this.
Disabled scripting capabilities
Scripting capabilities are disabled for the site:
To fix the error, do one of the following:
Update the app package and the desktop designer to the latest versions that don’t require enabling custom scripts.
Enable custom scripts with PowerShell commands.
Lacking permissions to save
If you get an error that you lack permissions to save form, you must ensure that you’re editing forms under a user with Full Control permissions to the currently edited list, as well as to the Site Pages library on the current site.
Trouble with outdated app package
There can be a variety of issues on your forms, if you’re using an outdated app package in the app catalog, check what version you have:
Many bugs are often fixed with its update, you can follow our guide to update the app package.
Trouble with custom JavaScript
Custom JavaScript is often the culprit behind errors when working with forms. Sometimes, you might have issues getting it to run properly, other times you might accidentally break with minor changes to the form. To find out if custom JavaScript is the culprit, check out browser’s console for errors:
The error like above indicates a custom JavaScript error. In this case, the most likely culprit is a missing field, or an incorrect field Name used in custom JavaScript when setting or checking field value. Use Names of the fields that are present on the form in your code:
To debug the code, we recommend removing parts and testing which part is broken, or using console.log() statements to see where you have missing values.
How to record console logs for support
If you have a problem that you can’t solve, we might need console logs to analyze what the issue is.
You can record console logs by opening browser’s console (use Shift + CTRL + J in Chrome or go into More tools → Developer Tools → Console) and right click inside the console, select Save as:
Send other screenshots and the detailed problem description to support@plumsail.com
How to record network logs for support
We might also need to analyze network requests. For this, open the Network tab in browser’s dev tools before opening a form and keep it open to record all the requests that are sent by the browser, then Save all as HAR file with content:
Send other screenshots and the detailed problem description to support@plumsail.com
Unable to retrieve client secret with msGraphClient in mobile app
If you’re trying to use msGraphClient in SharePoint mobile app, but get Unable to retrieve client secret error, the issue comes from the msGraph client itself, follow these steps to resolve it:
Visit the “Manage Permissions” Page in SharePoint Tenant Admin
Go to → https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredAppsPreview
Click on “SharePoint Online Client Extensibility” Web Application Principal
Click Manifest on the left menu
Copy the id from the oAuth2Permission array:
"oauth2Permissions": [
{
"adminConsentDescription": "Allow the application to access SharePoint Online Client Extensibility Web Application Principal on behalf of the signed-in user.",
"adminConsentDisplayName": "Access SharePoint Online Client Extensibility Web Application Principal",
"id": "2143704b-186b-4210-b555-d03aa61823cf",
"isEnabled": true,
"lang": null,
"origin": "Application",
"type": "User",
"userConsentDescription": "Allow the application to access SharePoint Online Client Extensibility Web Application Principal on your behalf.",
"userConsentDisplayName": "Access SharePoint Online Client Extensibility Web Application Principal",
"value": "user_impersonation"
}
],
Replace “preAuthorizedApplications” entry with the following JSON:
"preAuthorizedApplications": [
{
"appId": "00000003-0000-0ff1-ce00-000000000000",
"permissionIds": [
"2143704b-186b-4210-b555-d03aa61823cf"
]
}
],
Hit Save