Archive: Nintex for Office 365 Knowledge Articles

ISSUEWhen saving a Nintex Workflow in Office 365, the following error might occur: Variable - dispose : TypeError: Object expectedERROR CODEVariable - dispose : TypeError: Object expected errorRESOLUTIONAs a tenant administrator, click the gear icon on the top right of the Nintex Workflow Designer window. Click Grant Access to Workflow.ADDITIONAL INFORMATIONFor more information, see Assign a task action for Nintex Workflow for O365 throws error on save.RELATED LINKS

IssueWhen updating a personal connection in Nintex Workflow for O365 the new password is entered and saved but the "Last modified" date on the "Available Connections" page is not updated and neither is the password. Resolution1. Make sure that the user who owns the personal connection is logged in.2. Use Internet Explorer to do the update.3. If another browser is being used make sure the user is logged in properly especially when using Multi Factor Authentication. 

IssueTask actions showing the warning sign that the action is not configured correctly Resolution Confirm that all mandatory fields have been completed.If the action is sending an email, check the email body and confirm that any references used are being resolved and not appearing as {Unknow: Unknow}  

IssueWhen trying to export a workflow from the Nintex for Office 365 designer, the export fails with the error: "Workflow is too big, please reduce some of the actions." ResolutionRemove an disabled/un-needed actions Break the workflow into smaller parts and export the new child workflows  Error CodeWorkflow is too big, please reduce some of the actions. Related LinksSharePoint Workflow Thresholds 

Issue When creating a Excel Spreadsheet, using a Create List Item action, the Excel spreadsheet does not open, and shows the error:"We are sorry, we could not open your workbook. It's possibly corrupt or using a file format that is not supported."  ResolutionThis is an underlying issue with the Sharepoint platform and also occurs with a Sharepoint Designer Workflow action: "Create List Item"As an alternative, use the O365 action “Office 365 Upload File" 

TopicWhen using a Web Request action an error may occur when running the workflow. SolutionSome web services or API's do not require a Body in the request as all information is passed in the URL but the Web Request action does need something in the Body even though this section of the action configuration is not starred as mandatory. Adding the content type to the field will resolve the issue even though the content may be ignored by the web service or API. Additional InformationIn general, any error in O365 that has a field name in between square brackets e.g. [Field] means there is an issue with that field.  Sometimes the field name is obvious and other times it is not. Read the error to determine the issue.  In this example the field is empty "null" but other errors may be in regards to the syntax of the information provided in the field. Error MessageSome parameters failed the validation check. - [InputFileContent] : The parameter or the parameter value is null. 

TopicWhen trying to open the workflow designer in SharePoint Online, it gets stuck loading on 'Connecting to site'.  InstructionsIn Google Chrome:1. Navigate to Settings > Privacy and security > Cookies and other site data.Note: You will find that Block third-party cookies or Block third-party cookies in Incognito are enabled. This prevents the Workflow Designer from loading.2. To allow the Workflow Designer to load, make one of the following changes:Select Allow all cookies Under Sites that can always use cookies, add [*.]sharepoint.com  Additional InformationWhile it is possible to see this occur in other browsers with similar cookie-blocking features, this most commonly occurs in Google Chrome Incognito mode. 

IssueWhen click a Save button in Nintex Form for Office 365, the Form is submitting an HTML string to one of the list column that has data type string and has a default value.   ResolutionVerify the control setting button and make sure the configuration of Advanced > Connected to is Not Connected.  

IssueAfter enabling Conditional Network Access for SharePoint Online, the Nintex Workflow and Nintex Forms for Office 365 apps will fail to function as expected:Nintex Forms presents: Error (401) Nintex Workflow presents: Oops something went wrong.  ResolutionWith Conditional access enabled apps will need to be whitelisted.Please enable the following for Internet explorer:.*.nintex.com .*.sharepoint.com .*.nintexo365.net.On SharePoint Online please whitelist the following IP's:https://www.microsoft.com/en-au/download/details.aspx?id=41653 

IssueEven though reminders have been set for Start a Task Process action, the notifications are not being receive. ResolutionTo receive task reminders with Nintex Workflow for Office 365, you need to set the Due Date within the action configuration. If the Due Date is blank the reminders will not be sent as the workflow wouldn't know when the Task is due is actually due. Additional InformationYou can read further information and the Task action configuration options in the the help file below.Start a Task Process 

