Archive: Nintex for Office 365 Knowledge Articles

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 using Office 365 Upload File action to update a Person or Group field, the following error occurs: ‘Error performing Office 365 upload file activity. Reason: There was a service parameter validation error. Error: Some parameters failed the validation check.Validation error 1 - InputMetaDataXml. Reason: The 'Fields' is invalid.’  Resolution'Office 365 Upload File' action does not support update to a 'Person or Group' fields. As a workaround, utilise the 'Office 365 update items' action to update 'Person or Group' fields. 

IssueWhen a responsive form has a confirmation message and redirects to a specified URL, the form will hang when using the Save button within the ribbon of the form. ResolutionThis is a known defect with the current release of Nintex Forms for Office 365.Using the Save button on the form itself does not cause this behavior. 

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 a list, content type, site or site collection is deleted if there were Nintex Forms associated to any of the lists or content types etc they will still appear in the Nintex Mobile application. ResolutionFor Office 365 the local storage will need to be deleted from the settings in the Nintex Mobile Application and the forms re-downloaded.For on-premise installations the first thing to try is to find the form in the NM_Form table in the Nintex Forms database and change the IsDeleted column from 0 to 1.If the form still appears in the Nintex Mobile app the only other option is to delete the whole row in the Nintex Forms Database for the form. Additional InformationThe reason that this issue occurs is because Nintex is a third party application and SharePoint does not tell Nintex when one of its forms is deleted.To avoid this issue all together Nintex Forms should be deleted by opening them in the Nintex Forms designer and then clicking delete form before the SharePoint asset is

IssueWhen publishing a workflow that has a task action configured, in Nintex Workflow for Office 365, the workflow fails to publish and the following error occurs:Error publishing workflow. A duplicate content type "Nintex Task Outcome Content Type" was found.  Error CodeError publishing workflow. A duplicate content type "Nintex Task Outcome Content Type" was found. If the problem persists, contact Nintex support, and quote: Correlation ID: Tenant ID: Time (UTC): ResolutionOpen Site Settings and determine if a Nintex Task Outcomes content type is listed under both Nintex Forms for Office 365 and Nintex Workflow for Office 365. Navigate up to the site from which these content types are inheriting. This is likely the top level site of the Site Collection. Remove all of the Nintex Task content types.Note: This may require deleting workflow tasks from the Workflow Task list, these can be restored after the bad content types have been removed.Once all Nintex Task content types have been re

IssueWhen tying to publish a workflow within Office 365, the designer presents the following error after selecting Publish:Error publishing workflow. System.Net.WebExeption: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Error CodeError publishing workflow. System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack trace - ResolutionOption 1:If the site was recently migrated, please remigrate the site and that should resolve the issue.Option 2:If the site was not recently migrated, please contact M

IssueWhen opening a Nintex Form with a Lookup control, which allows multiple values from a Mac OS, it will render the Lookup control differently compared to the Windows OS.On the Windows OS, it will have two boxes with an arrow selection to choose multiple values and from the left box to right box.The Mac OS devices will render the Lookup control with only one box without any arrows to select the value and it will be moved from left side box to the right side box.   ResolutionChoose the multiple values in the lookup control by click Command + Click the value.  Additional InformationThe MacOs has a different way to render List Lookup control with multiple allow values allowed.  

ISSUEWhen lazy approval is utilized, the task in SharePoint stays in a "Not Started" status, and the workflow doesn't move forward. When attempting to approve the task again, an email saying, "This task no longer requires you to respond. The task has already been completed." is received.ERROR CODERESOLUTIONOpen the Existing Workflow. Click on the Workflow Settings. Scroll down to the Task List section. Select "create new" from the drop-down menu. Enter in the new task list name. Save the Workflow settings, Publish the Workflow.ADDITIONAL INFORMATIONRELATED LINKS

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.  

IssueWhen a Nintex Form List Lookup control is connected to a Single Lines of Text SharePoint column and an item is created using Quick Edit the control is blank on the Nintex Form. ResolutionThis is expected behavior.  Additional InformationWhen a Nintex Form List Lookup control is linked to a Single Lines of Text SharePoint column the ID of the looked up item is recorded in the Nintex hidden NFFormData column when the form is submitted.If the column in SharePoint is updated via Quick Edit or via a Workflow then the NFFormData column is not updated so it is not reflected on the form. 

TopicWhen attempting to add or upgrade Nintex Forms or Workflow for Office 365, the following message is displayed:"Sorry for the hassle, we hit a problem. click to recover your license"InstructionsA Tenant Administrator must renew the Nintex apps at the Tenant level:SHAREPOINT ADMIN CENTER MODERN VIEWAs a Tenant / Global Administrator, navigate to the Microsoft 365 admin center. Click on SharePoint. Click on More features. Click "Open" Apps. Click on More features. Click "Open" Site contents. Find the Nintex Workflow for Office 365 and or Nintex Form for Office 365 that has the issue > Click the 3 ellipsis button next to it. Click Manage License.  From the App License Management page > Click either Renew or Recover License. SHAREPOINT ADMIN CLASSIC VIEWAs a Tenant / Global Administrator, navigate to the Microsoft 365 admin center. Click on Apps Click on Purchase apps Find the Nintex Workflow for Office 365 and or Nintex Form for Office 365 that has the issue > Click the 3 ell

