Archive: Nintex for Office 365 Knowledge Articles

ISSUEWhen running a workflow that uses "Office 365 Upload File", the following error occurs:The file name already exists, or the folder could not be found, or the document library column could not be foundERROR CODEThe file name already exists, or the folder could not be found, or the document library column could not be foundRESOLUTIONReview the destination library on the SharePoint site and ensure that a file with the desired file name does not exist. If it does not appear in the SharePoint site view, use Windows Explorer to verify the file name is not in use. ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen publishing a Nintex Workflow the error "The workflow name is used elsewhere on this site. Please choose another name.” occurs.When looking through the site there is no existing workflow with the name that is being used when publishing. Error CodeThe workflow name is used elsewhere on this site. Please choose another name. ResolutionSolution 1.Empty the SharePoint recycle bin.Publish workflow.Solution 2.Log into the Site of the O365 tenant with SharePoint Designer.From the Objects tab in SharePoint Designer click Workflows.Find the Workflow with the name that you are wanting to use and delete it.Publish your workflow. Additional InformationThis issue can occur when a list has a Nintex Workflow published on it and the list is deleted without deleting the workflow from the gallery first.This same error will occur when creating a workflow with SharePoint Designer as the error is coming from SharePoints Workflow Manager and not Nintex. 

ISSUE When attempting to publish a workflow within the Nintex Workflow for Office 365 designer, the workflow fails to publish and the following error occurs in the designer: Error publishing workflow. Object reference not set to an instance of an object. ERROR CODE RESOLUTION From the ribbon within the workflow designer, open the Variables menu. Identify the variables with Initiation set to Yes that are of Integer type. If any of the identified variables are not currently in use, delete and re-create them.  Note: If this was all of the identified variables, you should now be able to publish successfully. If any of the identified variables are currently in use they will have to be manually updated within the workflow definition by Nintex Support. Export the workflow file and send it to support@nintex.com with the identified variables ADDITIONAL INFORMATION RELATED LINKS

IssueWhen using a Do Calculate action in Nintex Workflow for Office 365, it is not possible to add a decimal value greater than two characters. Resolution  Additional InformationThis is a known issue that is currently under investigation. 

IssueWhen building a conditional rule with a numeric value,  the rule does not work. For example a form with a rule such as: ControlName >= '25,000' can be submitted even when ControlName is greater than 25,000. ResolutionForm rules with number values should not include commas. Update the rule to just use integers. For example, ControlName >= '25000' 

IssueWhen double-clicking a control to open the Control Setting and Setting section located on the right side of Nintex Form Designer for Office 365, the control setting and setting section does not load or appears blank.  ResolutionReset the Nintex Form by clicking the "Reset" button in the Nintex Form Designer ribbon.  Additional InformationThe root cause is one of the control or rules or validation or formula is incorrect or corrupted.  

IssueWhen using a workflow that inserts data into a SharePoint List, the resulting data might contain an unexpected numeric value of 403. ResolutionUse {Current Item:Encoded Absolute URL} and update the user name and password with a Global account that has the correct permissions.  Additional InformationWithin the Web request the fir field URL {Current Item: URL} was being used. This was receiving a 403 forbidden error. 

IssueWhen running Nintex Workflow for Office 365, the following message appears in the Workflow status history page:Some parameters failed the validation check. - [InputDestinationSharePointUrl] : Destination URL is invalid ResolutionThe error is shown when the 'Destination site URL' field has either been entered in manually or copied and pasted from a similar account. To resolve the issue, you will need to do the following:1. Clear the existing text for the field 'Destination site URL'2. Place cursor in the 'Destination site URL' field3. Expand 'Workflow Context' section on the right4. Click on 'Current site URL' to add this information to the 'Destination site URL' field 

IssueWhen viewing a form, check boxes in the list lookup column might appear blank when no other changes were made to the form.Resolution1. Upgrade to the newest version of Nintex Forms.2. Test the same list again after upgrading.

ISSUEConnection manager window stuck at loading when creating a new connection.ERROR CODERESOLUTIONAdd the below url to trusted sites in Internet Explorer options. https://*.sharepoint.com https://*.nintex.io https://*.microsoftonline.comADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen using OKTA authentication, the following error occurs for Office 365 Live actions:Error: Direct login to WLID is not allowed for this federated namespaceERROR CODEError: Direct login to WLID is not allowed for this federated namespaceRESOLUTIONNintex does not support OKTA Single Sign on Provider. Use @on.microsoft.com account to resolve this issue. ADDITIONAL INFORMATIONRELATED LINKS

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(); });   

