Archive: Nintex for Office 365 Knowledge Articles

IssueWhen using the action 'Set Field in Current Item' or 'Update List Item' in Nintex Workflow for Office 365, it automatically sets the list column that has the data type Multiple line text to blank, even though this column is not part of the field that is being updated, in the action configuration.  ResolutionThe root cause of this issue is because the Multiple lines of text column has a field 'Append Changes to Existing Text' that has been set into 'Yes'.If this is not the business requirement, then set the 'Append Changes to Existing Text' into No. If this is the business requirement, then make sure that the action to update list item is configured to set the value of the Multiple lines of text column to avoid overriding into blank value.' 

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 looking up a list with the List Lookup control on a Nintex Form and a Source View is specified only 30 items are shown in the control even though the Advanced section of the control settings specifies an item limit of 2000 by default. ResolutionIn SharePoint modify the List View that is specified as the Source View in the List Lookup control and go to Item Limit.  Increase the limit to the desired setting. Additional InformationWhen specifying a Source View in the List Lookup control the List View settings override the item limit specified in the advanced section of the List Lookup control. 

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 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 using a state machine action in a workflow, the workflow processes actions after the change state action, instead of changing states.ERROR CODERESOLUTIONReorganize the workflow so that change state actions occur as the last actions in the state machine.ADDITIONAL INFORMATIONThis is expected behavior for a state machine. The state machine will continue to the end of its logical loop prior to trying to change states. At the end of the loop it evaluates to which state it should change. If there are multiple places with change states it will change to whatever state it was last set.RELATED LINKS

ISSUEWhen browsing to Nintex Forms using Safari on Mac, the following prompt appears:Please enable cookies for your browser to use the FormERROR CODE‘Please enable cookies for your browser to use the Form’RESOLUTIONNavigate to Safari > Preferences. Click Privacy. Select "Allow from websites I visit" or "Always allow".ADDITIONAL INFORMATIONForms is using cookies for user authentication, this is part of the product and cannot be changed. The reason Safari (default behaviour on OS X and iOS) behaves differently than Chrome is because Safari defaulted to not accept all cookies, while Chrome does. As such this would be considered expected behavior. RELATED LINKSSafari 8 (Yosemite): Manage cookies and website data

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 using a Managed Metadata term value within a text field, such as an email body, or Log To History action, the term displays as 'Value | TermIdGUID'Example: 'Nintex Engineer | b664989e-0ac2-4d49-9a89-d6f7bf092fe1' ResolutionThis is expected behavior when converting a Managed Metadata term to a string. You can use the Regular Expression action with the following configuration to strip out the GUID:String: {Variable:OriginalManagedMetadataTerm} String operation: Replace Pattern: |(.*) Replacement String: Output: {Variable:UpdatedManagedMetadataTerm} 

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 Google Chrome version 72 (was released on the 29th of January 2019), the Nintex Task Form cannot be modified in the Responsive Form designer. As well as: To Add a new control onto Nintex Task Form Designer.  Drag and drop controls in the Nintex Task Form Designer.  ResolutionClose all instances of the Chrome browser.  Navigate to the directory where the Chrome browser has been installed. This is either C:Program Files (x86)GoogleChromeApplication or C:Program FilesGoogleChromeApplication. . Then Run the following command from command prompt:  - chrome.exe --disable-features=VizHitTestSurfaceLayer,VizHitTestDrawQuad,VizDisplayCompositor Additional InformationThe Chromium team has confirmed this issue on Google Chrome version 72 and they are working towards a permanent fix for the next released of Google Chrome. 

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. 

IssueAfter adding a confirmation message within the Advanced section inside of a form control configuration, the confirmation message fails to appear on button click. ResolutionEnsure that there are no special characters in the confirmation message. This will include characters such as apostrophes (‘). 

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.