Archive: Nintex for Office 365 Knowledge Articles

TopicWhen using a Web Request action an error may occur when running the workflow. SolutionSome web services or API's do not require a Body in the request as all information is passed in the URL but the Web Request action does need something in the Body even though this section of the action configuration is not starred as mandatory. Adding the content type to the field will resolve the issue even though the content may be ignored by the web service or API. Additional InformationIn general, any error in O365 that has a field name in between square brackets e.g. [Field] means there is an issue with that field.  Sometimes the field name is obvious and other times it is not. Read the error to determine the issue.  In this example the field is empty "null" but other errors may be in regards to the syntax of the information provided in the field. Error MessageSome parameters failed the validation check. - [InputFileContent] : The parameter or the parameter value is null. 

ISSUEWhen accessing workflows in Office 365, the following error might occur: Some workflows may not be shown. We are unable to reach the workflow service ERROR CODESome workflows may not be shown. We are unable to reach the workflow serviceRESOLUTIONContact Microsoft to verify the Workflow Manager service is functioning correctly.ADDITIONAL INFORMATIONRELATED LINKS

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

TopicWhen trying to open the workflow designer in SharePoint Online, it gets stuck loading on 'Connecting to site'.  InstructionsIn Google Chrome:1. Navigate to Settings > Privacy and security > Cookies and other site data.Note: You will find that Block third-party cookies or Block third-party cookies in Incognito are enabled. This prevents the Workflow Designer from loading.2. To allow the Workflow Designer to load, make one of the following changes:Select Allow all cookies Under Sites that can always use cookies, add [*.]sharepoint.com  Additional InformationWhile it is possible to see this occur in other browsers with similar cookie-blocking features, this most commonly occurs in Google Chrome Incognito mode. 

IssueNintex O365 Workflow fails to complete once permission has been removed for current item even though the workflow is using Action Step. ResolutionThe solution to this design is to create a new workflow on the same list/library with Start Workflow Action. This action is calling the second workflow which is running under the credentials supplied in the Start Workflow action. This way the second workflow can “see” the item after the permission removal. 

IssueA trial customer that has paid the Office 365 subscription still have a trial notification when opening the Nintex Workflow or Form designer.  ResolutionThe licensing team has to generate a new license and to verify that the PPT ID must have a valid GUID format including dash symbol.  

IssueWhen one of the branches in the "State Machine" action does not have a "Set Next State" action, the workflow will keep looping in the particular branch. This might lead to another error depending on the action configured under the branch.   ResolutionAdd the "Set Next State" action in the end of each branch of the "State Machine" action. Related LinksBest practice: State machine workflowsSet Next StateState Machine 

