Archive: Nintex for Office 365 Knowledge Articles

Issue"Access denied: Connection does not have access error" when configuring an action using a Connection in Office 365. Error Code"Access denied: Connection does not have access error" Resolution Connection type Minimum permissions SharePoint Online: List & library SharePoint - Designer SharePoint Online: Site & user administration Full SharePoint Online: Site collection administration SharePoint - Global admin SharePoint Online: User management SharePoint - Global admin Nintex Connector - Azure Directory Admin consent required Azure AD app permissions: Read all user's full profile Read all user's basic profile' Nintex Connector - Azure Directory Administration Admin consent required Azure AD admin account required to make connection Azure AD app permissions: Read and write all users profile Read and write directory data  Additional InformationThis table is summarized fo

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. 

IssueWhen trying to assign a task to a user, the workflow fails with the error: 'Failed To Resolve User' ResolutionVerify that the user is recognized within the SharePoint Online User Profile Service, and that they have a valid email associated with their profile. Error CodeFailed To Resolve User 

IssueNintex Form displays blank when item is edited. ResolutionIf a SharePoint column contains illegal characters or non printable characters it may cause an issue opening a Nintex Form for editing. For example, if you copy a table from Excel and paste it in a Multi Line Textbox (Enhanced rich text) and save it, you may have an issue opening that form because it may include illegal characters or non printable characters. For resolution, click edit in the SharePoint list (or click "Quick Edit" button in the list ribbon) and clear the data in the Multiple lines of text column. 

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

TopicWhen trying to start a Component Workflow from another Component Workflow which started from the List Workflow, the following error may occur: "Could not start child workflow" InstructionsThe maximum depth limit when calling component workflows is set to one. The parent-child workflow depth cannot exceed one.  Additional Information For example, consider the following scenarios with different depths:Scenario 1: A List workflow is designed to start Component workflow 1 and Component workflow 1 starts Component workflow 2. This workflow will fail in this scenario as the depth exceeds the limit as shown below: List workflow (depth 0) Component workflow 1 (depth 1) Component workflow 2 (depth 2) Scenario 2: Component workflow 1 that starts Component workflow 2 is added to a workflow. The workflow is successful because the depth does not exceed the limit value as shown below: Component workflow 1 (depth 0) Component workflow 2 (depth 1)  Related Linkshttps://help.nintex.com/en-US/o

ISSUEWhen using a customized Nintex Form within Office 365, the form might have an initial load time of 15 seconds or more.ERROR CODERESOLUTIONAs all custom forms are unique, here are some of the most common fixes for long load times with Office 365 Forms:Reduce the number of controls. Make sure that all of the controls that are on the form are needed, and if there are any that were there for testing purposes, remove them. Reduce the number of rules. Review the rules that are being used on the form, and if there are several rules that accomplish the same outcome, reduce the duplicate rules and apply the single rule to multiple controls on the form. Break the form into multiple forms with redirects. If the form has logical break points, separate it into multiple forms, and use redirects to move the end user to the next stage of the form.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen running a workflow with Office 365 update item permissions action that has configured with a Filter, this error might occurs:Unable to find list item to updateERROR CODERESOLUTIONCheck on the Filter fields and make sure there is no miss configuration on the value.  Use "contains" instead of "is equal to" to compare a value that has a blank space. ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen opening the Nintex Forms Designer there is no option to select New Responsive Forms. ResolutionNavigate to site contents in classic mode and look for the Nintex Forms application.If there is an update available perform the update and test.If the issue persists, remove the Nintex Forms application from the site and then add it back again. 

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.      

IssueAfter removing and reinstalling the Nintex for Office 365 Forms app, all custom forms are missing. ResolutionOpen the Nintex Forms app on the list where the custom form was previously designed and re-publish the form. The custom form will now be restored to that list within SharePoint Online. 

IssueWorkflows complete successfully, however when trying to send emails to particular Active Directory groups, the emails are never received by group members. ResolutionUpdate the Active Directory group mail option from ‘Only Senders Inside My Organization’ to ‘Send Outside The Organization.’  

