Archive: Nintex for Office 365 Knowledge Articles

ISSUEWhen saving a Nintex Workflow in Office 365, the following error might occur: Variable - dispose : TypeError: Object expectedERROR CODEVariable - dispose : TypeError: Object expected errorRESOLUTIONAs a tenant administrator, click the gear icon on the top right of the Nintex Workflow Designer window. Click Grant Access to Workflow.ADDITIONAL INFORMATIONFor more information, see Assign a task action for Nintex Workflow for O365 throws error on save.RELATED LINKS

ISSUEWhen publishing a workflow, the following error might occur:Error publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverERROR CODEError publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverRESOLUTIONRecreate the Query List actions in the workflow. Republish workflow.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen using Office 365 storage on a subsite, the following error might occur:AADSTS50001: The application named <application name? was not found in the tenant named <tenant ID>. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.  ERROR CODERESOLUTIONDocuments can only be stored at the site collection level.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen using the List Lookup control on Nintex Mobile that is connected to an Office 365 list, it will only return a total of 2000 items, regardless of the number of items on the list.ResolutionMake sure the Nintex forms and Nintex Mobile are all updated to the latest version. This has been resolved on the latest version of the product.  

IssueWhen adding Nintex Workflow or Nintex Forms for Office 365 apps to a site, they show as "Pending Purchase" instead of being added to Site Contents. ResolutionThe apps are pending approval within the SharePoint Online environment and must be approved by the SharePoint tenant administrator. For more information, see Request app installation permissions in Microsoft Support.  

IssueWhen using the Task action in Nintex Workflow for Office 365 with the "Auto-complete task" setting being activated, the user finds the "task date completed" is the same date when the task created, this can be confusing as to when the Task was actually completed.  ResolutionMake sure to get the information on the task last date modified from the task itself (via workflow task list) and not from the item related to the task.  Additional InformationUse the Query List action by supplying the Task ID from the Task action output, to get the information details of the completed Task. 

ISSUEWhen loading a Nintex Form, the following error occurs, even though app is already up to date:The app Nintex Forms for Office 365 is out of date.  Please update the appERROR CODERESOLUTIONCheck the Javascript on the form to ensure that all parentheses () and brackets {} have been closed.ADDITIONAL INFORMATIONWhen a parenthesis or bracket is not closed it breaks the formatting of the form and the form fails validation. Ensuring all brackets and parentheses are closed properly in the Javascript should resolve this issue.RELATED LINKS

IssueDuring a data center migration the customer receives the following error when publishing a workflow.“Workflow starting based on conditions cannot be saved or published until migration is complete”. Error CodeWorkflow starting based on conditions cannot be saved or published until migration is complete ResolutionThere are multiple steps to a data center migration and one of them is to migrate workflow start condition subscriptions.Each start condition requires a subscription in the list that they are being published on.Each list can hold a total of 100 subscriptions.If these subscriptions are taken up by other applications such as Microsoft Flow the customer will receive this error.Resolutions.1. The customer will need to manually delete subscriptions from the list to make room.2. The customer can remove all start conditions from the workflow and then publish.3. Worst case scenario is that DevOps can remove the subscriptions from the source data center so that they do not need to b

ISSUEWhen saving a workflow, or configuring workflow actions, in Nintex for Office 365, using Edge browser, the following error occurs:Email = dispose : TypeError: Object expectedERROR CODERESOLUTIONUse a different browser. For more information, see Nintex Forms Supported Browsers. ADDITIONAL INFORMATIONEdge is currently not a supported browser.RELATED LINKS

IssueWhen sending emails using the Send An Email action in an Office 365 workflow, the emails have a blank subject line when received by recipients. ResolutionWhen using an Advanced Lookup within the subject line field, do not copy and paste them from one Send An Email action to another. Re-type the subject line and re-use the Advanced Lookup control to pull in the lookup value. 

IssueWhen connecting to Nintex Mobile with an Office 365 account, user authentication fails with the error: "Access Denied. You do not have permission to perform this action or access this resource" ResolutionVerify that the site being connected to has the Nintex Forms for Office 365 app installed.  Error CodeAccess Denied. You do not have permission to perform this action or access this resource 

