Archive: Nintex for Office 365 Knowledge Articles

IssueWhen opening the Nintex Forms Designer there is no option to select New Responsive Forms. ResolutionNavigate to site contents in classic mode and look for the Nintex Forms application.If there is an update available perform the update and test.If the issue persists, remove the Nintex Forms application from the site and then add it back again. 

IssueWhen using LazyApproval with Nintex for Office 365, if the task assignee has an 'out of office' response, the LazyApproval system sends a second email saying that their response was not valid.  ResolutionThis is currently expected behavior within Office 365, as LazyApproval within Office 365 currently does not support LazyApproval. There is a feature request for this functionality which can be found here. 

ISSUE When attempting to copy a document to a subsite using "O365 Upload File" within a workflow the following error might occur:   Details: ServiceNoResponse Description:The list ‘xxxx’ does not exist in web site ERROR CODE RESOLUTION Verify "Destination site URL" is set to the Subsite URL Verify the user has the appropriate permission to the list Verify that the Folder path exists Save and publish the workflow  ADDITIONAL INFORMATION RELATED LINKS

IssueError "Something went wrong. We're sorry. There is a problem loading the license" when try to open a New Responsive Form runtime using IE 11 and Windows 7.  ResolutionUse Chrome or Firefox to open the New Responsive Form in Windows 7 or Windows 8.   Additional InformationThe New Responsive Form does not support IE 11 for an Operating System older than Windows 10.     

ISSUEWhen completing a Nintex Task Form associated with a Nintex Workflow, SharePoint displays the error message "Unexpected error occurred."ERROR CODEFrom the GUI: Unexpected error occurred. If the problem persists, contact your support team with the following information: Correlation ID: xxxxxx Tenant ID: xxxxxx Time (UTC): YYYY-MM-DD HH:MM:SS From Logs: - Task Outcome Control 'outcomeCtrl' is not found in form - Nintex.Forms.SharePoint.Exceptions.UserException: Error in task. Input string was not in a correct format. - Exception caught by error page. => Nintex.Forms.SharePoint.Exceptions.UserException: Error in task. Input string was not in a correct format. - Application_Error => System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown.RESOLUTIONMake sure the task form has the "Task Outcome" control present or SharePoint will throw an error message when closing the form.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen attempting to use normal buttons instead of radio buttons with Task Forms, you will get the following error when submitting task:"Error in task. Input string was not in a correct format"ERROR CODE"Error in task. Input string was not in a correct format"RESOLUTIONThis feature is currently not support. However you may wish to vote this feature on our UserVoice page.ADDITIONAL INFORMATIONRELATED LINKS

IssueA blank page appears when accessing the Workflow gallery in Nintex Workflow for Office 365 using Internet Explorer 11 however with all others browsers there are no issues. ResolutionUsing Internet Explorer press F12 to bring up developer tools. Click on the Emulation tab (or Ctrl +7). On the menu bar, click on the Emulation icon along the right. Change the current setting to 11 which is generally the default option. 

IssueA calculated value control is put onto a form and configured but when the form is viewed in any mode the control does not appear. ResolutionIn general this issue occurs when the syntax of the formula is not correct in controls configuration.An example is:Bad:= Qty*CostGood:Qty*CostThe equals sign is not required and will cause bad syntax and the control may not appear at all instead of showing #Value error. 

IssueWhen opening the Nintex Workflow designer within Office 365,  there is a red bar displayingError Connecting to the Workflow Manager: undefinedOr:Error Connecting to the Workflow Manager ResolutionOption 1 Add the following to the trusted sites for the browser: *.nintex.com *.sharepoint.com  Deactivate and Reactivate the "Workflow can use app permissions" site feature.  Ensure the user account has the appropriate permissions to access the designer.Option 2Contact Microsoft SharePoint Support to resolve the underlying connection error between the site and SharePoint Workflow Manager. Additional InformationIf the above doesn't work then please try the following steps in the link below:https://community.nintex.com/t5/Technical-Issues/Enable-SharePoint-2013-workflows-in-Sharepoint-Online-Office-365/ta-p/86006 