IssueWhen a user clicks on a URL for a Nintex Form in SharePoint Online in Internet Explorer, an error page states 'The query string "redirect_uri" is missing or invalid'. ResolutionUse the Classic SharePoint 'New Item' URL in your Web Part:Navigate to your list where your Nintex Form is published. Select 'Return to classic SharePoint' (bottom left) Right-click 'New Item' Select 'Copy Shortcut' You now should have a URL that looks like: https://tenant.sharepoint.com/sites/MySite/_layouts/15/listform.aspx?PageType=8&ListId=%7BD82805CA%2D30A3%2D4CFD%2D941C%2D76EF40AF62E7%7D&RootFolder= Place this URL in your Web Part Error CodeThe query string "redirect_uri" is missing or invalid Additional InformationThis issue most commonly occurs when clicking on a Nintex Form URL that is stored in a Web Part in SharePoint Online. Using the Classic SharePoint 'New Item' URL allows SharePoint Online to navigate to the 'New Item' form which automatically redirects to your published Nintex Form,

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

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 save a SharePoint Online site with the Nintex for Office 365 apps installed, the save process fails and the following error occurs:Sorry, something went wrong.  Sorry, this site can't be saved as a template. It contains apps that don't work in templates:Nintex Workflow for Office 365Nintex Forms for Office 365ERROR CODERESOLUTIONRemove the Nintex for Office 365 apps from the SharePoint Online siteNote: With the introduction of the New View Mode in SharePoint Online, it will be necessary to change the view of Site Contents to Classic in order to remove the Nintex for Office 365 appsSave the site as a template Create new site with the saved template Add the Nintex for Office 365 apps back to the SharePoint Online siteADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhile trying to publish a workflow within Office 365, the publish fails with the error:Error publishing workflow. Microsoft.Workflow.Client.WorkflowManagementExcept. A response was returned that did not come from the Workflow Manager. Status code = 503: Service UnavailableERROR CODERESOLUTIONContact Microsoft SharePoint Online support to troubleshoot and resolve issues or failures with the underlying Workflow Manager system in SharePoint Online.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen opening the Nintex Workflow designer within Office 365,  there is a red bar displayingError Connecting to the Workflow Manager: undefinedOr:Error Connecting to the Workflow Manager ResolutionOption 1 Add the following to the trusted sites for the browser: *.nintex.com *.sharepoint.com  Deactivate and Reactivate the "Workflow can use app permissions" site feature.  Ensure the user account has the appropriate permissions to access the designer.Option 2Contact Microsoft SharePoint Support to resolve the underlying connection error between the site and SharePoint Workflow Manager. Additional InformationIf the above doesn't work then please try the following steps in the link below:https://community.nintex.com/t5/Technical-Issues/Enable-SharePoint-2013-workflows-in-Sharepoint-Online-Office-365/ta-p/86006 

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

ISSUEWhen creating a list with geo-location fields, items using those fields cannot be viewed and the following error occurs:Index was outside the bounds of the array. If the problem persists, contact your support team with the following information:ERROR CODERESOLUTIONThis issue is currently under investigation. As a workaround, try the following:Navigate to Site settings. Regional settings. Select the Time zone and change it to something other that what is shows and wait for changes to take place. Once the time zone is set, set it back to your current time zone.  Once you have confirmed its changed back, go back to the list and form and try to access the item again.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen trying to use the "Calculated value" control with the fn-Replace function, in the following format: ("textToModify", "replacePattern", "replacement") The result will be different from the one expected. ResolutionResolution:Remove the two quotations that were placed around the 'TextToModify' parameter so that it should be in this format: (textToModify, "replacePattern", "replacement") 

IssueWhen trying to publish a workflow, you may receive this error."Error publishing workflow. Unable to cast object of type"... 'System.Double' to type 'System.String', or '[Microsoft.Activities.DynamicValue]' to type '[System.String]'.This is usually caused by a Set Variable action or a Math Operation where the data types do not match. The System.Double to type System.String may give you a clue where the issue lies within your workflow. ResolutionReview the workflow in question for any Set Variable actions or Math Operation actions. You will need to verify there are no mismatched data types, i.e. Integer to String, in your actions. 

ISSUEWhen saving or publishing a workflow that contains a State Machine action, the following error might occur:Error publishing workflow. Object reference not set to an instance of an objectERROR CODERESOLUTIONConfigure the State machine action and at least one of the branches. Note: After the workflow has been saved, the branch configuration can be cleared.ADDITIONAL INFORMATIONExclamation marks on State machine ActionRELATED LINKS