-
- Adding Fields
- Adding and Editing Linked List items using Inline, Dialog & Sintel Forms Embedded
- Linked Lists-How to add attachments
- Linked Libraries-Using a Document/Picture Library
- Sections - Tab order
- Using a Linked List
- Field and Section Validation
- Creating Calculated Fields & using formulas
- Default values & custom values
- Setting field properties within a Linked List
- About Layout
-
- Import a form template
- Configure Printing Options
- Lookup Columns: Retrieve additional columns from Lookup List
- Use Sintel Embedded Mode on a linked list
- Automatically add linked items or files
- Lookup Columns: Control the sort order
- Share a Form
- Configure a cascading drop-down
- Change the layout of Choice Fields
- Make Attachments Mandatory
- Set & clear field values using rules
- Create a custom form header
- Export a form template
- Transferring your license to another tenant
- Debugging your forms
-
- Workflow emails not being received by distribution lists or mail-enabled security groups
- Changing the Content Approval settings of a list can cause an issue with Sintel Forms
- Site naming and Sintel Forms
- Workflow emails not being received by SharePoint group members
- Ad blockers and Privacy Extensions
- "500 internal server error" on form opening
- Attachments option missing in Sintel Forms
- "401 Unauthorized" error during form data save
- Sintel Forms doesn't appear to be applied to a list
- Handling the list view threshold for the Workflow and Conversations features
- No actions appearing in the actions menu
- Enabling third-party cookies
- Sintel Forms Save Process
Activating Sintel Forms on newly created tenants
Created On
Last Updated On
bySławomir Bryk
2.8 out Of 5 Stars
5 Stars | 50% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 50% |
You are here:
- Main
- Activating Sintel Forms on newly created tenants
< All Topics
For SharePoint tenants created after August 2020 it may be necessary to perform one extra activation step in order to use Sintel Forms. If that is the case, you will receive the following screen:
As described in this thread on Microsoft’s Q&A section, a SharePoint administrator needs to perform the following steps:
- Make sure that SharePoint Management Shell is installed
- If it’s installed, make sure that it is up-to-date (using the Update-module cmdlet)
- Connect to the tenant using the Connect-SPOService cmdlet
- Execute the following code: Set-SPOTenant -DisableCustomAppAuthentication $false
- Wait a few minutes for the changes to be applied to the tenant
Was this article helpful?
2.8 out Of 5 Stars
5 Stars | 50% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 50% |
Table of Contents