ISSUEWhen opening a Nintex Form with a calculated control and a IF runtime function, the following error occurs:An embedded page at formso365.nintex.com says The form is reporting the following Errors: If is not definedERROR CODEIf Is Not DefinedRESOLUTIONThe IF function is a native SharePoint function. Contact Microsoft support for issues related to native functions.ADDITIONAL INFORMATIONThe following steps can be used to verify that issues with the IF function are not specific to Nintex Forms:On the affected list, create a calculated column on the list. Add the following formula: =if(1>2,"true","false") If this fails, it indicates a site-wide issue with the IF function.RELATED LINKSCalculated Field Formulas

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 saving a workflow, or configuring workflow actions, in Nintex for Office 365, using Edge browser, the following error occurs:Email = dispose : TypeError: Object expectedERROR CODERESOLUTIONUse a different browser. For more information, see Nintex Forms Supported Browsers. ADDITIONAL INFORMATIONEdge is currently not a supported browser.RELATED LINKS

ISSUEWhen a Nintex Form uses the Attachment Control, and a user goes to add an attachment, the control will not load as expected. RESOLUTIONCheck to see if there are any rules on this form.  If so check if there are duplicated rules (same formulas).  This issue is caused by inserted references being copy/pasted to the formula instead of being properly inserted by double clicking the desired references on the sidebar. Check to see if there are any calculated value control on this form. If so check if the formula of the calculated value controls are written correctly.  This issue is caused when assigned a formula to one of the item properties with Equal sign (==). Equal sign is only use if there is comparison between 2 values.  Delete the control and re-add it. ADDITIONAL INFORMATIONWhen references are copy/pasted instead of properly inserted, the unique ID for the control is not properly stored in the XML and thus may cause adverse effects.  In this instance, it broke the Attachment con

ISSUEWhen publishing a workflow, the following error might occur:Error publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverERROR CODEError publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverRESOLUTIONRecreate the Query List actions in the workflow. Republish workflow.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen generating a document using Nintex Document Generation action, and a tagger of a workflow variable with a name containing a space. The document generated has an empty value instead of the variable value. For example, the variable name is Var Title.  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. 

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 saving or publishing a workflow that contains a State Machine action, the following error might occur:Error publishing workflow. Object reference not set to an instance of an objectERROR CODERESOLUTIONConfigure the State machine action and at least one of the branches. Note: After the workflow has been saved, the branch configuration can be cleared.ADDITIONAL INFORMATIONExclamation marks on State machine ActionRELATED LINKS

IssueWorkflows within SharePoint Online will randomly suspend or terminate, and within the Instance Information panel (accessed through the blue 'i' on the Workflow Status page) is the message: 'HTTP status code 429' ResolutionReduce the number of requests that are being made into the SharePoint Online environment by the workflow Review Handling Workflow Throttling  Error CodeHTTP status code 429 Additional InformationMicrosoft's documentation on avoiding workflow throttling within SharePoint Online 

IssueWhen selecting a date from the Date Time control on a Classic Form in O365 and the mouse wheel is scrolled without choosing a date the date time picker popup will detach from the control and move up and down the screen as the user is scrolling ResolutionThis is a known issue of JQuery UI which is used in Nintex Forms for displaying the calendar control. The workaround for this issue is to hide the date picker popup on scrolling by adding the below custom JavaScript in the Form Settings. NWF$(window).on('wheel', function(event) { NWF$.datepicker._hideDatepicker(); });   

QuestionWill Microsoft change MC222880 affect Nintex forms for O365. AnswerMicrosoft is releasing a change that will affect classic form customizations in modern lists and libraries. This change will not affect Nintex Forms for O365.      

ISSUEWhen attempting to email a shared mailbox via an Office 365 Nintex Workflow the 'Send Email' action is unable to resolve the Shared Mailbox account.ERROR CODERESOLUTIONCheck to see if the email account can receive emails from a different source e.g. Gmail. If the shared mailbox can receive email, then utilize the 'External Email & Attachment' option. If the Shared Mailbox was setup and configured as an Office 365 Shared Mailbox then emails should be received with both options.ADDITIONAL INFORMATIONRELATED LINKS

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 open a Nintex Form for Office 365 (both Classic or Responsive), this error might occur:This site can't be reached ResolutionOpen the Nintex Form for Office 365 from a Private Browser. 

ISSUEWhen opening the Nintex Form for Office 365, the following error may occur: The given key was not present in the dictionary. ERROR CODERESOLUTIONVerify that the SharePoint Online List / Library setting for the Lookup data type column has a valid reference to the other List.ADDITIONAL INFORMATIONWhen creating a SharePoint List / Library from a list template, the reference for the Lookup column might be lost. RELATED LINKS

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