ISSUEWhen using an email action such as Send email or Assign Flexi Task, and using {Workflow Context: Current Item Url} in the body of the email, the hyperlink is broken in the email sent to the recipients.ERROR CODERESOLUTIONOption 1Remove any spaces in the list name and run the workflow. Option 2 Click on Insert link in the body of the email. Enter the URL { Workflow Content: Current Item Url}. Enter the hyperlink text  - "Hyper link text to be displayed in the email body".ADDITIONAL INFORMATIONDepending on the email client, this might be displayed as a clickable hyperlink. If there is a space in the link, then it might be broken after the space, if the email client cannot handle the space. Outlook will try to resolve this text as a URL, but Outlook Web Access will display it as text and not a URL.RELATED LINKS

IssueWhen Submitting a Nintex Form, the following error may occur: hexadecimal value 0x0B, is an invalid character ResolutionMake sure to type all the values for the Form. If the user requires to copy and paste the values from another source then please do paste the values into Notepad. After that, copy the values from the Notepad into the Nintex Form. Additional InformationThis error is because the submitted value contains a special or unknown character such as "[ ]" when a content has been copied from another source such as Words, PowerPoint, Website content, etc.  

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 hovering over a populated People Picker control in Nintex Forms for Office 365, the user account's information window appears, and then follows the mouse around the form instead of disappearing as expected. ResolutionIdentify the form rule that is disabling the People Picker control. Within the 'disable' rule, update the rules to include Is Edit Mode, for example: (Is Edit Mode)&&(State=="Completed"||State=="Waiting External Affairs Approval")  

ISSUEWhen accessing a Nintex form, the following error occurs:Unable to get property 'value' of undefined or null reference FormsPart.aspxERROR CODERESOLUTIONIn the FormPart.aspx JavaScript to get the value from the single line textbox control, locate the following line of code:NWF$(".option_crId_control .nf-filler-control-inner")[0].firstChild.dataAnd update it as follows:NWF$(".option_crId_control .nf-hidden-associated-control").val()ADDITIONAL INFORMATIONRELATED LINKS

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

ISSUEWhen opening or running a Nintex Task Form, the following error might occur:The form is referencing a field that does not exist. Please notify the form designer.ERROR CODEThe form is referencing a field that does not exist. Please notify the form designer.RESOLUTIONUse Runtime Function "isNullOrEmpty" to check the value of "TaskOutcome". For instance: isNullOrEmpty(TaskOutcome). Make sure the "TaskOutcome" control has a default value If "isNullOrEmpty" does not apply. When the field "Default value source" in "Task Outcome" choice control setting has been set to "Specify default value", make sure that "Default value" is not blank/empty.  The end user can populate this with double quotes/speech marks and space i.e (" ")  This is based on the business requirement of not having any value set on the outcome. Ensure that when using a workflow variable that is connected to a control, if the variable name is changed you must re-bind the variable to control.ADDITIONAL INFORMATIONThere are

ISSUEWhen clicking the button "Grant Access To Workflow" as per these instruction, the following error occurs: Sorry, something went wrongThe app <GUID> does not exists.ERROR CODERESOLUTIONNavigate to the site URL that is going to be trusted. e.g. https://companyname.sharepoint.com/sites/HR Then navigate to the Workflow App ID from the workflow by following the instruction below: Go to Site Setting > Site app permissions. Find the app display name Workflow (Note : NOT NINTEX WORKLFOW). Get the value of App Identifier of the app display name Workflow. The app ID is between ms.sp.ext| and the @ symbol, for example the App Identifier is i:0i.t|ms.sp.ext|23803489e-0e9e-4fc3-a3b3-e2bd7599c5ad@a6f890769-0c2d-46f7-9480-072519e051ed. The App ID is 23803489e-0e9e-4fc3-a3b3-e2bd7599c5ad. Once we have the URL (step 1) and the App ID (step 2) , we can make a link with this format below: {SiteAddress}/_layouts/15/OAuthAuthorize.aspx?client_id={AppID}&scope=AllProfiles.Read&resp

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. 

TopicWhen using "Start Workflow" action in the Nintex Workflow for Office 365 to start a workflow in a SharePoint List that has more than 5000 items, the following error may occur: The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator. InstructionsModify the "Start Workflow" action configuration of the field "Item ID or GUID" to use the Item ID instead of GUID. Additional Information  Related Links https://help.nintex.com/en-US/office365/Designer/Actions/StartWorkflow.htm 

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

ISSUE When running a workflow, it might stop automatically and an error similar to the following might occur:  RequestorId: eXXXXea-1164-652d-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: The instance has been moved from the Suspended state to the Terminated state because it has expired. The original error which caused it to be Suspended is: The instance has exceeded the outbound http request quota for a 1.00:00:00 time period. The 5000 request limit was reached in 01:23:53.7820143 ERROR CODE "The instance has exceeded the outbound http request quota for a 1.00:00:00 time period. The 5000 request limit was reached in ." Or “RequestorId: eXXXXea-1164-652d-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: The instance has been moved from the Suspended state to the Terminated state because it has expired. The original error which caused it to be Suspended is: The instance has exceeded the outbound

IssueWhen try to start a List workflow using Start Workflow action in Nintex Workflow for Office 365, this error might occurs:Item does not exist. It may have been deleted by another user ResolutionThe workflow that need to be started must have Start Manually setting is enabled.  Related LinksWorkflow Setting Help File