IssueSetting a date/time value to a date/time workflow variable outputs the wrong time at workflow execution. ResolutionThis is by design. SharePoint will adjust the time stored in the workflow variable to GMT (UTC+0), plus add time to account for daylight savings. SharePoint does not know the time zone of the date/time value being saved to the workflow variable, so the time is adjusted based on regional settings when used in a workflow. We recommend using the "Add Time to Date" action to adjust the date/time workflow variable to the correct time.  

IssueWhen using Quest's Mextalogix Essentials for Office 365, Nintex workflows fail to migrate with an "unauthorized" error. ResolutionEnsure that you have whitelisted https://nintex.onmetalogix.com. You can check the availability of this services URL by visiting https://nintex.onmetalogix.com/nintex/version, and you will see a result similar to the screenshot below:  

IssueWhen trying to update the Nintex for Office 365 apps from within SharePoint Online, the 'Get It' button is missing from the SharePoint Online Store page after selecting 'An update for this app is available.' ResolutionThe steps below are to resolve the issue for Nintex Workflow for Office 365, if the issue is also occurring with Nintex Forms for Office 365, please repeat them for that app as well:Open SharePoint Admin Center Select Apps > Manage Licenses > Nintex Workflow for Office 365 Under 'License Managers' select 'add manager' and add an active Admin account Return to the Site Contents and attempt to re-update the Nintex for Office 365 app Additional InformationIf there are expired/deactivated user accounts under License Managers it is recommended to remove these accounts from the list of license managers. 

IssueWhen using "Query List" action in Nintex Workflow for Office 365 and using the Filter current date variable that set up using "Add Time to Date" to compare with one of the current item list with data type is Date only, the result is null because the current date variable has a Date and Time instead of Date only.  ResolutionUser "Set Time Portion of Date/Time field" to get the current date and configured the hours and minutes of the action into zero (0).  

IssueWhen attempting to trigger a workflow either through the Start Workflow action, or by updating an item with a workflow, the "child" workflow fails with the error: HTTP Forbidden to https://SiteURL/_api/sp.utilities.utility.ResolvePrincipalInCurrentcontext...Access denied. You do not have permission to perform this action or access this resource.  Error Codehttps://SiteURL/_api/sp.utilities.utility.ResolvePrincipalInCurrentcontext?input=%27i%3A0i.t%7C00000003-0000-0ff1-ce00-000000000000%7Capp%40sharepoint%27&scopes=%2715%27&sources=%2715%27&inputIsEmailOnly=%27false%27&addToUserInfoList=%27False%27&matchUserInfoList=%27true%27 Correlation Id: d9b2fff7-fb3c-b3dc-823e-8cfb630f4c0b Instance Id: 9e6a7c9a-8a12-4f5c-813c-fcad6170b3dd  ResolutionActivate the Site Feature 'Workflow can use app permission'.

IssueUnable to access the existing connections with the account was utilized to create the connections.Error CodeOops! Something went wrong. Unauthorized access while getting connection list    ResolutionTo resolve the issue, re-trust the Nintex workflow app following the below steps: 1. Navigate to the site contents2. Switch to classic mode of sharepoint3. Hover over the Nintex workflow app and click on the ellipsis >> then next ellipsis and clcik on permissions4. On the last line, then click on here link to trust the app. Additional Information  Related Links  

IssueWhen trying to submit data using a New Responsive Form with Nintex Form for Office 365, the following error might occur:Invalid data has been used to update the list item. The field you are trying to update may be read only. ResolutionVerify that all the Lookup controls in the Form is connected to the List column. 

ISSUEWhen running a workflow that uses the "Start workflow" action to start another List workflow, the selected workflow does not start even though the master workflow does not return any error. ERROR CODERESOLUTIONConfigure "Workflow type" value in "Start workflow" action with "List Workflow". ADDITIONAL INFORMATIONRELATED LINKSStart workflow

IssueWhen configuring a form with rules that hide specific fields based on the status of a drop down, the rules do not function with the same behavior across multiple objects on the form. ResolutionEnsure that Inserted References in each rule have not been copied and pasted from another rule. Additional InformationBest practice for Nintex Forms rules is to manually insert every reference while writing a condition. 

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

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.