Archive: Nintex for Office 365 Knowledge Articles

IssueWhen configuring the Document Generation action, the configuration indicates the document quota has been exceeded, even when no documents have been created. ResolutionContact Sales@Nintex.com. Have Sales verify that the 'Nintex for Office 365' asset and 'Nintex Document Generation' asset are active. If both assets are active, confirm that both assets are on the same contract. Even if both assets are created and live, if they're on separate Salesforce contracts, Document Generation for Office 365 will not work.   Additional InformationThis is caused by a mismatch in the licensing with the associated customer account.Looking at the JSON call that is made when the action configuration loads, you will see the following inside of developer tools: {"Total":0,"Used":0,"IsTrial":false,"SubscriptionStartDate":"0001-01-01T00:00:00","SubscriptionEndDate":"0001-01-01T00:00:00","OverUsage":0,"QuotaOverageAllowance":0,"ErrorType":400,"IsSuccess":false,"ErrorPayload":null,"Info":null,"Subscripti

IssueWhen trying to use any of the the Nintex Office 365 REST API functionalities, the API request will fail without having the tenants API key. ResolutionUse the API Key Request Form to obtain the necessary Office 365 tenant API key.  

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.  

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. 

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. 

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 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  

Issue When update a value to an a list column, you will get get the following error "A text field contains invalid data”   Resolution Your list column may be Single Line Text. When changed to Multiple Line Text the workflow will resume and complete as normal.  

IssueWhen using an Office 365 Upload File action to upload a file to the list that has a special character as the list name (i.e : (Nintex) List Sample), the following error may occur: The list '<List Name>' does not exist in web site '<Site URL>' ResolutionThe issue has been fixed on the latest version of Nintex Workflow for Office 365 Apps that is being released by the end of August 2018. Make sure that the site has the latest version of Nintex Apps.     

IssueWhen attempting to authorize with Nintex Sign, you receive the 'Oops something went wrong" error.In the Nintex Sign Authorization email, you see this URL for the link to authorize. ResolutionReview the Mimecast encoding/decoding settings. There should be a setting to adjust for specific URLs. Once this is updated, you will be able to access the correct URL. 

ISSUEWhen running a workflow that is configured to send an email, the workflow suspends with the following error: RequestorId: 6fdb72dd-529e-e60f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130242040, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."}}}ERROR CODERequestorId: 6fdb72dd-529e-e60f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130242040, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."}}}RESOLUTIONWhen trying to send to an email that is not associated with an account within SharePoint Online, ensure that t

ISSUEWhen attempting to run a workflow that was imported from another list, the workflow suspends part way through and the following error occurs:Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentNullException: Value cannot be null.ERROR CODERESOLUTIONWithin the actions inside of the workflow designer verify that all required fields still contain data. If any required fields are empty, re-enter the appropriate value into the field.  The action with the field in question can often be determined by specifics at the end of the the error message returned from Workflow Manager.ADDITIONAL INFORMATIONThis error can also present as "An unhandled exception occurred during the execution of the workflow instance" with no null value error.  In this case check the stack trace in the internal status to verify which action type is causing the error and verify that the references for those actions are not returning null values.REL

IssueThe Shrink and Expand button are disabled in the New Responsive Designer.  ResolutionThe Shrink and Expand buttons are only enabled if there is more than 1 control in the same row. The buttons are disabled if only 1 control in the same row.  

IssueWhen using the connection manager in Office 365 actions, this error may occur: The destination site was unable to process request. The provided credentials might not have access ResolutionReconfigure the connection manager and make sure that the credential used has enough permission to execute the functionality as intended. Related LinksConfigure a connection 

IssueDuring Runtime, when clicking a button in Nintex Form for Office 365, the button that has been configured with a 'Confirmation message' which contains an apostrophe " ' " character, will not return a pop-up dialog as expected. The Form will be closed immediately without a confirmation message.  ResolutionModify 'Confirmation message' for the button control, and for any apostrophes or any other special character add slash '' before the character. For example:Incorrect value: You've submitted the form. Correct value: You've submitted the form. During the runtime, you will receive this value: You've submitted the form. 

IssueWorkflows on a particular list are stuck on starting. Checking the internal status of the workflow instance shows the following error.Error: List data validation failed ResolutionCheck if any validation settings are enabled on your list. Navigate to list settings -> Validation settings. There will be validation rule associated to a list field causing the workflow to fail to update a specified field. Error CodeList data validation failed 

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

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

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. 

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

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 using fn-formatdate to format the date into a certain format, the runtime function will only work in the VIEW mode and doesn't work for in the NEW or EDIT mode.  ResolutionThis is by design, the fn-formatdate only works in the VIEW mode; in EDIT and NEW mode, the date format will follow the Site's Regional setting. 

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

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