Archive: Nintex for Office 365 Knowledge Articles

IssueWhen running a workflow, the workflow completes successfully for some users, however other uses encounter an Access Denied error. ResolutionEnsure that the affected user accounts have Contribute permissions on: List where the workflow is running Any list that the workflow interacts with (query, update, etc.) Task list associated with the workflow Workflow History list for the site at https://[TenantName].sharepoint.com/sites/[SiteName]/Lists/Workflow%20History/AllItems.aspx To minimize guessing, identify which list the error is regarding by doing the following: 1. Refer to the error itself as the list ID is mentioned in the error message (in bold below).2. On any list within the same site, navigate to List Settings; notice that the URL references the list by the ListID.3. In the URL, replace the current list ID with the list ID mentioned in the error. For example: https://tenant.sharepoint.com/sites/MySite/_layouts/15/listedit.aspx?List=87d30f08-7f60-4b17-b144-a100bfab2dfb 4. Afte

ISSUEWhen a workflow contains an action(s) that utilize Connection Manager, the following error may occur: The username format is invalid.ERROR CODERESOLUTIONConfigure the Username field, in the Connection, with an email address instead of a display name. ADDITIONAL INFORMATIONRELATED LINKSHelp file - configure a connection manager

IssueWhen replying to a Lazy Approval email with a valid outcome the email does not seem to be received by the O365 tenant and the Task remains in the status of Not Started. ResolutionThere are many reasons why this issue can occur but these are the basic things to check.1. Navigate to the Nintex status page and check for any incidents concerning Lazy Approval.2. Make sure that the Email infrastructure is not changing the domain for outgoing emails as the task can only be completed if a reply is received from the email address that it was sent to.3. Make sure that the Email infrastructure is not altering the subject line of the email and altering the Lazy Approval token. Related LinksNintex Status Page : Nintex Services 

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. 

IssueWorkflow instance fails with the error: System.Activities.Statement.WorkflowTerminatedException: Error Code: -2146232060, Microsoft.SharePoint.SPException, Message: Exception from HRESULT: 0x80131904 ResolutionPlease open a support ticket with Microsoft SharePoint Online support, as this issue will fall outside the control of Nintex on the SharePoint Online platform. Error Code-2146232060, Microsoft.SharePoint.SPException, Message: Exception from HRESULT: 0x80131904 Additional InformationThis error is caused by a failure within the SQL database system of the SharePoint Online environment. 

ISSUEWhen viewing the workflow status column, workflow progress is not displayed.ERROR CODERESOLUTIONExport all workflows on the list to a secure location. Recreate the list. Import all workflows and publish the workflows.ADDITIONAL INFORMATIONThis issue is caused by using a list template that had the workflow status column already created before the list was saved.RELATED LINKS

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

IssueA workflow is run and suspends with the error System.InvalidCastException:   ResolutionAn invalid cast occurs when a source data type is being transformed into a destination data type but the conversion cannot take place because the data types are not compatible.  An example would be trying to transform a text string into a date/time.Any action that can do a conversion should be checked to make sure that the data going in is compatible with the data that is required to come out of the action. Error CodeEXAMPLE: RequestorId: 72cd8e33-f740-0000-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.InvalidCastException: String at Microsoft.Activities.GetDynamicValueProperty`1.CheckedRead(String propertyName, DynamicItem value) at Microsoft.Activities.GetDynamicValueProperty`1.Execute(CodeActivityContext context) at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor

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

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

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 creating a save button in a task form, the button cannot be used without one of the task outcomes being selected.ERROR CODERESOLUTIONThis is expected behavior. As a workaround, try the following:Create an additional outcome (Incomplete or In Progress etc). Set the new outcome as the default value for the outcome control Create a hide / disable rule on the 'Save & Submit' button for when the outcome is equal to the value created earlier. For example: taskoutcome=="Incomplete" This would allow the save button to be used, but would prevent anyone from submitting the form until the outcome field has been set to one of the expected out of the box fieldsADDITIONAL INFORMATIONRELATED LINKSHow to ignore Decision validation when save button clicked in Flexi Task Nintex Form

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

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

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. 

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 

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.