IssueIn Nintex forms when using a label and populating that label with an Item property changed ToUpper and it has the ”&” character it will crash the form and error with "Reference-to-undeclared-entity-AMP" on form load.  ResolutionA fix for this defect was released in April. Update to the latest version of Nintex Forms for Office 365 app. 

IssueWhen using action Office 365 update item permission, this error might occurs:Failed to resolve group <group name>  ResolutionVerify the group is exist in SharePoint Online.   Modify the action with a valid group name. Terminate and start a new workflow instance.  

IssueWhen using Office 365 query user profile action with connection manager, this error might occur:Unable to reach destination server ResolutionEnsure that "workflows can use app permission" feature has been activated via site settings >> Manage site features If MFA (Multi-factor authentication) has been enabled in tenant then execute the cmdlet Set-SPOTenant -LegacyAuthProtocolsEnabled $true Additional InformationSet-SPOTenant - https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/Set-SPOTenant?view=sharepoint-ps 

ISSUEWhen running a workflow that contains an "Assign a task" action, the workflow might hang on that action and not report any error, even if the user account is valid.ERROR CODERESOLUTIONReview regular expressions for a string field that is empty or has a NULL value and add a "Run If" action so the regular expression runs only if the String value input is not empty. ADDITIONAL INFORMATIONThis issue occurs when the "String" field of a "Regular Expression action" contains a value that is NULL or empty.RELATED LINKS

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

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. 

IssueSharePoint Online workflows are stuck in a 'Started' state, and the blue information bubble states the following:"Access denied. You do not have permission to perform this action or access this resource" Error CodeResolutionGrant workflow initiators 'Contribute' permissions to the Workflow History list. The Workflow History list can be accessed at the following URL: https://[TenantName].sharepoint.com/sites/[SiteName]/Lists/Workflow%20History/AllItems.aspx Additional InformationGuidance from Microsoft on managing list permissions can be found in the Related Links section below. Contribute permissions are needed for the workflow initiator to log workflow history entries to the Workflow History list. When a subscription is within 30 days of expiring, a workflow history entry stating "Nintex Workflow for Office 365 subscription is due to expire" is logged in every workflow instance until your subscription is renewed, and there is no way to disable this message. Related LinksCustomize

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

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. 

IssueWhen responding to a Task in Nintex Workflow for Office 365, the following error may occur: Invalid text value. A text field contains invalid data ResolutionVerify that the approver comment contains less than 256 characters.  Add validation to Nintex Task Form to set the maximum character up to 255.  

  ISSUE When trying to access Nintex Forms or Workflow designer in Nintex for Office 365, the following error might occur. This page can't be displayedTurn on TLS 1.0. TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to <Nintex cloud host URL> again.If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such an RC4, which is not considered secure. Please contact your site administrator.   ERROR CODE This page can't be displayed Turn on TLS 1.0. TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://xxx-xxx-xxx.nintexo365.net again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such an RC4, which is not considered secure. Please contact your site administrator. RESOLUTION Contact your Network Administrator to white-list the Nintex cloud host URL mentioned in the error message. ADDITIONAL INFORMATION This is caused by a Network access restrict

ISSUEWhen using OKTA authentication, the following error occurs for Office 365 Live actions:Error: Direct login to WLID is not allowed for this federated namespaceERROR CODEError: Direct login to WLID is not allowed for this federated namespaceRESOLUTIONNintex does not support OKTA Single Sign on Provider. Use @on.microsoft.com account to resolve this issue. ADDITIONAL INFORMATIONRELATED LINKS

Issue Numbers entered in Nintex form are being registered with comer in SharePoint when the Nintex form control is connected to a SharePoint column with the “Number” data typeThis is for all platforms of Nintex Form and SharePoint    Resolution This is a know issue in SharePoint, this is not a Nintex issue.There are workarounds1, Use a text column and not an number column data type2, Create a calculated column and use the formula = TEXT([Column Name], "0")  

IssueWhen trying to export a Nintex Workflow or Form a dialog appears with the error Export Fail.  ResolutionIncrease the Site storage limit and try again. Error CodeExport Fail Related LinksManage site storage Limits : Manage site storage limits