IssueNintex O365 Workflow does not start automatically ResolutionThere are few possible solutions to this issue:- ensure that group members are allowed to see each other - ensure members and group are added to the Nintex History list with Contribute permission- ensure App permission is activated at the root site and the sub-site level  

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 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 Nintex Office 365 workflow, the following error occurs on the Exchange Online Create Calendar Item action:Unable to create calendar item. Error: The account does not have permission to impersonate the requested user ResolutionEnsure that the user account has the Application Impersonation Exchange role added and that the user account has permissions to create the calendar list item on the user account specified in the "User to Impersonate" field of the action configuration.  

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 attempting to grant access to a workflow from within SharePoint Workflow designer for Office 365, the following error message appears: "Something Went Wrong"  ResolutionPlease follow the steps below:1. Navigate to the site URL that you are trying to trust ( e.g. https://m365x314721-cdad5d5d9abf7d.sharepoint.com/sites/HR2) 2. Navigate to Workflow App ID from Site Setting > App Permission. We need the App ID from the Workflow and NOT the Nintex Workflow. The app ID is between ms.sp.ext| and the @ symbol, for example: db8f9118-29ec-4d64-8630-521df24c9f32 (please double check and copy paste the value to make sure it is as expected) 3. Once we have the URL and the App ID, add them to the below URL, replacing the values SiteAddress and AppID with respective values.: {SiteAddress}/_layouts/15/OAuthAuthorize.aspx?client_id={AppID} &scope=AllProfiles.Read&response_type=code 4. Following the example above the combination between site URL and app id it will look like this (pl

ISSUEWhen responding to a task and updating the list item properties using Nintex Task Form for Office 365, the list item properties do not get updated.ERROR CODERESOLUTIONReset the Nintex Task Form.ADDITIONAL INFORMATIONThe issue is because the Form created by importing a List Form. RELATED LINKS

IssueWhen an item is created via the Create List Item action, the workflow will not be triggered even when it is configured to start on item creation. ResolutionUse the 'Office 365 Create List Item or Document Set' action instead of 'Create List Item' action.Additional InformationThis is by design and can be replicated via SharePoint Designer. SharePoint Online prevents workflows from recursively starting additional workflows. However, using the 'Office 365 Create List Item or Document Set' allows an item to be created under a set of credentials, allowing recursive workflows to be started as expected. 

TopicThis article is applicable to the new Office 365 Tenants that were created after August 25, 2020.   When trying to open Nintex Workflow for Office 365 Designer this error may occur:"Oops... something went wrong. Please visit status.nintex.com for the latest status or contact your system administrator to check the health of your Office 365 tenancy"  InstructionsResolution 1:Run this script in SharePoint Online Powershell:Set-SPOTenant -DisableCustomAppAuthentication $false Reference: https://docs.microsoft.com/en-us/sharepoint/troubleshoot/workflows/nintex-workflow-fails-to-start Resolution 2:Grant the "Nintex Workflow for Office 365" App Trust. This required Global Administrator permission.  Steps:Get the Nintex Workflow for Office 365 App Identifier Navigate to the Root Site that has Nintex Workflow for Office 365 is installed. Then navigate Site Setting > Site App Permission. On this page, the app permissions will be displayed for all apps on your site. Copy the client sect

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 using Office 365 update Item Permission action, it give an output of the List item URL that can not be use afterward. The URL format return by the List item URL as below: ["https://site_url/Lists/list_name/DispForm.aspx?id=2"]   ResolutionConvert the List item URL that has a Collection data type into single text by utilize action "Get Item From Collection".  Additional InformationThe details of "Get Item From Collection" can be found here. Related LinksHelp file "Get Item From Collection" 

ISSUEWhen running the 'Delete Item' action via the Workflow 2013 Engine office 365, the deleted item does not go to the recycle bin.ERROR CODERESOLUTIONThe 'Delete Item' action is functioning as intended, the action utilized by Nintex is the same as used in SharePoint Designer. In both cases the delete item action for the 2013 engine does not send the deleted item to the recycle bin.  It is possible to utilize the 'Office 365 Delete Items' action to delete items that are sent to the recycle bin. For more information, see Delete items. This action runs outside of the tenancy will take a bit longer as result. ADDITIONAL INFORMATIONRELATED LINKS

IssueThe Shrink and Expand button are disabled in the New Responsive Designer.  ResolutionThe Shrink and Expand buttons are only enabled if there is more than 1 control in the same row. The buttons are disabled if only 1 control in the same row.  

IssueWorkflow gets stuck when trying to create documents using custom templates with Create List Item Or Document Set Action. ResolutionSave and close the template document if it has been opened from the SharePoint library. Otherwise this will cause the workflow to become stuck and not progress as the template file is still open by a user. 

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.      

IssueWorkflows on a particular list are stuck on starting. Checking the internal status of the workflow instance shows the following error.Error: List data validation failed ResolutionCheck if any validation settings are enabled on your list. Navigate to list settings -> Validation settings. There will be validation rule associated to a list field causing the workflow to fail to update a specified field. Error CodeList data validation failed 

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 

IssueWhen trying to add one of the Nintex for Office 365 apps to a SharePoint site, the app addition fails and the following error occurs:Something went wrong trying to add app. Click to retry. When trying again, the app addition fails again with the same error. ResolutionContact SharePoint Online support and request to have the app site manually cleared from Azure.