Solution showcase: Learn how to use Nintex CE Platform
This section contains archived Nintex for Office 365 Knowledge Articles.
Recently active
IssueWhen receiving task email reminders that contains variables in the body of the email, the HTML code <href=> is displayed between the variables. ResolutionDelete, and then recreate the action in the workflow. Additional InformationThis issue occurs when content is copied and pasted from existing actions.
IssueWhen using Google Chrome version 72 (was released on the 29th of January 2019), the Nintex Task Form cannot be modified in the Responsive Form designer. As well as: To Add a new control onto Nintex Task Form Designer. Drag and drop controls in the Nintex Task Form Designer. ResolutionClose all instances of the Chrome browser. Navigate to the directory where the Chrome browser has been installed. This is either C:Program Files (x86)GoogleChromeApplication or C:Program FilesGoogleChromeApplication. . Then Run the following command from command prompt: - chrome.exe --disable-features=VizHitTestSurfaceLayer,VizHitTestDrawQuad,VizDisplayCompositor Additional InformationThe Chromium team has confirmed this issue on Google Chrome version 72 and they are working towards a permanent fix for the next released of Google Chrome.
IssueWhen using a Nintex Form to edit Properties of a Document inside of a Document Set, you are presented with "Sorry, something went wrong - An Unexpected Error has occurred" upon submission. The changes to the document's properties are still properly saved. ResolutionThis issue was resolved in the February 2019 update for Nintex Forms for Office 365.
IssueNintex Workflow Office 365 - Set Workflow status action not showing the status in the Document Library workflow name column ResolutionOpen the Document Library settings page : in the Versioning Settings, Require Check Out Make sure it is set to No in the library having the issue.
IssueWhen opening a Nintex Form for a List that has a special character in the title, The site navigation link, at the top left of the Form, displays an encoded list name. For example, the list name is Nintex@List, the site link navigation shows Site > Nintex%40List instead of Site > Nintex@List. ResolutionThe issue has been fixed on the latest version of Nintex Form for Office 365, that has been released at the end of August 2018. Make sure that the site has the latest version of Nintex Apps.
IssueAfter adding a confirmation message within the Advanced section inside of a form control configuration, the confirmation message fails to appear on button click. ResolutionEnsure that there are no special characters in the confirmation message. This will include characters such as apostrophes (‘).
IssueWhen attempting to delete a workflow in SharePoint Online, the workflow does not delete and the page displays "Deleting Workflow..." indefinitely. ResolutionThis issue can occur if there is a retention policy in place. Adjusting the retention policy will allow the workflow to be deleted.If adjusting the retention policy does not resolve the issue contact Microsoft Support for troubleshooting and resolution. Additional InformationNintex does not have access to the SharePoint infrastructure for SharePoint Online and cannot troubleshoot or resolve this issue. Related LinksOverview of retention policies
IssueWhen running a workflow that contains a run-if action, the workflow might fail with internal status errors describing issues with boolean operator. ResolutionOpen the failing Run-If action. Select a different field in the list lookup. Save the action. Open the failing Run-If action again. Select the Yes or No choice field. Enter 'Yes' or 'No' in the value filter.
IssueIf you open a Nintex Form for a SharePoint list and try to paste content into a Multi-Line text field it works in Chrome, but fails in IE11. Changing to compatibility mode does not resolve the issue. ResolutionVerify the ‘Allow Programmatic clipboard access’ in Internet Explorer is set to Enable or Prompt? Internet Options > Security > Internet > Custom level… Settings are shown below.
IssueThe Nintex Workflow and Forms designer and apps do not load when attempting to open them. ResolutionThis suggests that the 'link' between the site and the app has been broken. To resolve this: Uninstall the Nintex apps from the impacted site. Install the apps again. No workflows or forms will be lost due to this reinstall.
IssueWhen using the Office 365 Create Site action, the site is created, however the workflow suspends with the following error:Failed to resolve owner: <user name> ResolutionRemove the user or group from the Site Owner's section within the configuration of the Office 365 Create Site action, and then re-run the workflow.
ISSUEWorkflow suspends when using the "Query List" or "Office 365 Query List" actions to query a list that contains more than 5000 items. ERROR CODEThe attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator. RESOLUTIONIn an effort to increase the performance of the query, create an index on the list column on which the filter is being applied. 1. Identify the column which the query is being filtered on 2. On the list which is to be queried, navigate to List Settings > Indexed Columns (located under the list of all list columns) > Create a new index. 3. Select the previously identified column in the drop down menu for 'Primary column for this index'. Click 'Create'. 3. Execute your workflow and check the results in the workflow history.Note: The result below is from a 'Log in History List' action capturing a variable that contains the number of items returned from the query. This will not appear by default. ADDITIONAL INFORMA
IssueWhen opening a Nintex Form using Incognito mode in Chromium based browser (Chrome browser or Chromium based Edge),this following error may occurs in Developer tools:Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document. ResolutionThis exception is thrown when the "Block third-party cookies and site data" checkbox is set in Content Settings. This needs to be disabled or an Exceptions needs to be added to the Sharepoint site.To find the setting, open Chrome settings, type "third" in the search box, click the Content Settings button, and view the fourth item under Cookies. Related LinksPlease see the original site for further details:https://www.chromium.org/for-testers/bug-reporting-guidelines/uncaught-securityerror-failed-to-read-the-localstorage-property-from-window-access-is-denied-for-this-document
ISSUEWhen loading a Nintex Form, the following error occurs, even though app is already up to date:The app Nintex Forms for Office 365 is out of date. Please update the appERROR CODERESOLUTIONCheck the Javascript on the form to ensure that all parentheses () and brackets {} have been closed.ADDITIONAL INFORMATIONWhen a parenthesis or bracket is not closed it breaks the formatting of the form and the form fails validation. Ensuring all brackets and parentheses are closed properly in the Javascript should resolve this issue.RELATED LINKS
IssueWhen clicking a submit button that has a redirect URL configured, the following error may occur: Server Error in '/' Application. ________________________________ Runtime Error Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated. ResolutionVerify the button configuration for 'redirect URL' value is in plain text and does not have a hyperlink URL. For example:Valid value: https://site_url/siteAInvalid value : https://site_url/siteA
IssueWorkflow gets stuck when trying to create documents using custom templates with Create List Item Or Document Set Action. ResolutionSave and close the template document if it has been opened from the SharePoint library. Otherwise this will cause the workflow to become stuck and not progress as the template file is still open by a user.
IssueNintex Workflow for Office 365 is does not load and shows a spinning circle.Furthermore from the Browser Developer Tools (F12)> Network tab, the following error may appear:Field type [field name] is not installed properly. Go to the list settings page to delete this field ResolutionVerify if the "Field type" mentioned on the error message exists and delete it as per error message advised. Contact Microsoft Support for guidance if you are unable to find or for any further details regarding the mentioned "Field type". Additional InformationThe field type mentioned does not belong to Nintex, therefore contacting Microsoft Support is recommended.
ISSUEWhen attempting to publish an Office 365 Nintex workflow, the following error might occur: Error publishing workflow. Column ' ' does not exist. It may have been deleted by another user.ERROR CODEError publishing workflow. Column ' ' does not exist. It may have been deleted by another user.RESOLUTIONExport the workflow file, and then re-import and publish the workflow to recreate the missing columns.ADDITIONAL INFORMATIONThis is caused by a conflict between an open InfoPath Form, and Nintex workflow designer. If there is a published InfoPath form, and the InfoPath designer is not closed while workflows are published and run; InfoPath cannot reconcile the list columns held in memory, and the list columns created through the new workflow, and as such removes the list columns from the SharePoint list. The deletion of the columns results in the workflow no longer being able to publish, throwing the error above. To avoid this, please make sure that InfoPath is closed when publishing
ISSUEWhen opening Nintex Forms, the following error occurs:Index was outside the bounds of the arrayERROR CODERESOLUTIONReview all site column names and remove any special characters, for example: / : * ? " # % < > |, two consecutive periods (..), or special characters such as a tab.ADDITIONAL INFORMATIONRELATED LINKS
IssueWhen a document is uploaded in a document library with Nintex forms, the browse button is missing from the managed metadata field. ResolutionThe Manage Metadata control does not support browsing MMD terms when the item is opened in the pop up dialog mode. Workaround On document upload in a document library that has Nintex form published pop up dialog for new form is missing the browse feature for MMD control as it is not supported. Instead use the free text search functionality by typing the required term in the MMD field. Alternatively use the "Modern SharePoint UI" as "Modern SharePoint UI" does not open the new form in a dialog.
IssueWhen using a Lookup control as the 'value to filter on' within the Lookup runtime function of a Calculated Value control, the Calculated Value control returns a blank value, even when the function works as expected with a hard-coded value to filter on. ResolutionNest the Lookup control reference within the Lookup function inside of a parseLookup runtime function. For example, instead of this function:lookup("list title", "column to filter on", value to filter on, "output column")Use this:lookup("list title", "column to filter on", parseLookup(value to filter on), "output column") Additional InformationThis is caused by the fact that Lookup controls do not actually return the value shown within the control. If the item 'Testing' was selected within a Lookup control, and 'Testing' has an ID of 3 on the source list, the Lookup control would return the following: 3;#TestingThe parseLookup runtime function parses out the Testing portion of that output, which in turn can be used as a r
IssueNintex Forms for Office 365 is loaded multiple SharePoint sites, it is currently working on every site apart from one. For the one site that Nintex Forms isn't working on, previously the forms designer would load, allowing forms to be created or edited but now just spools at "Obtaining License". ResolutionWhen troubleshooting options have been exhausted, the best course of action is to remove the Nintex Forms app, and re-add it on this site. Additional InformationWhen troubleshooting, creating a new list on the same site and opening the forms designer changes nothing. Removing the app won't delete the forms, however they will be unpublished. They'll be saved on their respective lists, but you will have to manually republish all forms on each list (including task forms inside of workflows). When you have removed the app and attempt to add it again, if you see a second "ghosted" version of Nintex Forms for Office 365 still in the process of removal, stop the new app from installing
Issue"Access denied: Connection does not have access error" when configuring an action using a Connection in Office 365. Error Code"Access denied: Connection does not have access error" Resolution Connection type Minimum permissions SharePoint Online: List & library SharePoint - Designer SharePoint Online: Site & user administration Full SharePoint Online: Site collection administration SharePoint - Global admin SharePoint Online: User management SharePoint - Global admin Nintex Connector - Azure Directory Admin consent required Azure AD app permissions: Read all user's full profile Read all user's basic profile' Nintex Connector - Azure Directory Administration Admin consent required Azure AD admin account required to make connection Azure AD app permissions: Read and write all users profile Read and write directory data Additional InformationThis table is summarized fo
IssueWhen attempting to grant access to a workflow from within SharePoint Workflow designer for Office 365, the following error message appears: "Something Went Wrong" ResolutionPlease follow the steps below:1. Navigate to the site URL that you are trying to trust ( e.g. https://m365x314721-cdad5d5d9abf7d.sharepoint.com/sites/HR2) 2. Navigate to Workflow App ID from Site Setting > App Permission. We need the App ID from the Workflow and NOT the Nintex Workflow. The app ID is between ms.sp.ext| and the @ symbol, for example: db8f9118-29ec-4d64-8630-521df24c9f32 (please double check and copy paste the value to make sure it is as expected) 3. Once we have the URL and the App ID, add them to the below URL, replacing the values SiteAddress and AppID with respective values.: {SiteAddress}/_layouts/15/OAuthAuthorize.aspx?client_id={AppID} &scope=AllProfiles.Read&response_type=code 4. Following the example above the combination between site URL and app id it will look like this (pl
IssueOffice 365 Nintex workflows are triggering multiple instances. ResolutionOpen the Nintex workflow causing issues in the Nintex Workflow designer. Navigate to the workflow settings in the designer ribbon and check the workflow start conditions. It possible the workflow is configured to start when a item is updated or when a specific condition is met. The workflow is most likely meeting multiple start conditions, causing the workflow to trigger more then once. Example: The workflow is configured to start when a item is created or modified. The workflow starts and the first action performs an update to the current item. The update causes the workflow to start again based on the workflow start conditions. The workflow start conditions need to be adjusted or the workflow design changed.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.