IssueWhen creating a Connection in the Nintex Workflow Gallery in Office 365, an error window appears with:“Error creating connection. Bad Request - {"correlationId":"00000x0x-0000-xx00-x00x-00000x0000xx","code":"CM-ERR-00005","message":"Incorrect or incomplete input data. [WebTitle]","_links":null,"_embedded":null}”  Resolution-In Office 365, navigate to the App Launcher (dotted square in the top left corner) > Admin-You are now in the Microsoft 365 Admin Center. Click the > in the top left to expand the menu-Navigate to Admin Centers > SharePoint > Site Collections-Locate the Site Collection in which you are making the Connection to-Select the site and open the Properties for the site-Ensure that the 'Title' field is populated. If this is blank, you must enter a title.  Error Code“Error creating connection. Bad Request - {"correlationId":"80003c4f-0003-df00-b63f-84710c7967bb","code":"CM-ERR-00005","message":"Incorrect or incomplete input data. [WebTitle]","_links":null,"_

IssueWhen creating a form in Nintex Forms for Office 365 designer, using Chrome browser, and clicking the Create Column icon from the ribbon, the dialog window to create the column is blank. ResolutionUse another browser, such as Internet Explorer or Firefox. Additional InformationThis issue occurs due to an update in Chrome: Version 60.0.3112.113 (Official Build) (64-bit) 

IssueWhen execute the workflow with a Send an Email action configured with body of email  to get the information from User Profile properties, this error might occurs:RequestorId: xxxxxxxx-xxxx-xxxx-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}} ResolutionGrant permission to the user profile service Error CodeRequestorId: 6fbca847-0c8a-0cde-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}} Additional InformationAccess to the User Profiles service is required for use of the following manager references in workflows.Manager displ

IssueWhen trying to save or publish a workflow in Nintex Workflow for Office 365, the following error occurs:Cannot connect to the workflow manager to check the name of this workflow. (Access denied. You do not have permission to perform this action or access this resource.) Error CodeCannot connect to the workflow manager to check the name of this workflow. (Access denied. You do not have permission to perform this action or access this resource.) ResolutionRemove and re-add the Nintex Workflow for Office 365 Apps.   Related LinksHow to add and remove the app 

IssueWhen using a Responsive Task Form in Nintex Form for Office 365, with a disabled single line text control that has a number value, the number is divided by 1000 during task form submission. This issue only occurs if the control disabled is via control setting. For example: Initially the value on this single line text control is 5000, and since this control is disabled, via control setting, when the user opens the Task Form, the user is unable to modify the value. The user then chooses the Outcome of the Task and clicks Submit. As the result, now the single line text control value is changed from 5000 to 5.  ResolutionDisabled the control via Rule and not via control setting. 

IssueWhen using Web Request action in Nintex Workflow for Office 365 to create CSV file, the newline / break line character has not been included in the CSV generated. Example: Workflow variable input: Item 1, AbcItem 2, DefResult: Test1,Abc Test2, Def Expected Result:Item 1, AbcItem 2, Def  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 using the 'Start Workflow' action in Nintex Workflow for Office 365, the following error may occur:A workflow is currently running. Please wait for it complete ResolutionEnsure that there are no other workflow instances running for the same item. 

ISSUEWhen a workflow uses the Send An Email action and sends the email via the External Email and Attachment option, the email never arrives at the external email.ERROR CODERESOLUTIONVerify that the email can be sent to via an email service outside of Nintex Workflow. Verify that the email can be sent to via an email service outside the corporate environment. Verify that "noreply@workflownotification.com" has not been blacklisted for that email environment. If the issue persists contact support@nintex.com and ask to verify the domain has not been restricted for the external email service.ADDITIONAL INFORMATIONRELATED 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

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. 

IssueThe below error occurs when attempting to publish a Nintex workflow that contains a conditional start event.Error message:Error publishing workflow. Conditions could not be published and the workflow will not be able to start conditionally. Please try publishing again. ResolutionPublishing a Nintex conditional workflow will use 1 subscription per published workflow. SharePoint only allows 100 subscriptions on a custom list and it is possible that the list has reached the maximum number. Other third party products can also use subscriptions for example Microsoft Flow.Options:1. Recreate the SharePoint list.2. Contact Microsoft Support to assist with removing subscriptions from the SharePoint list. Error CodeError publishing workflow. Conditions could not be published and the workflow will not be able to start conditionally. Please try publishing again. 

IssueWhen trying to add an attachment into a form within a workflow in Office 365, the new comments don't appear and delete that comments that appeared in the comment history section that appeared before. ResolutionResolution steps:1- Go to List Settings2- Choose the column "multiple line of text" type and change the "Append Changes to Existing Text" into No in order to avoid clearing off any comments and/or attachments added.  

IssueWhen configuring the Nintex Sign powered by Adobe Sign action, and setting the Identification Authentication type as equal to "Adobe Sign", the following error may occur:Bad Request {"message":"This workflow does not permit including yourself in some fields"} ResolutionWhen using Identity Authentication as Adobe Sign, you need to have at least 1 Recipient that is not the same account as the account used to create the connection in the Nintex Workflow Cloud (NWC) and not the field Initiator in the Nintex Workflow for Office 365For example:The account used to create or connect to Adobe is AdobeUser@nintex.comThen, the recipient cannot solely be AdobeUser@nintex.com, you need to add at least another 1 recipient that has different email addresses.